Sales & Customer Support · Intercom + Claude
Intercom MCP with Claude: Faster Customer Support and Smarter Sales Follow-Up
The short answer
Claude works with Intercom through the Model Context Protocol (MCP), an open standard that acts like a secure adapter between the two. Once connected with OAuth sign-in, Claude can read conversations and contacts, draft or send messages, update customer records and help automate support tasks, all within permissions your organisation controls.
What is Intercom?
Intercom is a customer messaging platform used by sales, marketing and support teams. It offers live chat, inbox management and automated messages that help businesses talk to customers at the right moment. Support leaders, sales teams and customer success managers typically use it to engage visitors, answer questions and turn conversations into sales or renewals at scale.
How Claude connects to Intercom through MCP
The Model Context Protocol (MCP) is an open standard that lets Claude securely use other software. Think of it as a universal adapter between Claude and a tool like Intercom. Your organisation decides exactly what Claude is allowed to see and do, and the connection can be switched off at any time.
Once Intercom is connected through OAuth sign-in, Claude can typically fetch recent conversations, read contact details, summarise a customer's history and send replies or update contact fields. Access is limited to the permissions granted to the connected account, so Claude only works with what your team has approved.
Permissions and approvals keep people in charge. Consequential actions, such as messages to large customer lists or changes to billing-related contact data, can require a human sign-off before they run. Every action is logged so your team can review what happened and why.
What you can automate
Summarising open support conversations
Claude can read long chat threads in Intercom and produce a short summary of the issue, what the customer has already tried and what remains open. Support agents pick up cases faster and customers do not have to repeat themselves. Team leads can also review summaries to spot recurring problems.
Drafting replies for agents to review
For common questions, Claude can draft a reply based on your help articles and past resolutions. The agent reviews the draft, edits it if needed and sends it. This keeps tone consistent while saving time on repetitive queries.
Qualifying website leads
When a visitor starts a chat, Claude can ask structured questions, record answers such as company size and use case, and update the contact record in Intercom. Sales teams then receive well-prepared leads rather than raw chat transcripts.
Routing and tagging conversations
Claude can read incoming conversations and suggest tags, priority levels or the right team to handle them. Routing rules stay under your control, and staff can override any suggestion. Fewer tickets sit unassigned and response times improve.
Follow-up after customer success calls
After a call, a customer success manager can give Claude the notes. Claude drafts a follow-up message and updates the contact's notes in Intercom for the account owner to approve. Renewal conversations start with a clear record of what was agreed.
An end-to-end workflow: Lead-to-support handover with Microsoft 365
TriggerA website visitor asks a pricing question in Intercom outside office hours.
Claude answers common questions using approved product and pricing content.
Claude asks qualifying questions and records company size and need in the Intercom contact.
If the visitor requests a call, Claude creates a task in the sales team's Microsoft 365 calendar and sends a summary to the sales inbox.
The sales representative reviews the lead and approves the follow-up message before it is sent.
Once the deal closes, Claude updates the contact status in Intercom so support knows the customer's onboarding details.
OutcomeLeads receive a same-day response, sales teams start calls with full context, and support inherits accurate customer records. Results vary by business, but many teams find response times and handover quality improve noticeably.
How we set it up
Free automation audit
We review how your support and sales teams use Intercom today and identify the conversations, follow-ups and routing tasks worth automating. You receive a clear list of options and a suggested starting point, at no cost.
Secure connection with OAuth sign-in
We connect Claude to Intercom using OAuth sign-in, the method Intercom supports. Access is granted with least-privilege permissions, so Claude can only perform the actions your workflows require.
Workflow design and approvals
We design the end-to-end workflow across Intercom and your other systems, such as Microsoft 365, your CRM or ticketing tool. We set which actions need human approval before they run.
Testing on real past cases
We test the workflow against real past conversations and contacts. We check accuracy, tone and edge cases, and adjust until your team is satisfied with the results.
Launch, monitoring and training
We launch with audit logs and monitoring in place, then train your agents and managers on how to use and review Claude's work. We check performance after launch and refine the workflow as needed.
Who benefits
- Head of customer support
- Faster first responses, clearer case summaries and better routing, so agents spend more time on complex problems.
- Sales development lead
- Qualified leads with context captured in Intercom, reducing manual data entry and speeding up follow-up.
- Customer success manager
- Consistent follow-up messages and up-to-date account notes after every call or review.
- Operations or IT director
- A governed connection with defined permissions, approvals and audit logs that fits existing security policies.
Security and control
- Least-privilege OAuth access so Claude only reaches the data and actions it needs.
- Human approval for messages sent to large lists or changes to sensitive contact fields.
- Full audit logs of Claude's actions, reviewable by your team at any time.
- Clear rules on what Claude may say to customers, based on your approved content.
- Regular reviews of workflow performance and permissions after launch.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the Claude integration in their chosen region to match internal data policies and sector rules. In India, the Digital Personal Data Protection Act, 2023 governs how customer personal data is handled, and we design workflows to support those obligations. Organisations in the UAE and Saudi Arabia must meet local data protection laws, and hosting region is chosen to meet those requirements as well.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Intercom MCP server do?
The Intercom MCP server acts as a secure bridge between Intercom and AI tools such as Claude. It allows Claude to send messages, fetch conversations, update contacts and support automated workflows, using natural language instructions. Access is limited to what the connected account is permitted to do.
Is connecting Claude to Intercom secure?
Security depends on how the connection is set up. Using OAuth sign-in, least-privilege permissions, human approval for sensitive actions and full audit logs helps keep customer data protected. We design the connection to match your existing security and data policies before anything goes live.
What can Claude do with Intercom once connected?
Typically, Claude can read conversations and contact details, summarise customer history, draft or send replies, suggest tags and routing, and update contact fields. What it is allowed to do is defined by the permissions you grant during setup.
How long does setup take?
Timelines depend on how many workflows you want to automate and how many other systems are involved. A focused first workflow can often be ready within a few weeks after the free audit, including testing and team training. We confirm the timeline during the audit.
Which Intercom plan or permissions are needed?
Requirements depend on the features you want to use and the account permissions your organisation holds. In general, the connected Intercom account needs access to the conversations and contacts involved in each workflow. We review your current setup during the free audit and advise what is needed.