You can connect Intercom to Claude in under a minute by adding Windsor’s native connector inside Claude and picking Intercom as a connected data source, no code, no pasted URLs, and no custom connector setup required. Once it’s linked, Claude can pull your live Intercom conversation data through Windsor.ai and answer questions about response times, ratings, and reopen rates in plain language.
The alternative is digging through the Intercom inbox or building a report by hand every time someone asks how fast the team is replying or how conversations are being rated. Connecting through Windsor.ai skips that manual work. The data stays live, so you can ask Claude directly instead of exporting spreadsheets or screenshots each time.
2 steps to connect Intercom to Claude
Takes under a minute, no code or manual CSV work required.
📖 See the full setup walkthrough in Windsor’s documentation on integrating data into Claude.
Prerequisites
- A Windsor.ai account (free forever plan, no credit card required, or a paid plan for higher usage)
- An Intercom account with conversations or support tickets to report on
- A Claude account on a plan that supports connectors
Step 1. Connect Intercom to Windsor.ai
- Create a free account (or sign in) at onboard.windsor.ai/app/intercom
- Select Intercom from the list of data sources
- Authorize Windsor.ai to access your Intercom workspace
- Connect additional Intercom workspaces too, if you support more than one brand or region
Step 2. Add the Windsor.ai connector in Claude
Windsor is listed natively inside Claude, so there’s no custom connector URL to paste. Open Claude, go to Settings, then Customize, then Connectors. Search for “Windsor” and select Add, it’s a one-click install.
Sign in to Windsor when prompted, then pick your Intercom connector from the list of sources tied to your account. Done.
💡 Pro tip: Set permissions to “Always allow” so Claude can query your Intercom data without asking for confirmation on every prompt.
Confirm the connection is live before you start asking anything else:
List the data sources connected to my Windsor account. Do you see Intercom there?
If Intercom shows up in the list, you’re ready to start asking Claude about your support data in natural language.
The metrics that matter for Intercom
| Metric | What it tells you |
|---|---|
| Conversation Median Time To Reply | The typical wait before a customer gets a reply mid-conversation, a core support SLA signal. |
| Conversation Time To Admin Reply | How long it takes an admin to send the first reply, a direct read on your team’s initial responsiveness. |
| Conversation Time To Assignment | How long a conversation sits before it gets routed to a person or team, a flag for routing bottlenecks. |
| Conversation Time To First Close | How long it takes to resolve a conversation the first time, your baseline resolution speed. |
| Conversation Time To Last Close | How long a conversation takes to reach its final close, including any reopens, a truer end-to-end resolution time. |
| Conversation Count Assignments | How many times a conversation changed hands before it was resolved. High counts point to escalation or routing problems. |
| Conversation Count Parts | How many back-and-forth messages a conversation took, a proxy for how complex the issue was. |
| Conversation Count Reopens | How often a conversation marked closed had to be reopened, a sign that first-touch resolution isn’t sticking. |
| Conversation Rating | The 1-5 CSAT score a customer gave the conversation, your most direct read on satisfaction. |
What to ask Claude about your Intercom data: prompt ideas
Conversation and support performance
Show our median time to reply on Intercom conversations this month compared to last month.
Which conversations took the longest to reach first close in the past 30 days, and which team handled them?
Customer engagement and messaging
List which conversations got reopened the most in the past 30 days.
Break down our average conversation length, by count of message parts, by team this quarter.
Ratings and satisfaction
Calculate our average conversation rating by team this quarter, and flag any team below a 4.
The Intercom connection through Windsor.ai is read-only. It’s built for analysis and reporting on your support performance, not for creating, closing, or reassigning conversations.
Bonus: analyze Intercom alongside your full stack
Windsor connects 350+ sources, so Intercom doesn’t have to live in its own silo. A few realistic blends:
- Support cost behind every acquisition channel. Blend Intercom’s conversation volume and reply times with Facebook Ads and Google Ads spend to see which acquisition channels bring in customers who need the most support after they convert.
- On-site behavior around chat conversations. Pair Intercom conversation ratings and reopen rates with GA4 to see whether visitors who start a chat convert or bounce at a different rate than those who don’t.
- Support-to-revenue view. Blend Intercom’s response times and CSAT scores with your CRM or billing data to see whether slow replies or low ratings show up later as churn or smaller deal sizes.
Other ways to connect Intercom to Claude
Manual CSV export
You can export conversation data from Intercom as a CSV and hand it to Claude as a file. It works for a one-off look, but it’s a static snapshot from the moment you downloaded it, and you have to repeat the export every time you want an updated answer.
Zapier or Make
Zapier or Make can move Intercom data into another tool as part of an automated workflow. That still means building and maintaining the workflow yourself, and it moves a copy of the data rather than giving you a live connection to query directly in Claude.
Neither approach gives you the live, queryable view that connecting Intercom directly through Windsor.ai does.
Conclusion
Connecting Intercom to Claude through Windsor’s native connector takes two steps and no code: link Intercom to Windsor.ai, then add the Windsor.ai connector in Claude. From there, you can ask about response times, ratings, and reopen rates whenever you need them, without leaving the conversation to dig through the Intercom inbox.
🚀 Ready to connect Intercom to Claude? Connect Intercom to Windsor.ai and start asking Claude about your support performance.
FAQs
Do I need to write any code to connect Intercom to Claude?
No. The setup is entirely no-code: authorize Intercom in Windsor.ai, then add the Windsor.ai connector in Claude through Settings, Customize, Connectors.
Can I connect multiple Intercom workspaces to Claude?
Yes. You can authorize more than one Intercom workspace in Windsor.ai, which is useful for agencies or teams managing support for multiple brands or regions, all queryable from the same Claude connection.
Can I combine Intercom data with other channels in Claude?
Yes. Windsor.ai connects 350+ data sources, so Claude can blend Intercom’s support metrics with marketing, sales, or product data already connected to the same account for a fuller, cross-channel view.
Can Claude create, close, or reassign Intercom conversations through this connection?
No. The Intercom connection through Windsor.ai is read-only. Claude can analyze and report on reply times, ratings, and reopen rates, but it cannot create, close, or reassign conversations back in Intercom.
Does Windsor.ai pull the actual conversation text from Intercom?
Windsor.ai reports on conversation-level metrics and dimensions, such as reply times, ratings, and device or account breakdowns, rather than the raw message text of individual conversations.
Windsor vs Coupler.io

