Use Claude for customer support

Add Afterchat to Claude from Claude's connector directory. Claude reads the chats waiting on you, answers from your knowledge vault and drafts the replies, and the chat on your site keeps answering around the clock.

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

  1. Add Afterchat. Open it in Claude's connector directory and add it.

    Add to Claude

    Or add it by hand: in Claude, open Settings, then Connectors, choose Add custom connector and use the address https://afterchat.chat/mcp.

  2. 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.

  3. 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.

Questions

How do I use Claude for customer support?

Connect your support tool to Claude as a connector. Afterchat is in Claude's connector directory: add it, sign in in the browser, and Claude can read the inbox, answer from your knowledge vault, draft replies and save what it learned.

Does it work in the Claude desktop app?

Yes. A connector added in your Claude settings works in Claude on the web and in the desktop app.

Is this the same as Claude's Customer Support plugin?

No. That plugin gives Claude skills for triaging tickets, drafting replies and writing knowledge base articles with the tools you connect. Afterchat is the support chat itself: the chat on your site, the inbox and the knowledge vault, which Claude connects to.

Can Claude reply to customers without me?

Only if an owner allows it. By default its replies wait as drafts in the inbox for a person to approve, and hold rules keep prices, refunds and legal terms with a person whatever the setting.

Can Claude answer questions about our code?

Not from the Claude app, which can't see your code. Connect the same inbox to Claude Code in your repo for those. Both work on the same inbox and the same vault.

What does it cost?

Afterchat is free while in early access, within a monthly AI allowance that covers a small team's chats. Claude is billed by Anthropic as usual.

Works with

MCP server MCP server for customer support Connect Claude Code, Cursor or Codex to your support inbox over MCP. Answer chats from your code, keep every answer, approve what reaches customers. Claude Code Claude Code for customer support Use Claude Code for customer support: one command connects it to your inbox over MCP, it answers from your code, and every answer is kept. Cursor Customer support in Cursor over MCP Connect Cursor to your support inbox over MCP in one click. Cursor's agent answers support chats from your code, and every answer is kept for the chat on your site. Codex Customer support in Codex over MCP Connect Codex to your support inbox over MCP with one command. Codex answers support chats from your code, and every answer is kept for the chat on your site.

Read next

Handover When should an AI chatbot hand off to a human? The five moments an AI support chatbot should hand a conversation to a person, what the handover message should say, and how often it happened in a live support chat's first week on its own. Knowledge base An AI support chatbot trained on your docs and your code How to give an AI support chatbot your own knowledge: why crawling your docs is only the start, how short checked entries built from your docs, code and chats answer better, and how to keep them true. Feature requests How to track feature requests from support chats Support chats are where customers say what they wish your product did. How to capture those requests, group different wordings into one, rank them by how many accounts asked, and tell everyone when it ships.