Skip to main content
Your chatbot can now answer on WhatsApp. You can now tell the AI in plain language when to hand a conversation to your team. Custom responses are now found and used more reliably. Your text snippet now takes priority in answers. This page covers changes up to September 29, 2026.

​
New

  • Your chatbot can now answer on WhatsApp. Get a free US number, keep your WhatsApp Business app number, or connect a dedicated number. The chatbot shows follow-up suggestions as buttons and collects leads with a WhatsApp form. Your team can reply from the dashboard, or from the WhatsApp Business app, which pauses the AI. See Connect WhatsApp.
  • SiteGPT is now a plugin in ChatGPT. Install it from the ChatGPT plugin page, approve access, and ask ChatGPT to work on your chatbots. It uses the same remote MCP server and tools as the other apps. See MCP server.
  • On the Human Support page, write your own rules in When should the AI escalate?. Your rules replace the default rules. Leave the field empty to keep the defaults. See Tell the AI when to escalate.
  • When a subscription ends, SiteGPT now schedules the chatbots and their data for deletion no earlier than 30 days later. At least seven days before the deletion date, SiteGPT emails the account owner that date. To keep your chatbots, subscribe again before that date. See Manage your plan and billing.

​
Improved

  • On the Billing page, buying or removing an add-on now opens a dialog that says what the add-on does and when you are charged or credited. Before, the browser showed a short confirmation. See Manage your plan and billing.
  • The AI no longer offers human help at the end of ordinary answers. A visitor’s “yes” escalates the conversation only when the AI’s last answer offered human help. A visitor who asks for a human in their own words still gets one.
  • The chatbot now searches your custom responses separately with the visitor’s exact question. When a custom response fits, the chatbot prefers it and keeps your wording, product names, and links. See Custom responses.
  • The chatbot now searches your text snippet separately for each message. The matching parts go above your other content, and the AI prefers the snippet’s links and facts and copies its links exactly. In the website widget, links that are only in your snippet now stay in the answer. See How answers work.
  • One setting now controls lead emails: Enable Lead Notifications on the Leads Settings page. Turn it off to stop lead emails. The Disable lead notifications switch in Settings > General is gone. Before, that old switch could stop lead emails even when Enable Lead Notifications was on. If you used the old switch, check Enable Lead Notifications. See Get each lead by email.
  • In Zendesk Messaging, SiteGPT now gives an idle conversation back to Zendesk after 12 hours without a message. Before, Zendesk did this after 24 hours. SiteGPT stays the responder for your channel. See Zendesk.
  • When an account has no active plan, its chatbots stop answering and the widget does not load. Content imports, resyncs, and scheduled syncs also stop. You can still sign in, read your data, and delete content. The API returns 403 ACCOUNT_INACTIVE for blocked actions. See Billing.
  • When a page fails to import, the error now shows the exact error that the website returned.
  • Deleting a chatbot now also stops its scheduled crawls and syncs.
  • Each SiteGPT MCP tool now states whether it only reads, changes data, or deletes data. See MCP.
  • iPhone push notifications now go to every team member of a chatbot, not only the owner. If escalation emails go to a custom list, the escalation push goes only to team members on that list. Each device keeps its own notification settings. See Choose who gets notified.
  • iPhone app 1.0.3: Take over conversation now works the same way as Take over the chat in the dashboard. The visitor sees a notice, and the AI stops. The Needs you filter now shows every escalated conversation that no one took over or answered. See iPhone app.
  • API v2 has a new take-over action: POST /chatbots/{chatbotId}/conversations/{threadId}/take-over. It works the same way as Take over the chat in the dashboard. The visitor sees a notice. See API conventions.
  • The TypeScript and Python SDKs 0.3.0 add conversations.takeOver and conversations.take_over.
  • The Go SDK v0.3.0 adds Conversations.TakeOver and Conversations.SwitchToAI. Conversations.Escalate now works without fields. See Go SDK.
  • The Go SDK v0.4.0 has helpers for the same operations as the TypeScript and Python SDKs. It adds 20 methods for documents, sources, sync jobs, conversations, leads, messages, and onboarding workspaces. Knowledge.DocumentStats now takes filters as a third argument, so code written for v0.3.0 must add nil. See Go SDK.
  • When one model’s share of your messages is used up, the chatbot now switches to the other model in your integrations and through the API too, not only on your website. See Choose a model.
  • In Zoho SalesIQ, when the chatbot escalates a chat, SiteGPT now asks SalesIQ to transfer it to an operator. See Zoho SalesIQ.
  • API v2, the CLI, and MCP now check your plan. On a plan below Growth, requests fail with 403 PLAN_UPGRADE_REQUIRED, and the CLI login page shows an upgrade note. See Authentication.

​
Fixed

  • Widget opens on the Analytics page now count real opens, once per visit. Before, the number was the same as the number of conversations. See Analytics.
  • After a visitor submits the contact form during an escalation, the confirmation message now shows below the form.
  • A document that you resync no longer stays in a waiting state for a long time. It trains again within seconds, or it shows a failed state.
  • In Zendesk Messaging, a visitor who writes again after an agent ends the session, or after you resolve the conversation, now gets a new conversation. It follows your chat mode, so the AI answers when new conversations start in AI mode. See Zendesk.
  • In Slack, answers now hide the 👍 and 👎 buttons when Hide Feedback Buttons is on.
  • On the Appearance page, the Hide Sources switch now shows off for chatbots that never changed it. Sources were always shown for these chatbots. If you saved the Appearance page before September 25 without meaning to hide sources, check this switch. See Appearance.
  • A sitemap scan no longer deletes pages that are still in your sitemap. The scan now deletes pages only when it read the whole sitemap. See Keep content up to date.
  • In Freshdesk Messaging, a tap on the Request Human Support Prompt button now escalates the conversation. Before, the tap sent the button text to the AI. See Freshdesk.
  • In HIPAA workspaces, API v2, the CLI, the SDKs, and MCP now refuse to create, change, authorize, or import from cloud file connectors, like the dashboard. See HIPAA.