How to connect Zendesk to AskVault

Written by Aashiq, Founder, AskVault · Reviewed by Aashiq

Last updated: May 15, 2026 · 4 min read

What this integration does

Two distinct flows you can enable, separately or together:

Knowledge ingestion. Your Zendesk Help Center articles become a knowledge source. The AskVault bot retrieves from them when answering customer questions. Auto-syncs daily.
Ticket routing. When the bot escalates, the ticketing_router skill creates a Zendesk ticket with the full chat transcript attached, routed to the right team queue.

Knowledge ingestion is on Starter and above. Ticket routing is also on Starter. Starter+

Setup

Five minutes for both flows.

Open Knowledge > Add Source > Zendesk in AskVault. Click Connect with Zendesk.
Enter your Zendesk subdomain. Format: yourcompany.zendesk.com. AskVault auto-detects the OAuth endpoint.
Sign in to Zendesk. Approve the requested scopes: read (for articles and tickets) and write (for ticket creation).
You're redirected back to AskVault. Connection shows active.
Configure ingestion sources. Pick which Help Center sections to ingest, sync cadence (daily, weekly, manual). For ticket routing, map Zendesk groups to AskVault intent tags under AI Agents > Skills > ticketing_router > Intent Mapping.

Test by asking the bot a question whose answer lives in your Help Center. The bot should retrieve and respond with a citation. Then trigger an escalation; verify the ticket lands in your Zendesk queue.

Scopes requested

read (Help Center articles, tickets, users, groups).
write (create tickets, add comments, set group assignment).

Read-only mode is available if you only want knowledge ingestion without ticket creation. Configure under Integrations > Zendesk > Permission Mode.

Help Center ingestion

Zendesk Help Center articles ingest as standard knowledge documents. The integration:

Walks every article in the sections you configured.
Extracts the article body, title, and metadata.
Chunks into pieces of 400 to 800 tokens.
Embeds and stores in your workspace's vector index.

Bot retrievals cite the original Help Center article URL so visitors can click through to read more.

For multilingual Help Centers, AskVault ingests every language version as a separate document. Bot retrieves the version matching the conversation's language.

Ticket routing

When the bot escalates to a human, ticketing_router creates the ticket. The ticket includes:

Subject. Auto-generated from conversation intent.
Requester email. From the customer (captured via collect_lead or identity verification).
Description body. Full conversation transcript, formatted for readability.
Tags. askvault, intent (billing, technical, returns, etc.), source channel (widget, whatsapp).
Priority. Default normal. Bumps to urgent if sentiment_router flagged the conversation.
Group. From your intent mapping. Billing intent goes to the Billing group; Technical goes to Engineering, etc.

SLA timers fire automatically per your Zendesk SLA policies.

Reverse routing (Zendesk replies back to chat)

For continuity, you can route Zendesk agent replies back to the customer in their original chat channel. Setup:

In Zendesk, create a trigger that fires on "Ticket is updated with public comment".
The trigger calls AskVault's webhook URL (visible under Integrations > Zendesk > Reverse Route).
AskVault routes the reply to the customer's chat channel.

For most teams, Zendesk's default email reply is fine. Reverse routing matters when customers expect chat-native responses.

Multi-brand Zendesk

Zendesk Multi-Brand setups (different Help Centers for different product brands) need careful configuration. Two patterns:

Per-brand AskVault workspace. Each brand gets its own AskVault workspace connected to that brand's Zendesk subdomain. Cleaner separation.
Single workspace with brand filter. One workspace, ingest articles from multiple brands, filter by brand metadata at retrieval time. More complex but fewer workspaces.

For most teams the per-brand workspace pattern is right.

Limits

Zendesk API rate limits. 700 requests per minute on Enterprise. Lower on Professional. AskVault stays well under these.
Help Center article cap. No hard cap, but Help Centers with 5,000+ articles take 15 to 30 minutes for initial ingestion.
Ticket creation rate. 200 tickets per minute via the API. Enough for any normal support volume.

Common pitfalls

Help Center articles ingest but the bot doesn't cite them. Articles haven't finished indexing. Check Knowledge Hub > Zendesk > Status. Wait for the progress bar.

Tickets create in the wrong queue. Intent mapping is misconfigured. Test individual intents under Skills > ticketing_router > Test Mode.

Customer email missing on ticket. collect_lead didn't capture the email. Configure ticketing_router to require email before creating the ticket.

Duplicate tickets. Customer mentioned "ticket" multiple times. Enable dedup under Skills > ticketing_router > Deduplicate.

FAQ

Does this work with Zendesk Suite?

Yes. The integration uses Zendesk Support APIs which are part of every Suite plan.

Can I route to Zendesk Chat instead of Zendesk Support?

Zendesk Chat (now Zendesk Messaging) is a different product than Support. AskVault routes to Support (creates tickets). For chat-to-chat handoffs, use the Live Chat inbox directly.

How does AskVault distinguish AI-generated and human-agent replies in Zendesk?

AI-generated replies are tagged with askvault-ai-reply. Human-agent replies (from your Zendesk team) are normal Zendesk replies. Easy to filter in Zendesk reports.

Can the bot escalate to Zendesk Sell?

Not natively. Zendesk Sell is the CRM product; AskVault routes to Support (the ticketing product). For CRM-style flows, use the HubSpot or Salesforce integrations.

Will this interfere with my existing Zendesk Answer Bot?

No. They're independent. You can run Answer Bot and AskVault side by side; most teams turn off Answer Bot once AskVault is live because AskVault is grounded in your full knowledge base rather than just the Help Center.

Was this page helpful?