Reply to visitors from the inbox
Your team can now answer a conversation from the Inbox. The reply reaches the visitor wherever they are talking — the chat page, the widget, WhatsApp or Telegram — signed with the team member's first name.
What shipped
- A reply box under every conversation, with emoji, Enter to send and a note of which channel the answer goes out on.
- Visitors see the team member's first name and photo next to the message, marked as someone from your team — never their email address.
- An open chat page or widget shows the reply within seconds, without a reload.
- On WhatsApp, Meta only allows free-form replies within 24 hours of the customer's last message; after that the reply box tells you instead of failing silently.
- Whoever replies first becomes the conversation's owner if nobody had it yet.
- Also in the API and MCP: POST /v1/sessions/{id}/reply and the reply_to_conversation platform tool.
One platform MCP connection per workspace
Each workspace now has its own platform MCP URL, so you can keep several workspaces connected in Claude, Cursor or any MCP client at the same time instead of disconnecting and reconnecting.
Invite links, resend and a clearer Team tab
Every workspace invitation is now a link you can share on WhatsApp or Slack, and the Team tab shows when each invite was sent, lets you resend it, and keeps revoked invites with their date.
Saved replies, team presence and automatic assignment
The last pieces for running live support from SuperCognit: canned answers on a slash, an Available / Away switch, new hand-overs assigned to whoever is online, and an Inbox that updates itself.