What shipped

PlatformG4 per-workspace pii read masking, default off.

DocsThe Sign-in and identity docs page now has its navigation title in every supported language. The title of the new /docs/identity page showed in English in the docs menu of the Arabic, Hindi, Japanese, Korean, Russian and Chinese sites. It now ships with all 14 translations.

ChatBusymate AI clamps list sizes and pages instead of refusing. When an AI assistant asks Busymate AI for more rows than a list returns, for example 500 conversations at once, it now gets the maximum with a short note "limit clamped to 200" instead of an error. The conversation list also returns a next_cursor to fetch the next page. In ChatGPT, an error that arrives only as a code (such as "INVALID_ARGUMENT") now shows a sentence people can act on.

InboxDeleting a contact now also clears their name from the AI conversation records. When you delete a contact in the Inbox, the name and handle that the channel stamped on the contact's AI conversations is cleared too. The conversations stay; they just no longer show the redacted name.

PlatformThe login-page check on the sign-in provider test now actually runs. The "Test identified launch" report was meant to include a check of your login page (does it stay silent, can it be framed, does its cookie work in a frame), but it never appeared. It now does, with a fix text for each problem.

ChatA signed-in page no longer pops a guest chat open after a reload, and signing out ends the chat's account access. Some sites show the assistant inside one of their own pages (RentADriver's Support tab) and also have the floating chat button. On those sites the floating chat no longer reopens by itself, as a guest, every time the page is reloaded. After the visitor signs out, it can no longer pick up the signed-in session.

DocsOne page now explains every way to sign your customers in, and how your own tools act as them. The new page /docs/identity covers a customer already signed in on your site, sign-in inside the widget, the full chat page, apps, your MCP server or API, the "Ask customers" switch, sign-out, and what each channel can do. It starts with one diagram, then short numbered steps with copy-paste code, a verify checklist and a troubleshooting table. The older identity guides point to it.

ChatEdits to a sign-in provider (login URL, account URL, issuer) apply at the next chat load, with no republish. The chat page used the copy of the provider frozen in the last published settings, so a changed login URL only took effect after a publish. The published settings now only list which providers are on; the details are read from the live provider (cached for 10 s).

InboxIntegrators and agents can now read the Busymate AI identity contract as one machine-readable page. Https://busymate.ai/.well-known/Busymate AI-integration.json lists the identity contract version, the SDK releases, the launch and connector token rules, the host calls and the reason codes, each marked live, planned or legacy. Nothing changes in how sign-in or connectors behave. Messenger conversations taken over by a person keep the customer's Facebook name. When someone on your team claims a Messenger conversation, or the customer asks for a person, the Inbox now shows the customer's Facebook name instead of "Anonymous visitor".

MCPWorkspaces can stop asking signed-in customers to authorize account tools, connector by connector.

InboxPartner widgets in the chat can refresh their own read-only data again. Messenger conversations now show the customer's Facebook name. The Inbox, conversation header and Customer Dashboard name a Messenger customer by their Facebook name instead of "Anonymous visitor".

MCPConnectors can now receive the new signed customer token, one workspace at a time. When the new token is switched on for a workspace, every call a signed-in customer makes to one of its MCP servers also carries Busymate AI's ES256 identity token in the X-Busymate AI-Actor header (or in Authorization once the server says it accepts it), and guests' calls carry no identity token at all. The account-linking timeline shows when a connector accepted or rejected the token. Nothing changes for workspaces where it is off, which is every workspace by default.

MCPBusymate AI now publishes the public keys for its new connector identity token. Your MCP server can verify the signed customer identity Busymate AI sends with no shared secret.

ChatConnecting a partner account from the chat now completes with providers that do not return an issuer on the redirect. In-chat sign-in sends your session only to busymate.ai. Signing in inside the chat now exchanges your session for a chat sign-in only at busymate.ai itself. A request that claims a different host is refused and logged, and nothing is sent anywhere. Signed-in Telegram customers can use the assistant's tools again. If you signed in through a workspace's Telegram bot, the assistant answered every tool request with "Your verified customer session is no longer active". Public tools such as product search now work again. Signing out of Telegram, or a disabled sign-in channel, still stops them at once.

InboxYour mate can now remember signed-in customers. Turn on Customer memory under Connections › Customer context and your mate keeps a short summary of each signed-in customer's earlier conversations and the issues still open. It reads that summary when the customer comes back, so they do not have to repeat themselves. The summary is written only from what the customer and your mate said, never from tool results, and only for customers signed in through your identity provider. Your team sees it, with the customer's signed details, in the Inbox contact panel and can correct or forget it there. You choose how long it is kept; turning memory off deletes it within a day, and erasing a customer erases it at once. Choose which signed facts about a customer your mate may use. A new Console page, Connections › Customers › Customer context, lets you decide which facts your identity token carries about a signed-in customer (plan, number of orders, vip status, language…) your mate and your team may use, with a name and a meaning for each. Your mate receives only those, labelled and quoted, with the identity provider that signed them, and treats them as facts, never as instructions. Facts can now sit inside one signed object (for example customer.plan). Anything a browser, app or channel sends without your signature is never used. The identity and Web SDK guides explain how to add them. ChatGPT is told bulk conversation deletion isn't available. When you ask ChatGPT to delete old conversations in bulk, the conversation tools it reads now say plainly that bulk deletion isn't available, so it no longer offers to clean up by date.

PlatformBusymate AI views in ChatGPT say why a request failed.

MCPPublic tools work for guests on sign-in connectors. A guest asking the Rent assistant for a delivery quote or coverage check now gets the answer. Tools a workspace marks public no longer need a stored sign-in; they run without a credential and never borrow a stored one.

DocsYour mate now reads the platform's own docs, setup guides and release notes directly. Ask the assistant on busymate.ai how to set up Telegram, what a docs page says, or what changed recently, and it now reads the published page, the setup guide or the changelog and answers with links to the exact page and section. It can also tell you whether the platform is up right now, from the same live checks the status page shows. MCP clients that connect to busymate.ai/mcp without signing in get the same four new read-only tools.

DocsWhen a workspace's knowledge comes from a public documentation MCP (for example a Mintlify site), the assistant can now open the full page a docs search found, instead of answering from search snippets only.

InboxOn Insights, Resolution and handoff, the "Where people ask for a person" panel now shows its real figures (or an empty state) instead of a false "You may not read this scope."