PyAI x Zendesk
Every call opens a ticket with the summary already written.
The support queue problem was never answering calls; it is writing them up. PyAI opens a Zendesk ticket for every completed call: the TL;DR is the subject, the summary and next steps are the first comment, and tags mark it as a PyAI recap or AMD outcome so your views and triggers can route it.
- Status
- Live
- Direction
- PyAI to Zendesk
- Setup
- Console, no code
- Cost
- Included
What lands in Zendesk
One ticket per call, tagged so your existing views pick it up. The agent's TL;DR reads as the subject, and the full recap is the first comment.
The ticket after a rescheduling call
Ticket
Subject: Customer asked to reschedule Friday's installation
Tags: pyai, recap
First comment:
The customer called to move their appointment. The agent offered
Tuesday or Wednesday morning; the customer chose Wednesday 9-11am
and asked for a text reminder the day before.
Next steps: Confirm the new slot by SMS and update the calendar invite.Setup, end to end
- 1
In Zendesk Admin, open Apps and integrations, then API, and create an API token.
- 2
In the PyAI console, open Integrations and choose Zendesk, then enter your account host, agent email, and token.
- 3
Press Test to open a sample ticket and check it against your views.
- 4
From the next completed call, tickets open automatically.
Delivery you can prove
Verified, and never twice
Every delivery carries proof it is really from us (the X-PyAI-Signature header, an HMAC your tools can verify) and a unique receipt id (the Idempotency-Key), so a retry can never post the same call twice.
Retried, then shown to you
If your endpoint hiccups, we retry with backoff (eight attempts over about twenty minutes). Still failing? The exact error waits on the integration card in your console, not in a log you never read.
Your credentials stay yours
Tokens, secrets, and webhook URLs are encrypted at rest and masked everywhere. They never appear in the messages we send.
Included, no extra fees
Integrations come with your Recap or AMD usage. There is no per-connection or per-delivery charge.
FAQ
Can tickets flow into my existing Zendesk views and triggers?
Yes. Every ticket is tagged pyai plus recap or amd, so a view filtered on those tags collects them and your triggers can assign, escalate, or auto-close as you like.
What does an AMD ticket look like?
The subject carries the verdict and confidence (for example, human at 97%), and the comment holds the reason, session label, and call reference. Useful for reviewing how outbound campaigns are being answered.
Who is the ticket requester?
Tickets are created with your agent credentials, so the requester defaults to that agent. If you want tickets modeled differently, route them through the Zapier integration instead and shape them in a Zap.
What does the Zendesk integration cost?
It is included with your Recap usage. There is no per-ticket or per-connection fee from PyAI.
Connect Zendesk to PyAI today.
An instant sandbox key lets you test every delivery without billing. Create an account when you want saved projects, and fund a live key for production traffic.
Agents is live in beta. Sandbox keys have daily limits and never touch billing.