Skip to main content
New conversations can follow your working hours, and lead emails can include returning visitors. Team invitations now arrive as a clear invitation email, and inviting the same email address again with the same role sends it again. Your team can lock a conversation in human mode from the … menu. The remote MCP server has a new home view, two settings tools, a tool to reply to visitors, and a read-only connection option. Chatbot lists no longer stop at 100 chatbots. In HIPAA workspaces, the remote and local MCP servers no longer return conversations or leads. At the 4XL and 5XL sizes, the chat icon now loads a larger image. Chat History shows where each conversation started and filters the list by source. This page covers changes up to October 9, 2026.

​
New

  • New conversations can follow working hours. In Settings > Chat Modes, select Follow Working Hours, then set a time zone and the hours for each day. During the hours, new conversations start with your team. Outside them, the AI answers, or your team answers later and the visitor gets your away message one time. Zendesk and Zoho SalesIQ do not use working hours. See Answer during working hours.
  • In API v2, the chat-mode settings section accepts workingHours and returns it with currentMode, which tells how a conversation that starts now begins. When a visitor message gets the away message, the API v2 and API v0 responses include it as awayMessage. See Answer during working hours.
  • Get a lead email each time a returning visitor fills out the lead form again. Turn on Email for every form submission in Leads > Leads Settings. The email has Returning Lead in the subject and shows the values of that submission. It is off by default. See Get each lead by email.
  • The remote MCP server has a new open_sitegpt tool. It opens a SiteGPT home view with a chatbot switcher and tabs for your inbox, escalations, leads, analytics, and knowledge. See MCP server.
  • The remote MCP server has two new tools, read_sitegpt_settings and update_sitegpt_settings. They read and change lead email notifications, human handoff, how new conversations start, and hide sources, for the first 10 chatbots in your chatbot list. See MCP server.
  • The remote MCP server has a new open_sitegpt_inbox tool, named Support Inbox. It opens the SiteGPT home view as a panel inside a conversation in apps that support panels. See MCP server.
  • Reply to visitors from ChatGPT, Claude, and other AI assistants. The remote MCP server has a new reply_to_conversation tool, and the inbox and escalations views have a reply form. If the AI still answers the conversation, the reply takes it over first. See MCP server.
  • API v2 has a new endpoint to reply to the visitor as your team: POST /chatbots/{chatbotId}/conversations/{threadId}/replies. See API conventions.
  • Connect an AI assistant with read-only access. On the MCP approval page, select Read only under Access. The assistant can then read your data, but it cannot create, change, or delete anything. Write calls return 403 TOKEN_SCOPE_NOT_ALLOWED. See Connect with read-only access.
  • A conversation in Chat History shows whether SiteGPT emailed your reply to the visitor, or why it did not, under your last reply. See See whether the visitor got the email.
  • Lock a conversation that your team holds without a lock, for example after a team member replied or when it started in human mode. Open the … menu at the top of the conversation and select Lock conversation. The visitor can then no longer select Continue with AI. Before, you had to select Release to AI and then Take over the chat. See Lock a conversation that your team holds.
  • Chat History shows where each conversation started: Website, API, WhatsApp, Messenger, Slack, Google Chat, Crisp, Freshdesk, Zoho SalesIQ, or Zendesk. In the list, conversations from the API and integrations show the source icon. The source also shows at the top of an open conversation and in Conversation Details. Open Filter and select a source to see only its conversations. The CSV export follows the filter. In API v2, conversations have a source field, and the conversation list accepts a source filter. See Sources.

​
Improved

  • Lead emails list the custom fields in the order and with the labels that you set in the lead form. The page URL comes last. See Get each lead by email.
  • Team invites now arrive as an invitation email with the subject You are invited to <chatbot name> on SiteGPT, with the name of the person who invited, the role, and an Accept invitation button. Before, the invite was a plain sign-in email. See Invite a team member.
  • An invited person can join by signing in to SiteGPT with the invited email address, also after the Accept invitation button expired. Before, after the link expired, you had to delete the invite and invite the person again. See Invite a team member.
  • In HIPAA workspaces, the remote MCP server no longer returns conversations, leads, or escalations to ChatGPT, Claude, or other AI assistants. These calls return 403 HIPAA_AI_ASSISTANTS_DISABLED. See MCP server.
  • SiteGPT CLI 0.6.0 is available. In HIPAA workspaces, the local MCP server (sitegpt mcp) now also blocks conversations and leads. Update the CLI to 0.6.0 or later. With an older CLI, the local MCP server is blocked only if you signed in with sitegpt login. With an older CLI that is signed in with sitegpt login, CLI commands for conversations and leads also fail in HIPAA workspaces. See HIPAA and HIPAA_AI_ASSISTANTS_DISABLED.
  • In ChatGPT and Codex, the remote MCP server no longer offers get_onboarding_status or the onboarding API. Agent-first onboarding is for people without an account, and these apps always sign in to an account first. See MCP server.
  • Your own imports, syncs, and scans no longer wait behind scheduled auto-syncs. Scheduled syncs now run in their own queue.
  • The SiteGPT views in ChatGPT and other AI assistants use the light or dark theme of the app. Each conversation row shows the visitor, the last question, and the page. An open conversation has an Open in SiteGPT button that opens it in the dashboard. See MCP server.
  • GET /chatbots in API v2 returns pages, with limit (100 by default, 200 at most) and cursor. See Pagination.
  • Conversation lists in API v2 load much faster, also for chatbots with long histories. This includes list_conversations and list_escalations in the MCP server.
  • API v2 replies and visitor messages respond faster. Their responses include a Server-Timing header with the time of each step.
  • iPhone app 1.0.4: the Chatbots sheet lists every chatbot on accounts with more than 100 chatbots, and the Usage tab counts the training of every chatbot. See iPhone app.
  • After a team member replies, the conversation shows Release to AI, so you give it back to the AI in one click. Before, it showed Take over the chat first. This also applies to a conversation that started in human mode. See Release to AI.
  • The default away message for working hours no longer promises a reply in the chat. It now reads “Thanks for your message. Our team is offline right now and will get back to you during our working hours.” A hint below the box says that every channel sends the message and that your team cannot reply in Google Chat. Away messages that you saved keep their text. See Answer during working hours.
  • Invite the same email address again with the same role to send the invitation email again. SiteGPT sends the email for the pending invite and does not create a second invite, also when you reached the member limit. In API v2, the response has resent: true. Before, you had to delete the invite and invite the person again. See Send the invitation email again.
  • An invited person can now join by signing in to the iPhone app with the invited email address. Before, they had to accept the invite on the web first, or the app showed the For team accounts screen. See iPhone app.
  • The MCP settings tools now show working hours. read_sitegpt_settings returns chatMode as WORKING_HOURS while the chatbot follows its working hours, so an AI assistant can tell you before it changes the mode. update_sitegpt_settings with chatMode set to WORKING_HOURS turns the saved schedule on again. AI and AGENT still turn working hours off and keep the schedule. See Appearance and settings tools.

​
Fixed

  • Accounts with more than 100 chatbots now see all of them in GET /chatbots (page by page), in the open_sitegpt chatbot switcher (up to 1,000 chatbots), in the chatbot list of the CLI login page, and in the Zendesk connect page. You can also limit an API token to any of these chatbots. Before, these lists stopped at 100 chatbots. GET /api/v2/limits and sitegpt limits now count the quotas of every chatbot that you own, and API v0 GET /chatbots returns every chatbot.
  • SiteGPT CLI 0.6.1 is available. sitegpt chatbots list and the sitegpt_list_chatbots tool of sitegpt mcp now show every chatbot, not only the first 100. See Upgrade the CLI.
  • In API v2, open escalations now show in the conversation list with escalated=true also when the chatbot has had more than 1,000 messages since the escalation.
  • On a shared browser, a visitor who signs in with identity verification no longer sees the conversation of the person who used the widget before. See Identity verification.
  • When you approve SiteGPT again in ChatGPT or another AI assistant, the app’s other connections to SiteGPT stay connected. Before, approving again ended the other connection, and ChatGPT asked you to connect again. If ChatGPT still asks, connect once more. See Permissions.
  • When a visitor answers an email with your team’s reply, the answer now goes to the chatbot’s Support Email, as the setting describes. If no valid Support Email is set, it goes to the first address in the escalation email list or the chatbot owner, as before. See When SiteGPT emails your reply to the visitor.
  • Invites sent with API v2 or sitegpt members invite now use the same invitation email as the dashboard, and the person arrives signed in. Invite email addresses sent with API v2 are now saved in lowercase, so they match the person’s account. See Add a team member.
  • After a visitor submits the lead form, the AI no longer escalates the conversation only because of the form. It thanks the visitor and continues to help. This happened most often with the After N messages trigger. Auto-escalate on lead capture still escalates when it is on. See Hand the conversation to your team after a lead.
  • A website or sitemap crawl that runs longer than 25 minutes now continues where it stopped. Before, it stopped, and the next sync started again from the first page, so pages deep in a large site were not found. See Add your website.
  • A sync no longer stays in processing when its last pages fail, for example pages that return 404. It now completes, and the failed pages show as failed. See Fix failed links.
  • A document that stays in processing for 2 days is now tried again by itself, or marked as failed so that you can resync it. Before, it could stay in processing for good. See Fix failed links.
  • Inviting a person who is already a member of the chatbot now says so, and SiteGPT sends no invite. Before, SiteGPT created a pending invite and sent the invitation email. API v2 now returns 409 MEMBER_ALREADY_EXISTS. See Invite a team member.
  • Inviting an email address that has a pending invite with another role now asks you to cancel that invite first. Before, a second invite to the same email address showed an error on the Members page, and API v2 returned 500. API v2 now returns 409 MEMBER_INVITE_PENDING. See Invite a team member.
  • When SiteGPT saves an invite but cannot send its email, the Members page now says so. Before, nothing showed. Invite the same email address again to send it. See Invite a team member.
  • Older invites saved with capital letters in the email address can now be accepted. See Invite a team member.
  • Saving a settings page no longer resets the settings that a turned-off switch disables. For example, saving Leads Settings while lead notifications are off keeps Email for every form submission. This also applies to the Human Support button texts and switches, the icon background color in Appearance, and Max Messages Per Conversation in Settings > General. See Get each lead by email.
  • The MCP approval page now sums up every permission that the app gets, including billing management, API tokens, and integrations. A request for only read permissions shows read-only summaries. See Permissions.
  • The API v2 reference for team members now matches the API: invite roles are AGENT, MANAGER, ADMIN, and SUPER_ADMIN, the list of pending invites is pendingInvites, and canceling an invite needs members:write. See API v2.
  • The chat icon on your website can now be sharp at the 4XL and 5XL sizes. Before, the widget showed a 96x96 px image stretched to the larger button. For a sharp icon, upload an image of at least 156x156 px. Smaller sizes load the same image as before. See Change the chat icon.
  • iPhone app 1.0.5: in the Chatbots sheet, a chatbot whose conversations have not loaded shows “Open to see activity” until you open it. Before, it showed “All quiet”, also when conversations needed you. See iPhone app.