Skip to content
AskVault Docs
Try Free →

Zendesk integration use cases

Written by , Principal Architect, Networks and Tech, AskVault · Reviewed by Allison Chan
Last updated: - 5 min read

1. Auto-create tickets when bot can't resolve

The most common pattern. When the bot escalates a conversation to a human (via escalate_to_human skill), a Zendesk ticket auto-creates with:

  • Subject line summarizing the issue (LLM-generated).
  • Full conversation transcript as the ticket body.
  • Customer email matched to a Zendesk requester (auto-created if new).
  • Tags mirroring AskVault tags.
  • Priority mapped from AskVault priority.
  • Custom fields populated from the conversation context.

Time saved: about 5 to 10 minutes of context-gathering per ticket. The agent picks up where the bot left off, no re-asking the customer for details.

2. Bidirectional reply sync (planned)

Routing a Zendesk agent's reply back into the customer's original AskVault channel — and syncing a customer's follow-up in AskVault back onto the ticket as a new comment — is on the roadmap and not yet available. Today the handoff is one-way: AskVault creates the ticket with full context, and the agent's reply reaches the customer through Zendesk's own channel (typically email) rather than the original chat surface.

3. Intent-based routing

The ticketing_router skill classifies the conversation and routes accordingly:

  • Refund-related -> Billing group.
  • Technical issue -> Engineering group.
  • Sales question -> Sales group.
  • General -> Tier 1 support.

Configure routing rules under AI Agents > Skills > ticketing_router > Routing. Up to 10 routes per workspace.

Routing accuracy: about 85 to 92% on typical conversations (varies by training data quality).

4. Auto-close low-effort tickets

For tickets the bot resolved in chat but pushed to Zendesk for record-keeping:

  1. Bot answers the customer's question.
  2. escalate_to_human skill is not triggered because the customer accepted the answer.
  3. AskVault creates a Zendesk ticket with status "Solved" and the resolution noted.
  4. Ticket appears in reporting but doesn't require agent action.

Useful for compliance teams that need a ticket for every customer interaction.

5. SLA enforcement via Zendesk macros

For teams using Zendesk's macro system:

  • AskVault sets initial ticket priority based on conversation context.
  • Zendesk macros enforce SLA-driven actions (urgent escalation, manager assignment) inside Zendesk from there.

Compose Zendesk-native workflows on top of AskVault's intelligent triage. (Syncing the macro's outcome back into the AskVault conversation is on the roadmap — see Planned features below.)

Field mapping

AskVault maps seven fields to Zendesk by default. The table below lists them.

AskVault fieldZendesk field
Conversation summaryTicket subject
Full transcriptTicket body (description)
Customer emailRequester email
ChannelTicket source (custom field)
TagsTags
PriorityPriority
Audience tagRequester's organization (if mapped)

Override per workspace under Integrations > Zendesk > Field Mapping. Add custom-field mappings for industry-specific data.

Status sync (planned)

Bidirectional status sync — where an AskVault conversation status maps to a Zendesk ticket status and changes on either side propagate to the other — is on the roadmap and not yet available. Today, status changes need to be made in each system separately.

Conversation-history-as-context

Beyond the current ticket, AskVault can pass:

  • Past resolved tickets for the same customer (from Zendesk).
  • Past chat conversations (from AskVault).

The bot uses this context to:

  • Detect recurring issues. "This is the third time this customer asked about login. Escalating to engineering for a fix."
  • Personalize replies. "Last time you contacted us, we discussed X. Following up on that?"
  • Inform the human agent. Ticket body includes a "Customer history" section.

Article suggestions to agents

When the bot partially helps but can't fully answer, it suggests Help Center articles to the human agent.

Suggested response (from Acme Help Center):

  1. Reset your password
  2. Two-factor authentication

Agent reviews and uses the suggestion or writes their own reply. Cuts reply time by about 30 to 50%.

Requires the ticketing_router skill plus AskVault indexed your Help Center pages (so it can recommend articles).

Setup walkthrough

About 30 minutes:

  1. Connect Zendesk via OAuth. See Zendesk integration setup.
  2. Pick the Zendesk subdomain and authenticate.
  3. Map ticket fields and routing rules.
  4. Enable the ticketing_router skill under AI Agents > Skills.
  5. Test by escalating a sample chat conversation.

Confirm the ticket appears in Zendesk within 30 seconds.

Webhook events

AskVault records the Zendesk ticket ID at creation time. Listening for ticket.updated, ticket.solved, and ticket.deleted events from Zendesk to sync agent replies, resolutions, and deletions back into the AskVault conversation is on the roadmap and not yet available (see bidirectional reply sync above).

Multi-Zendesk-instance workspaces

For Enterprise customers with multiple Zendesk instances (e.g., per region or per brand):

  • Connect multiple Zendesk subdomains to one workspace.
  • Route tickets by audience tag or channel.
  • Configure under Integrations > Zendesk > Instances.

Available on Business and above.

Plan availability

  • Free. No Zendesk integration.
  • Starter. Basic ticket creation. Starter+
  • Growth. Adds intent-based routing rules. Growth+
  • Business. Adds multi-instance, custom field mapping, history context. Business+
  • Enterprise. Custom integration work, scoped and quoted by sales. Note that AskVault single sign-on is not yet available on any plan, see team management.

Privacy and data flow

What AskVault sends to Zendesk:

  • Conversation transcripts when a ticket is created or updated.
  • Customer info (name, email, tags).
  • Custom field values per mapping.

What AskVault receives from Zendesk: nothing today beyond the API response confirming a ticket was created — AskVault doesn't yet listen for Zendesk-side reply, status, or tag changes (see Planned features above).

Both sides under your own data-processor agreements. Zendesk is a sub-processor of customer data; see sub-processors.

Sample workflow

End-to-end:

  1. Customer asks about a refund via widget chat.
  2. Bot answers the standard refund policy.
  3. Customer says "But I want my money back NOW."
  4. Sentiment skill detects frustration; bumps priority.
  5. escalate_to_human fires; ticketing_router classifies as Billing.
  6. Zendesk ticket creates with priority=high, group=Billing, transcript attached.
  7. Billing agent gets the ticket, reviews transcript in 30 seconds, replies.
  8. Reply reaches the customer through Zendesk's own channel (typically email) — chat-native reply sync is on the roadmap.
  9. Agent marks the ticket resolved in Zendesk.

Behind the scenes: AskVault hands off full context to Zendesk so the agent never has to re-ask the customer for details.

Planned features (on the roadmap)

Documented for accuracy:

  • Bidirectional reply and status sync. Today, ticket creation is one-way (AskVault to Zendesk); an agent's reply reaches the customer through Zendesk's own channel. Syncing agent replies and status changes back into the AskVault conversation is planned.
  • Zendesk AI integration. Today, AskVault and Zendesk operate independently. Native Zendesk AI plus AskVault co-pilot mode planned.
  • Ticket merge. Today, AskVault creates one ticket per conversation. Auto-merge of related conversations into one ticket planned.
  • SLA mirroring. Today, AskVault and Zendesk track SLA independently. Unified SLA view planned.

Limits

  • Tickets per workspace. No hard cap.
  • Custom field mappings. Up to 50.
  • Multi-instance connections. 5 on Business, unlimited Enterprise.

Common pitfalls

Ticket creation fails with "validation error". Required Zendesk field missing. Map or set default value.

Customer email mismatches. Same person uses two emails. Use Zendesk's contact-merge or AskVault's identity verification to unify.

Wrong routing group. Routing rule too permissive or too strict. Audit under Skills > ticketing_router > Routing.

FAQ

Does this work with Zendesk Suite?

Yes. All tiers of Zendesk supported via the Zendesk API.

Can I use Intercom instead?

Yes via Intercom integration. Similar capabilities.

Does AskVault replace Zendesk?

Not for teams with established Zendesk workflows. AskVault augments by handling the AI-resolvable conversations and routing the rest to Zendesk.

What happens to AskVault conversations when a Zendesk ticket is deleted?

AskVault conversations persist regardless of what happens to the linked Zendesk ticket — the conversation is reachable from AskVault directly either way. AskVault doesn't yet detect a Zendesk-side deletion automatically (see Planned features above).

Can I bulk-import historical conversations into Zendesk?

Yes via API. Loop through AskVault conversations and call Zendesk's create-ticket endpoint with the transcript.

Was this page helpful?