Customer support from Claude Code

One command connects Claude Code to your support inbox. It answers from your code, drafts the replies for your OK, and saves every answer so the chat on your site handles it next time.

Recorded on the Northwind demo workspace: adding the server, signing in, and Claude Code working the inbox from the code.

Most hard support questions are about how the product works, and the answer is in the code. Claude Code can read the code, but it only works while you are at the keyboard and starts each session fresh. Afterchat is the part that stays: the chat on your site that answers around the clock, the inbox, and the knowledge vault that keeps every answer. Connected over MCP, Claude Code works the inbox with your repo open.

Set it up

  1. Add the server. In a terminal:

    claude mcp add --transport http --scope user afterchat https://afterchat.chat/mcp

    --scope user makes it available in every project. Leave it out to add it to the current project only.

  2. Sign in. Restart Claude Code, run /mcp, pick afterchat and choose Authenticate. A browser opens on Afterchat. 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. Ask Claude to "check Afterchat status". It tells you the workspace, what it may do and what is waiting.

Or paste this into Claude Code and let it do the steps itself:

Connect Afterchat to this agent: fetch https://afterchat.chat/agent-setup.md and follow it.

Starting with an empty workspace? Run /mcp__afterchat__vault in your repo first, and Claude writes the vault from your code and docs for you to review.

A morning in the inbox

Open Claude Code in your repo and run /mcp__afterchat__inbox, or just ask it to check the Afterchat inbox. It lists the conversations waiting on you, technical ones first. For each one it reads the conversation, searches the vault, opens the code it needs and drafts a reply into the inbox.

The reply waits there for your OK, with a line saying what Claude checked and what it saved. You approve it in Afterchat, or edit it first. When the conversation closes, what Claude learned is kept as an entry that points at the files it read, and the chat on your site answers that question by itself from then on.

The commands

CommandWhat it does
/mcp__afterchat__inboxWorks through the conversations waiting on you, technical ones first
/mcp__afterchat__investigateDigs into one conversation with the code and your own tools
/mcp__afterchat__gapsAnswers the questions the vault is missing, from the code
/mcp__afterchat__vaultBuilds or improves the vault: topics, entries, merges and guides
/mcp__afterchat__reviewChecks unchecked answers and tidy-up suggestions against the code
/mcp__afterchat__triageLays out the ranked requests, for deciding what to build
/mcp__afterchat__buildLoads a request's brief to build from
/mcp__afterchat__shipTells everyone who asked and updates the vault, once you approve

What waits for you

Claude works as you, with what you allowed when you signed in. Replies to customers wait as drafts unless an owner lets them go out at once, and hold rules keep prices, limits, refunds, legal terms and anything quoting your code with a person whatever the setting. Public changes and shipping a request wait on the Coding agent page, and every call is in the log with an undo. The full list is on the MCP server page.

On our own support

We run FanWake's support this way. Since 26 October 2026 Claude Code has made over 800 calls to it, reading chats, drafting replies and keeping the vault. On 31 October one session rewrote the vault from FanWake's code and docs, 152 entries in 10 topics, which were reviewed and approved as one batch. The whole story, with the numbers, is in the write-up on the blog.

Questions

How do I use Claude Code for customer support?

Connect your support inbox to Claude Code as an MCP server. Claude can then read conversations, check your code, draft replies and save what it learned, while the chat on your site keeps answering when you are away. With Afterchat that is one command and a sign-in in the browser.

Can I use Claude itself, not Claude Code?

Yes. In Claude on the web or the desktop app, add Afterchat from Claude's connector directory. Claude there can work the inbox and the vault but can't see your code, so the questions that need the code are for Claude Code.

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 Code connects to over MCP.

Does Claude Code have to stay open?

No. The chat on your site answers around the clock from the knowledge vault and hands over what it can't answer. Claude works through those when you open it.

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.

What does it cost?

Afterchat is free while in early access, within a monthly AI allowance that covers a small team's chats. Claude Code 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 Claude for customer support How to use Claude for customer support: add Afterchat from Claude's connector directory, and Claude works your support inbox, drafts replies and keeps your knowledge vault. 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

Coding agents How to use Claude Code for customer support How I run customer support from Claude Code over MCP: the setup, what the agent can do, what waits for approval, and 825 real tool calls on FanWake. 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. 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.