01
Response times that matter
First reply and resolution time broken down by plan, so your biggest accounts get priority.
p90 first reply
Support
Intercom + Kimo
Conversations, CSAT and response times. Connect support load to accounts and revenue, and spot churn risk before it reaches the renewal call.
- Auth
- OAuth 2.0
- Sync
- Hourly
- Setup
- ≈ 2 min
Live demo workspace with fictional data · no signup, no credentials needed
kimo / connectors / intercomSyncing
Sync loghourly
- Succeeded:tickets+945 rowsnow
- Succeeded:agents+1,726 rows2m ago
- Succeeded:ticket_metrics+107 rows4m ago
- Succeeded:tickets+888 rows6m ago
Rows synced · 30 days
121.7M
Workspaces
23%
What you can do
What teams build with Intercom
Intercom on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.
02
Support cost per account
Join tickets with revenue to see which customers cost more to serve than they pay.
Tickets / $1k MRR
03
Churn early warning
Flag accounts with rising ticket volume and falling CSAT ahead of renewal.
Risk score
Objects & tables
Exactly what gets synced
Kimo maps Intercom into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.
3 tables · 13 fields
Tables
tickets
Incremental≈ 28,100 rows| Field | Type | Notes |
|---|---|---|
| id | id | Primary key |
| status | enum | Low-cardinality dimension |
| priority | integer | Measure |
| channel | enum | Low-cardinality dimension |
| created_at | timestamp | Incremental cursor |
Custom fields and extra objects are discovered automatically on each sync. Row counts are illustrative.
Sample model
From raw Intercom tables to a certified metric
A starter model Kimo suggests the moment Intercom is connected. Every join is editable.
Intercom · Support load
Tickets and satisfaction joined with accounts and MRR.
- Intercomtickets
- MySQLcustomers
- Stripesubscriptions
Model
requester_email · account_id
Measuresticketsfirst_reply
Tickets · last 30 days
285-0.9% wk/wk
Fictional data · hover the chart for daily values
Setup
Connect Intercom in 2 min
No engineers, no pipelines to maintain. Kimo asks for the minimum access it needs and tells you exactly what it will read.
- 1
Click “Connect Intercom”
You are redirected to Intercom to sign in. Kimo never sees your password.
- 2
Approve read-only scopes
Kimo requests the narrowest scopes available. You can revoke access at any time.
- 3
Pick accounts
Choose which accounts to sync. Add more later without reconnecting.
- 4
First sync and schema mapping
Kimo backfills history, maps tickets and suggests joins with your other sources.
Read-only, encrypted, revocable. Credentials are encrypted with a per-workspace key, never logged, and can be rotated without breaking your models.
Connect Intercom
Step 2 of 3 · Kimo demo workspace
Kimo wants read-only access to your Intercom account
read-only accessread
Accounts
- Northwind · Intercom
- Northwind EU · Intercom
Read-only access
Illustration only · placeholder values, never real secrets
Works great with
Pair Intercom with the rest of your stack
Kimo suggests these joins automatically when both sources are connected.
FAQ
Intercom questions, answered
By default Kimo syncs Intercom hourly. You can change the schedule per table, or trigger a sync manually from the connector page.
Intercom · OAuth 2.0 · Hourly
See your Intercom data in Kimo in 2 min.
Try it on the live demo workspace first, then connect your own account when you are ready.