A support question isn't always meant to be answered on the spot. Sometimes the right outcome isn't AIVA resolving something — it's AIVA recognising that it shouldn't try, and making sure the right team gets it with everything they need to act. That's what the Zendesk integration is actually for.
Resolution isn't always the goal
It's tempting to measure an AI support agent purely on how much it resolves without a human. We track that number too — AIVA resolves a large majority of what it handles across voice, chat, and SMS. But treating every unresolved conversation as a failure leads to the wrong behaviour: an AI that stretches to close out things that genuinely need a person, or one that quietly drops anything it can't finish.
The better outcome, for anything that needs an agent, isn't AIVA pretending to resolve it. It's AIVA opening a ticket that's actually usable.
What a ticket from AIVA contains
Connected to Zendesk, AIVA opens a ticket automatically when a conversation needs to go to your team — because the customer asked for a human, because the issue falls outside what AIVA is configured to handle, or because it hit an escalation trigger you've set. The ticket carries the full conversation, what was already tried, and any relevant account or booking details AIVA already pulled up before handing off.
A ticket that says "customer has a billing question" sends an agent hunting. A ticket with the transcript, the account, and the specific question already attached lets them open with an answer instead of "can you tell me more about the issue."
How urgency gets flagged
The same logic applies to priority. A conversation where a customer mentions a canceled appointment they're upset about shouldn't sit in the same queue as a routine follow-up question — AIVA flags urgency based on what it heard, so your team's queue is roughly triaged before anyone opens a single ticket. That flagging uses the actual content of the conversation, not just keywords — a customer calmly asking to reschedule reads differently from one who mentions they've already called twice with no callback, even if both technically mention "rescheduling."
What AIVA checks before opening a ticket
Before AIVA opens a new ticket, it checks whether the customer already has one open — using whatever identifying detail your Zendesk instance already relies on, typically the phone number or email the conversation came in on. That check exists for a specific reason: a customer who already has an open ticket about a delayed order and calls back for an update doesn't need a second ticket competing with the first for an agent's attention. Where an open ticket already exists for what looks like the same issue, AIVA adds the new conversation as a note on it rather than creating a duplicate — the way a returning email would customarily update an existing ticket rather than spawn a new one. Timing matters here too — this check happens before the ticket is created, not as a cleanup pass afterward, so an agent never sees the duplicate in the first place instead of having to notice and merge it later.
Where the new conversation is genuinely about something different — the same customer, an unrelated issue — AIVA opens a separate ticket, because merging two unrelated problems into one thread would just make the existing ticket harder for whoever's working it to parse.
What doesn't happen: AIVA doesn't touch a ticket's existing status, doesn't reassign it away from whoever it's currently sitting with, and doesn't override a priority an agent already set by hand. Once a human has taken a ticket somewhere, AIVA treats that as the current state of truth rather than a starting point to revise.
A ticket, start to finish
A customer calls to ask about a delayed order, and it turns out the delay is outside anything AIVA can check or resolve on its own. Rather than leaving the customer with a vague "someone will get back to you," AIVA explains that it's bringing in a team member, opens a Zendesk ticket tagged to the right group, attaches the order details already discussed, and lets the customer know roughly what to expect next. The agent who picks up the ticket sees exactly what the customer already said — no re-asking, no starting cold.
What happens if the same issue gets reported through two channels
A specific version of the above worth walking through: a customer emails support directly about a billing issue — bypassing AIVA entirely, straight into Zendesk the normal way — and then, not seeing a reply within an hour, also calls in and reaches AIVA about the exact same issue. Does that become two tickets an agent has to notice are the same thing and merge by hand?
Not if the identifying details line up. AIVA checks for an existing open ticket against the same customer before creating a new one, and an email that came in through Zendesk directly is visible to that check the same way a ticket AIVA itself opened earlier would be. Where AIVA can tell the call and the open ticket are about the same account, it adds the call as a note on the existing ticket rather than opening a second one an agent then has to reconcile.
Where it can't confidently tell — a customer who emails from one address and calls from a number not yet linked to that email in Zendesk — that's the genuine edge case, and it resolves the same way any support team already handles it when a customer reaches out twice through channels that don't obviously connect: an agent notices the overlap when they open either ticket and merges them by hand. AIVA reduces how often that happens by checking what it can; it isn't claiming to catch every case where a customer's two channels don't share an obvious identifier. That's a smaller gap than it might sound, since most customers reaching out twice about the same thing use the same phone number or email both times — the disconnected case is the exception, not the pattern this needs to handle well.
The alternative is worse than it looks
Without this, the fallback is usually one of two things: the customer gets bounced to a phone queue and has to explain everything again, or they file their own ticket, three sentences, no context, arriving cold. Both cost your team more time than a well-formed ticket AIVA opens the moment it recognises it should hand off. For more on how AIVA decides when a person needs to step in at all, see how handoffs work and how escalation rules get configured.
Considerations before you connect
Worth deciding before going live: how your existing Zendesk groups map to the kinds of conversations AIVA hands off — a billing question and a product issue probably belong in different groups, and getting that mapping right upfront saves a round of manual re-routing later. It's also worth deciding which escalation triggers are urgent enough to notify an agent immediately versus simply queue normally, so your team isn't paged for something that can wait until morning.
Setting it up
Connect your Zendesk account, decide which escalation triggers should open a ticket versus route to a live agent directly, and set which fields AIVA should populate — priority, group, tags. Most teams have this live within a setup session, alongside whatever triage rules Zendesk already has configured.
If your team is fielding tickets with no context attached, this is usually the fix. See it alongside similar options — Freshdesk, Intercom — in AIVA's other integrations, check pricing, or start free and connect Zendesk yourself.