Native Zendesk integration

Zendesk Chatbot With AI Lead Sync and Ticket Handoff

Let an AI agent trained on your own content handle the first conversation, then pass contacts and escalations into the Zendesk account your support team already works in.

Last updated October 14, 2026 · By Samuel Su

What the integration does, in two sentences

When a visitor submits the lead form, Chat Data creates them as an end-user in Zendesk with their name, email and phone. When a conversation escalates to a human, Chat Data opens a Zendesk ticket containing the lead details, a link back to the live conversation, and the timestamped transcript.[*]

Everything before that point is handled by the agent: it answers from the documents, files and web pages you trained it on, on your website widget and on the messaging channels you connect. Setup takes three values, the Zendesk domain, an account email and an API token, and no code. The step-by-step reference lives in the Zendesk integration guide.

A real configuration, field by field

Here is the Zendesk panel filled in for a fictional company, Acme, whose agent is named Acme Help. These are the only inputs the panel has.

Panel fieldExample valueWhat to know
Zendesk Domainacme.zendesk.comPaste it with or without https:// — Chat Data keeps only the hostname before saving.
Zendesk Email[email protected]An address that signs in to that Zendesk account. Tickets the integration opens are created as this user.
Zendesk Token•••••••••••••••• (password field)An API token from Admin Center. The input is masked and is cleared after a successful save.

Clicking Connect does not just store the values. Chat Data immediately calls Zendesk's /api/v2/users/me endpoint with basic authentication in the email/token:api_token format Zendesk documents, so a mistyped domain or a token without API access fails on the spot instead of at the first escalation.[*] Once connected, the button changes to Update and a Disconnect option appears.

What appears in Zendesk afterwards

After a lead form submission

A new Zendesk user with the role end-user. For a visitor who typed “Dana Reyes”, [email protected] and a phone number, the profile carries exactly those three values.

{
  "name": "Dana Reyes",
  "email": "[email protected]",
  "phone": "+1 555 0100",
  "role": "end-user"
}

After an escalation

  • Subject: [Acme Help] Live Chat Escalation — the agent name in brackets
  • Agent details: The Chat Data agent ID and agent name
  • Lead info: The lead details collected for that conversation, such as name, email and phone, as a code block
  • Handling URL: A link that opens this exact conversation in the Chat Data live chat dashboard so a teammate can reply in real time
  • Chat history: The time the chat started (UTC), then every message with its UTC timestamp and who said it

Zendesk sets the requester of an API-created ticket to the authenticated user when none is given, which is why the ticket shows the connected email as requester and the visitor's details inside the body.[*]

Setting it up

1

Create an API token in Zendesk

You need admin rights. In Admin Center go to Apps and integrations, then APIs, and make sure API token access is turned on. Click Add API token, give it a description such as “Chat Data”, and copy the value right away: once you click Save, Zendesk only ever shows a truncated version.[*]

2

Give the agent something to send

Train the agent on your PDFs, docs and site pages, then enable the lead form and live chat on it. Ticket creation is part of the live chat escalation, so an agent with live chat switched off never opens a ticket. If your lead fields are required, a request for a person from the visitor or from the agent's live chat action waits until the visitor has filled them in, which is what puts real contact details in the ticket. A workflow Live Chat Escalation block escalates right away with whatever details the conversation already has.

3

Paste the three values and connect

Open the agent's Integrations tab, choose Zendesk, enter the domain, email and token from the table above, and click Connect. A green dot means Zendesk accepted the credentials.

4

Prove it with one test chat

Open the widget, submit the lead form with your own email, and ask for a person. In Zendesk you should find a new end-user and a ticket named after your agent. Click the handling URL in that ticket to confirm it lands on the right conversation.

Who handles which part of a conversation

Think of the agent as the front desk and Zendesk as the filing system. The agent answers questions about shipping, setup or billing policy straight from your material and asks for contact details at the point you configure. Routine conversations end there and never create a ticket.

Escalation can start three ways: the visitor clicks the button to talk to a human, the agent decides a question needs a person, or a workflow reaches a Live Chat Escalation block. In each case your usual escalation notifications fire and, with Zendesk connected, a ticket appears alongside them. A teammate opens the handling URL, picks up the chat in the live chat dashboard, and your Zendesk queue keeps a written record of every handoff for reporting.

Comparing Chat Data with running everything on Zendesk alone? See the Chat Data vs Zendesk comparison and our roundup of Zendesk alternatives.

Limits worth knowing before you connect

  • The connection is one-way. Chat Data writes users and tickets to Zendesk; it does not read tickets, macros or Help Center articles through the API.
  • Lead sync creates users only. An existing Zendesk profile is never edited.
  • Only name, email and phone go to the user profile. Custom lead fields stay with the lead in Chat Data.
  • Each agent has its own Zendesk connection, so two agents can point at two different Zendesk accounts.

Reviewed for Accuracy

Samuel Su

Founder & CEO

AI AgentsWorkflow AutomationSaaS ArchitectureCustomer Support AIProduct Strategy

Panel fields, credential check, user and ticket contents verified against the Chat Data Zendesk integration and its cookbook guide. Token, authentication, user-role and requester behavior checked against Zendesk's own help center and developer reference.

Last updated on October 14, 2026.

Frequently Asked Questions

Does the bot run inside the Zendesk widget?

No. Visitors talk to the Chat Data widget on your site, and Zendesk is where the results land: lead form submissions become Zendesk end-users and escalated conversations become Zendesk tickets. Many teams keep Zendesk for ticket tracking and put the Chat Data agent in front of it to absorb repetitive questions.

Where does my team reply to an escalated visitor?

From the handling URL inside the ticket, which opens the live conversation in the Chat Data dashboard. Because the ticket is created with the connected account, Zendesk records that account as the requester, so a public reply from Zendesk goes to your own address rather than the visitor. Use the ticket for assignment, tracking and reporting, and use the email in the lead info for any follow-up after the chat ends.

Which lead fields reach the Zendesk user profile?

Name, email and phone. The user is created with the end-user role; if the visitor skipped the name field the profile is named Unknown. Custom lead fields are not copied to the Zendesk profile; they stay with the lead in Chat Data.

Will it update customers who already exist in Zendesk?

No. The integration only creates users; it never edits an existing Zendesk profile. Keep changes to known customers in Zendesk itself.

Can the agent learn from my Zendesk Help Center?

Yes, if the Help Center is public: add its URL as a website source and the crawler indexes the articles like any other page. The Zendesk integration itself does not read tickets or articles; it only writes users and tickets.

What happens if the API token is deleted in Zendesk?

Chat Data can no longer write to Zendesk, so new leads and escalations stop appearing there, while any other escalation notifications you set up, such as email, still go out. Generate a new token, paste it into the panel and click Update.

Is the Zendesk integration allowed in a HIPAA workspace?

Yes. Zendesk is one of the destinations a HIPAA workspace can keep connected because, as of October 2026, Zendesk offers its own Business Associate Agreement for HIPAA-enabled accounts (see Zendesk's BAA page in the sources below). Chat Data shows a warning when you connect it: sign a BAA with Zendesk before any protected health information flows into tickets.

Put an agent in front of your Zendesk queue

Train it on your content, connect Zendesk with three values, and let only the conversations that need a person reach your team.

References

  1. [1]
    Zendesk Help Center: Managing access to the Zendesk API (2026-10-14)

    Zendesk admin guide to enabling API token access and generating API tokens in Admin Center.

  2. [2]
    Zendesk Developer Docs: Security and authentication (2026-10-14)

    Zendesk API authentication reference, including the email/token basic authentication format for API tokens.

  3. [3]
    Zendesk Developer Docs: Users API (2026-10-14)

    Zendesk Users API reference describing end-user, agent and admin roles and user creation endpoints.

  4. [4]
    Zendesk Developer Docs: Tickets API (2026-10-14)

    Zendesk Tickets API reference covering ticket creation, the first comment, and default requester behavior.

  5. [5]
    Zendesk: Business Associate Agreement (2026-10-14)

    Zendesk page for executing its HIPAA Business Associate Agreement, which provides HIPAA Enabled Accounts.