Claude is good at the writing side of support: reading a conversation, working out what the customer needs and answering clearly. What it doesn't have on its own is your support inbox, or any memory of what your team already answered. Afterchat gives it both. Add it to Claude as a connector, and Claude can work the inbox, answer from the knowledge vault and save what it learns, while the chat on your site answers customers when nobody is around.
Set it up
-
Add Afterchat. Open it in Claude's connector directory and add it.
Or add it by hand: in Claude, open Settings, then Connectors, choose Add custom connector and use the address
https://afterchat.chat/mcp. Sign in. Choose Connect. Afterchat opens in your browser. Signing in makes your account if you don't have one, and you pick the workspace and untick anything Claude should not do.
Check it works. In a new chat, ask Claude to "check Afterchat status". It tells you the workspace, what it may do and what is waiting.
On a Team or Enterprise plan, an owner may need to add the connector for your organization first.
What to ask it
No special commands are needed. Ask in plain words:
- "Check the Afterchat inbox and draft replies to what's waiting."
- "What did customers ask this week that the vault couldn't answer?"
- "Turn yesterday's answer about invoice exports into a vault entry."
- "What are customers asking for most, and how many asked?"
Replies wait as drafts in the Afterchat inbox until someone approves them, and what Claude learned is kept in the vault, so the chat on your site can answer the same question next time.
For everyone on the team
Each person adds the connector and signs in as themselves, so Claude works as the person who connected it, with that person's role, and your workspace's rules apply to everyone. Someone who answers customers all day can work the inbox from the Claude chat they already have open, without opening another tool.
When the answer is in the code
Claude in the app can't see your code. For the questions only the code can answer, like why an export skipped three invoices, connect the same inbox to Claude Code in your repo. Both work on the same inbox and the same vault, so an answer Claude Code found is there when Claude in the app picks up the next chat.
What waits for you
Replies to customers wait as drafts unless an owner lets them go out at once, and hold rules keep prices, limits, refunds and legal terms with a person whatever the setting. Public changes to your help content wait for a yes, and everything Claude does is in the log with an undo. The full list is on the MCP server page.