{"site":{"name":"Koji","description":"AI-native customer research platform that helps teams conduct, analyze, and synthesize customer interviews at scale.","url":"https://www.koji.so","contentTypes":["blog","documentation"],"lastUpdated":"2026-07-09T17:30:58.344Z"},"content":[{"type":"documentation","id":"5a71a601-1235-46ec-9baf-63a143fa03bf","slug":"zendesk-research-integration","title":"Zendesk + Koji: Trigger AI Interviews from Support Tickets and Sync Insights Back to Every Conversation","url":"https://www.koji.so/docs/zendesk-research-integration","summary":"The Koji + Zendesk integration is bidirectional and needs no native app. From Zendesk into Koji: a native Zendesk trigger fires a webhook to Koji's Start Interview endpoint when a ticket is solved, CSAT is low, or a tag like churn-risk is applied, sending the requester a personalized AI interview link. From Koji back into Zendesk: on analysis_ready, a forwarder calls the Zendesk API to add an internal note with top themes, sentiment, quality score, and a transcript URL to the original ticket, and applies insight/sentiment tags. Three setup paths exist: native Zendesk trigger + webhook, no-code Zapier, or direct headless API. Identity resolves via requester email (respondent_email) or the Zendesk user ID (respondent_id); anonymous-mode studies skip the write-back. Studies use Koji's six structured question types so a single_choice root-cause question maps to your ticket taxonomy. Webhooks/API are on the Interviews plan (EUR79/mo) and Enterprise; Zapier and CSV import work on any plan.","content":"# Zendesk + Koji: Turn Support Tickets Into AI Interviews That Explain the Root Cause\n\n**Answer first:** A Zendesk ticket tells you a customer had a problem; it rarely tells you *why the problem mattered, what they expected, or whether they are now a flight risk*. Koji closes that gap. The integration is bidirectional: (1) a Zendesk **trigger + webhook** fires a Koji AI-moderated interview when a ticket is solved, a CSAT rating comes in low, or a specific tag is applied, and (2) when the interview is analyzed, Koji posts a concise insight summary back onto the ticket (or the requester's user record) as an **internal note and tags** — sentiment, top themes, quality score, and a transcript link. No native Zendesk app is required: Zendesk's trigger/webhook system plus Koji's headless API and HMAC-signed webhooks do all the work, and a Zapier path exists for no-code teams. A first version is live in well under an hour.\n\nThe result is a support org that does not just resolve tickets — it systematically learns from them, at a scale no manual QA or callback program can match.\n\n## Why connect Zendesk and Koji\n\nSupport conversations are the largest, most honest stream of customer signal most companies own — and the least mined. The ticket text captures the *symptom* (\"export is broken\") but almost never the *stakes* (\"I nearly cancelled because I present this to my CEO every Monday\"). Traditional follow-up options are weak: a one-question CSAT survey with no depth, or an agent-initiated callback that does not scale past a handful a week.\n\nKoji's AI moderator interviews the customer conversationally, asks adaptive follow-up questions, and works in voice or text across 50+ languages — so you can follow up on hundreds of tickets a week without adding headcount. With platforms like Koji, every resolved ticket can become a two-minute \"what really happened\" interview, and every low CSAT score can trigger an immediate, structured root-cause conversation instead of a lost customer.\n\n## What flows in each direction\n\n### Zendesk → Koji (trigger interviews from ticket events)\n- A Zendesk **trigger** fires on an event you choose (ticket solved, CSAT = bad, tag `churn-risk` added, priority = urgent escalated).\n- The trigger's **webhook** calls Koji's [Start Interview endpoint](/docs/starting-interviews-via-api) with the requester's email as `respondent_email` and the ticket ID as a custom field.\n- Koji sends the customer a personalized interview link (email or embed), moderates it, and analyzes it automatically.\n\n### Koji → Zendesk (insights land back on the ticket)\n- On `analysis_ready`, Koji's webhook posts to your forwarder.\n- The forwarder calls the **Zendesk API** to add an internal note to the original ticket (or the user) with the top themes, sentiment, quality score, and transcript URL, and to apply tags like `insight:pricing-confusion` or `sentiment:frustrated`.\n- Agents and CX leads see the \"why\" attached to the very ticket that prompted it.\n\n## Ticket events worth interviewing\n- **Solved tickets** — a lightweight \"did we actually fix the underlying job?\" check.\n- **Low CSAT / detractor ratings** — an immediate, structured root-cause interview while it is fresh (see [churn interview questions](/docs/churn-interview-questions)).\n- **Churn-risk or cancellation tags** — route straight to a [cancel-flow exit interview](/docs/cancel-flow-exit-interview).\n- **Feature-request tickets** — probe the underlying need, not just the asked-for feature.\n- **Repeated escalations** — understand the cumulative frustration a single ticket hides.\n\n## Setup: three paths\n\n**1. Native Zendesk trigger + webhook (recommended).** In Zendesk Admin, create a **webhook** pointing at Koji's Start Interview endpoint (with your API token), then a **trigger** whose conditions match the event and whose action calls that webhook with the requester email. For the return leg, register a Koji webhook that hits a tiny forwarder calling the Zendesk API. Clean and fully native.\n\n**2. No-code with Zapier.** Use the Zendesk Zapier trigger (\"New Ticket\" / \"Ticket Solved\") to fire Koji's \"Start Interview\" action, and a second Zap on Koji's webhook to run Zendesk's \"Add Comment\" action. Zero code — see [Connect Koji to Zapier](/docs/zapier-research-automation).\n\n**3. Headless API from your own middleware.** If you already run a support-automation service, call Koji's [headless API](/docs/headless-api-overview) directly and subscribe to its [webhooks](/docs/webhook-setup).\n\n## Design the interview so it maps to your taxonomy\n\nKoji's **structured questions** make the returned data align with how your CX team already thinks. A study can mix six types — `open_ended`, `scale`, `single_choice`, `multiple_choice`, `ranking`, and `yes_no` — so a `single_choice` \"which best describes the root cause?\" maps directly to your ticket-reason taxonomy, while `open_ended` probes capture the story. See the [structured questions guide](/docs/structured-questions-guide). Every quantitative answer aggregates into a [real-time report](/docs/real-time-research-insights) you can watch fill in as interviews complete.\n\n## Example: turning CSAT detractors into a save motion\n1. Zendesk trigger: CSAT rating = *bad* → webhook to Koji.\n2. Koji sends a 3-minute interview: one `single_choice` root-cause question, two `open_ended` probes, one `scale` \"how likely are you to keep using us?\"\n3. On completion, Koji tags the ticket `sentiment:at-risk` and posts the summary as an internal note; a second automation alerts the account owner in Slack.\n4. CX now has a ranked, themed view of *why* CSAT dips — and a triggered save conversation for every detractor.\n\n## Identity and privacy\nMatch on the requester's **email** (`respondent_email`) or pass the Zendesk user ID as `respondent_id`; the same key returns on the webhook so notes land on the right ticket. For sensitive topics, run the study in **anonymous mode** — Koji collects no email and you skip the Zendesk write-back, keeping raw transcripts out of the helpdesk.\n\n## Plans and limits\nWebhooks and the headless API are included on the **Interviews plan (EUR79/month, 79 credits)** and **Enterprise**. The **Insights plan (EUR29/month)** does not include webhooks, but the Zapier and CSV-import paths still work. One completed interview consumes one credit.\n\n## The insight note Koji writes back\n\nWhen an interview is analyzed, the internal note Koji posts on the ticket is designed to be skimmable by a busy agent. A typical note includes the overall sentiment, the two or three ranked themes, the answer to each structured question, the interview quality score, and a link to the full transcript. Tags such as `insight:onboarding-gap` and `sentiment:at-risk` are applied to the ticket and the requester, so you can build Zendesk views and reports around them — for example, a view of every \"at-risk\" customer surfaced by a follow-up interview this week.\n\n## Common pitfalls (and how to avoid them)\n- **Triggering on every ticket.** Volume kills goodwill. Gate interviews to the moments that carry real signal — bad CSAT, cancellation tags, complex solved issues — and cap frequency per requester.\n- **Asking what the ticket already answered.** Do not re-ask the reported issue. Use the interview to probe stakes, expectations, and alternatives considered, which the ticket never captures.\n- **Letting insights die in a note.** Route the highest-severity findings (negative sentiment plus a high quality score) to Slack or a weekly CX review so they drive action, not just documentation.\n- **Ignoring language.** Koji moderates in 50+ languages; set the study language from the ticket's locale so international customers get a native-language interview.\n\n## From tickets to a continuous voice-of-customer program\n\nHandled this way, Zendesk stops being only a cost center and becomes your largest research panel. Every week, solved tickets and CSAT detractors feed a themed, quantified stream of root-cause insight — the kind of signal product and CS leaders usually pay agencies for. Because Koji analyzes each interview automatically and aggregates structured answers into a live report, the CX team gets a standing \"why customers contact us\" dashboard without running a single manual study, and every new theme is traceable back to the exact ticket and transcript that produced it.\n\n## Related Resources\n- [Intercom + Koji](/docs/intercom-research-integration)\n- [Research Automation with Webhooks](/docs/research-automation-webhooks)\n- [Structured Questions in AI Interviews](/docs/structured-questions-guide)\n- [Churn Interview Questions](/docs/churn-interview-questions)\n- [Customer Success Interview Guide](/docs/customer-success-interview-guide)\n- [Understanding Themes & Patterns](/docs/understanding-themes-patterns)","category":"API Reference","lastModified":"2026-07-09T03:24:55.44634+00:00","metaTitle":"Zendesk + Koji Integration: AI Interviews From Support Tickets","metaDescription":"Trigger Koji AI interviews from Zendesk ticket events like solved tickets and low CSAT, then post themes, sentiment, and transcript links back onto the ticket automatically.","keywords":["zendesk koji integration","ai interviews from support tickets","zendesk webhook research","csat root cause interview","support ticket customer research","zendesk trigger interview","helpdesk voice of customer"],"aiSummary":"The Koji + Zendesk integration is bidirectional and needs no native app. From Zendesk into Koji: a native Zendesk trigger fires a webhook to Koji's Start Interview endpoint when a ticket is solved, CSAT is low, or a tag like churn-risk is applied, sending the requester a personalized AI interview link. From Koji back into Zendesk: on analysis_ready, a forwarder calls the Zendesk API to add an internal note with top themes, sentiment, quality score, and a transcript URL to the original ticket, and applies insight/sentiment tags. Three setup paths exist: native Zendesk trigger + webhook, no-code Zapier, or direct headless API. Identity resolves via requester email (respondent_email) or the Zendesk user ID (respondent_id); anonymous-mode studies skip the write-back. Studies use Koji's six structured question types so a single_choice root-cause question maps to your ticket taxonomy. Webhooks/API are on the Interviews plan (EUR79/mo) and Enterprise; Zapier and CSV import work on any plan.","aiPrerequisites":["A Koji account with API access on the Interviews or Enterprise plan","A Zendesk account with admin access to create triggers and webhooks","Familiarity with webhooks or Zapier"],"aiLearningOutcomes":["Trigger Koji AI interviews from Zendesk ticket events","Post interview insights back onto the originating ticket as notes and tags","Map structured interview answers to your ticket-reason taxonomy","Build a triggered save motion for CSAT detractors"],"aiDifficulty":"intermediate","aiEstimatedTime":"12 min read"}],"pagination":{"total":1,"returned":1,"offset":0}}