Intercom + Querri
Ask why volume moved, where response times slipped and which accounts lean on support hardest, and get answers that also know revenue, renewals and product usage. Querri copies Intercom into one Library with the rest of your business on a schedule you pick.
Querri only reads from Intercom and never changes a conversation, ticket or contact. You authorize it in Intercom, with no token to paste. SOC 2 Type II, HIPAA and ISO 27001:2022 certified.
Why Intercom reporting gets hard
Support and CX leaders hit the same walls once a question goes beyond the charts Intercom ships with. They come from a reporting tool designed around the conversation, and the inbox itself works fine.
Custom reports and custom chart editing need Intercom's Advanced or Expert plan. On other plans you assemble reports from the chart library and live with the metrics it offers.
Custom reports cover conversation and ticket metrics, not the people or the business behind them. Intercom's own advice for profile-level reporting is to export the data to another tool. Plan, revenue and renewal date sit in other systems anyway.
Intercom reporting freezes company attributes and tags at the moment a conversation is created. A customer who upgraded last month still shows their old plan on every earlier conversation, so "volume by plan" depends on which plan you mean.
Conversation exports download in the browser only up to 10,000 rows, and bigger ones arrive by email. Someone rebuilds the same pivot table every Monday, and each copy drifts from the last.
One teammate tags "refund", another "refunds", a third uses a conversation attribute instead. Counts by topic split three ways, and the trend you're looking for hides inside the noise.
What you can finally answer
Each comes from the weekly work of running a support or CX team: the question, why Intercom alone makes it slow, and what Querri does with it.
Why it's hard
Tags are applied by hand and inconsistently, so a topic report counts the same issue under three names and misses the ones nobody tagged.
With Querri
Querri reads conversations with their tags, folds spelling variants together and tells you how much that moved each count. Say once which tags make up a topic in Facts & rules. The volume drivers playbook shows the steps.
Why it's hard
Office hours or clock hours, bots counted or not: every choice changes the number, and a chart can only show the one it was built with.
With Querri
Write your definition down once and track first response time as a KPI by team, using Teams and Admins from Intercom. History builds from the day you start. The first response time playbook covers the setup.
Why it's hard
Conversation counts live in Intercom and revenue lives in billing or the CRM. Nobody can rank accounts by support load per dollar without an export and a lookup.
With Querri
Connect Salesforce or QuickBooks next to Intercom. In the Library, each Intercom company is paired with a paying customer, the answer names the fields used for the pairing, and any doubtful pair gets a caveat.
Why it's hard
Product usage sits in a warehouse and conversations sit in Intercom. A customer whose logins fall while their tickets rise looks fine in each system on its own.
With Querri
Bring usage from BigQuery or Snowflake beside Intercom conversations and score each account. The health score playbook walks through the weighting.
Why it's hard
A spike in one topic is easy to see after the fact and easy to miss on the day, because the overall total barely moves.
With Querri
Track daily conversations per topic as a KPI, and monitors hold each one up against its own history every night using plain arithmetic. A topic that jumps is waiting in your Inbox the next morning.
Why it's hard
Tickets, ticket types and the teams that own them are separate lists. Seeing the backlog by type and age means stitching them together by hand.
Why it's hard
Every Monday someone exports datasets, rebuilds the pivot tables and pastes the charts into a deck. The formatting breaks the moment it's forwarded.
With Querri
Set the review up one time with a delivery schedule. On each run Querri works from the latest Intercom sync and sends a formatted Excel workbook, an email or a deck, with one version per team if you want. See reports and automation for the options.
Why it's hard
An assistant handed a CSV decides for itself what a resolved conversation is. Ask twice and the answer can change.
With Querri
Connect Claude or ChatGPT to Querri. The assistant answers from your Library, with your definitions of response time and resolution, and each person sees only the rows their Querri access allows.
Intercom plus the rest
Intercom knows who wrote in and why. Billing knows what they pay, the CRM knows when they renew, and the warehouse knows whether they still use the product. Querri lines them up in one Library, so a question about a customer gets the whole customer.
Intercom pairs well with
Answers you can stand behind
First response time measured around the clock and first response time measured in office hours are both honest, and they can be hours apart. Querri picks the one your rule names, labels it, and shows the second figure too, so Monday's review argues about the queue and not the stopwatch. Read how Querri works out an answer.
Wake up to what changed
Overnight Querri measures each topic, team and channel against its own past and looks for the slice nobody is watching. Anything it turns up sits in your Inbox when you log in, and nothing is changed unless you approve it.
Custom Intercom dashboards
Tell Querri what the support review should show, or hand it a screenshot of the Intercom report you look at now as a starting point. Charts can put conversations next to revenue and usage, edits are requests in plain words, and each team lead can be limited to their own team's rows.
Reports you can stop rebuilding
Which topics generate the most conversations, and which customers write in about the same thing twice.
Read the playbookResponse time on your own definition, broken out by team and teammate, with history from the day you start.
Read the playbookSupport load, usage and billing combined into one score per account, without a CS platform.
Read the playbookAccounts renewing soon whose conversations are climbing or whose tickets sit open.
Read the playbookEach account's conversations, open tickets and top topics for the quarter, ready to drop into the review.
Read the playbookVolume, backlog by ticket type and response times, sent every Monday as email or a workbook.
See reportsWhat comes over
After you connect, choose the objects to sync and Querri copies them into your Library. Contacts and companies arrive with their standard attributes. What Querri can read is set by the permissions on its app in your Intercom workspace.
All 24 objects
Each sync rereads every object you picked, on a daily, weekly or monthly schedule or by hand, so records deleted in Intercom drop out too. There is no incremental sync for Intercom.
Records are written to disk page by page, up to 10 objects sync at once, and Querri slows down and waits whenever Intercom asks it to. Objects read one contact at a time take longer.
Querri only reads from Intercom. It never sends a message, closes a conversation or edits a contact, company or ticket.
You sign in to Intercom and authorize Querri's app. There is no access token or API key to copy, and the Connector Agent never handles one.
How to connect Intercom
Type "connect our Intercom" to the Connector Agent on the Connect page, or find Intercom in the catalog.
Sign in to Intercom and approve Querri's app. No access token or API key changes hands.
Choose from 24 objects, from conversations and tickets to tags, teams and help center articles.
Nothing is copied until you approve it. Then choose a daily, weekly or monthly refresh.
Once the first sync finishes, ask about conversations, tickets and contacts, or build a dashboard or report on them.
Intercom FAQ
Ask the Connector Agent on Querri's Connect page to set up Intercom, or select Intercom in the catalog. Sign in to Intercom and authorize Querri's app, choose the objects you want from the list, then approve the load and a sync schedule. You never paste an access token or API key.
Up to 24 objects: contacts, companies, conversations, articles, tickets and ticket types, help centers and collections, teams, admins, tags, segments, data attributes, brands and more, plus per-contact notes, tags, segments and companies, and data events. News items and newsfeeds come over when your Intercom plan includes News.
On the schedule you choose: daily, weekly or monthly, and you can start a sync by hand any time. Every Intercom sync is a full refresh that rereads the objects you picked, so deleted records drop out. Querri doesn't offer incremental syncs for Intercom.
No. Querri only reads from Intercom. It never replies to a customer, closes or reassigns a conversation, or edits a contact, company, ticket or article. Questions run on the copy in your Querri Library, so nothing in your Intercom workspace changes because you connected it.
Querri can read only what its app is permitted to read in your Intercom workspace. If a permission is missing, Querri tells you to turn it on in Intercom's Developer Hub and reconnect. Once the data is in Querri, Intercom teammate roles stop applying: Querri's own sharing and row-level access decide which rows each person sees.
No. Querri copies Intercom data on your schedule and answers from that copy, so results reflect the last sync. For a meeting that needs this morning's conversations, run a manual sync first. Because each Intercom sync rereads everything, a large workspace takes longer to refresh.
Connect both, and Querri matches Intercom companies to Salesforce accounts in the Library. Then ask which accounts renewing this quarter have rising conversation volume, or how support load compares with account value. If a pairing depends only on two company names looking alike, the answer flags it.
Connect both and Querri lines up Intercom contacts and companies with HubSpot records, usually by email and domain. You can see conversations by lifecycle stage, or which open deals have a customer waiting on support. Tell Querri once how the records correspond and every answer uses that rule.
Connect the warehouse or database that holds usage, such as Snowflake, BigQuery or PostgreSQL, alongside Intercom. Querri joins usage to Intercom contacts or companies, so you can find accounts whose activity is falling while their conversations climb, and track a health score with its history kept.
Sync conversations, teams and admins, then say once how first response time should be measured, for example office hours only. Querri tracks it as a KPI by team and teammate and keeps its history from the day you start. The first response time playbook shows the full setup.
Ask which topics drove volume this month. Querri reads conversations and tags, merges tags that mean the same thing, says how much that changed the counts, and compares each topic with its own history. Monitors can then watch every topic nightly and flag the one that spikes.
Yes. Your Intercom plan has no bearing on what you can build in Querri. Ask for the charts you want, or begin from a screenshot of a current report, and request changes in plain words. It can mix Intercom with billing, CRM and usage data, and each team lead can be limited to their team's rows.
Save the report as a Querri project and attach a schedule. Each time the schedule fires, Querri reruns the project on the latest synced data and emails a formatted Excel workbook, split into one version per team, region or client if you like. Nobody downloads a dataset or rebuilds pivot tables by hand.
Yes. After a one-time setup through Querri's MCP connection, Claude or ChatGPT reads from your Querri Library: it uses the response time, resolution and topic definitions you wrote down, and each person gets only the rows their Querri access allows. The figure in Claude matches the one on your support dashboard.
Not in full. Each conversation comes over with up to 20 of its message parts, and longer threads are cut off. There is no separate conversation parts object, so Querri suits counts, timings, topics and assignments better than a complete message-by-message history.
Data events cover only the last 90 days, for users and leads. The other objects have no such date window, though each conversation still stops at 20 message parts. If you need event history longer than 90 days, track the counts you care about as a KPI, which keeps its history in Querri.
Not today, as far as we can confirm. Querri connects to Intercom's US region, and it has no setting for EU or Australian data hosting. If your workspace is hosted outside the US, talk to us before you connect so we can check what will work.
Most objects page through quickly, but contact notes, contact tags, contact segments, contact companies, company segments and data events are read one contact or company at a time. On a workspace with many contacts those take longer, so pick them only when you need them.
Querri is SOC 2 Type II, HIPAA and ISO 27001:2022 certified, and your data is never used to train a model. You authorize Querri inside Intercom, so no token is pasted anywhere, and Querri only ever reads your workspace data.
Keep exploring
Authorize it in a few minutes. Querri only reads your data and never changes a conversation.