01
SLA tracking
First reply and resolution against SLA, by plan, channel and priority.
SLA breach %
Support
Zendesk + Kimo
Tickets, satisfaction and agent metrics from Zendesk, joined to accounts and revenue to measure support cost per customer.
- Auth
- OAuth 2.0
- Sync
- Hourly
- Setup
- ≈ 2 min
Live demo workspace with fictional data · no signup, no credentials needed
kimo / connectors / zendeskSyncing
Sync loghourly
- Succeeded:tickets+1,400 rowsnow
- Succeeded:satisfaction_ratings+619 rows2m ago
- Succeeded:ticket_metrics+2,238 rows4m ago
- Succeeded:tickets+1,457 rows6m ago
Rows synced · 30 days
86.8M
Workspaces
14%
What you can do
What teams build with Zendesk
Zendesk on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.
02
Cost to serve
Tickets and agent time per account, compared with what each account pays.
Tickets / $1k MRR
03
Churn early warning
Rising ticket volume plus falling CSAT flags accounts before renewal.
Risk score
Objects & tables
Exactly what gets synced
Kimo maps Zendesk into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.
3 tables · 12 fields
Tables
tickets
Incremental≈ 492,000 rows| Field | Type | Notes |
|---|---|---|
| id | id | Primary key |
| status | enum | Low-cardinality dimension |
| priority | integer | Measure |
| via_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 Zendesk tables to a certified metric
This model ships with the Business Intelligence demo. Open it to see every join and measure.
Customer support
Zendesk tickets joined to accounts: volume, SLA and CSAT by plan.
- Zendesktickets
- MySQLorganizations
Model
org_id = id
Measuresticketsfirst_responsecsat
Tickets · last 30 days
169+2.0% wk/wk
Fictional data · hover the chart for daily values
Setup
Connect Zendesk 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 Zendesk”
You are redirected to Zendesk 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 Zendesk
Step 2 of 3 · Kimo demo workspace
Kimo wants read-only access to your Zendesk account
read-only accessread
Accounts
- Northwind · Zendesk
- Northwind EU · Zendesk
Read-only access
Illustration only · placeholder values, never real secrets
Works great with
Pair Zendesk with the rest of your stack
Kimo suggests these joins automatically when both sources are connected.
FAQ
Zendesk questions, answered
By default Kimo syncs Zendesk hourly. You can change the schedule per table, or trigger a sync manually from the connector page.
Zendesk · OAuth 2.0 · Hourly
See your Zendesk data in Kimo in 2 min.
Try it on the live demo workspace first, then connect your own account when you are ready.