see why an urgent zendesk ticket keeps changing hands
see why an urgent ticket came back to your queue before you pass it on again. a zendesk bot in dusk can read the ticket, follow its assignment history and pull its service targets.
ask for the customer’s last question and the last action an agent took. keep both beside the ticket id.

what a bot can do in Zendesk
put the ticket history beside the current owner. the owner field tells you where the ticket sits now. an audit can show who held it earlier. the comments tell you what the customer has already tried.
| action | dusk bot treats it as | what you would use it for |
|---|---|---|
| Search Zendesk | read | find unsolved tickets marked urgent in the support queue |
| Get Zendesk Ticket | read | open the ticket a shift lead needs to assign |
| Get Ticket Comments | read | recover troubleshooting steps the customer already attempted |
| List Ticket Audits | read | follow the sequence of assignment changes for this ticket |
| Get Ticket SLA Policy Metrics | read | look up the policy targets that apply to a particular ticket |
| Get Zendesk Ticket Related | read | look for an associated issue or a follow-up source |
| Reply to Zendesk Ticket | send: asks first | add a private note or a public reply after choosing the audience |
composio, the connection service behind dusk bot's apps, lists 484 Zendesk actions (version 20261120_00, read 20 november 20264). dusk bot treats 268 as reads, 3 as sends and 213 as changes.
only actions starting with a read word (get, list, search) count as reads, so a read-only bot can't call the rest. a send reaches people or moves money, like redact zendesk comment, and waits for your Allow unless you set a daily amount.
connect Zendesk
- open Connected apps in the sidebar.
- pick Zendesk and sign in on Zendesk's own page, so your password goes to them and never to a bot.
- choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your Zendesk.
- ask in plain words. reading and drafting happen freely; sending asks you first.
name the queue as your team searches for it. sign in to zendesk from connected apps. give your bot reading access and your usual ticket search. try a ticket that changed groups this week. ask for the transfer and the first comment after it.
routines to copy
pick a brief the next agent can act on. each routine brings back ticket ids. keep the original comments close so a short handoff still has a source.
urgent queue at shift start
every weekday at 8, search zendesk for unsolved urgent tickets in my group. for each, read the last customer comment and any service targets on the ticket. show me the request, assignee and applicable target here. flag an empty assignee. leave the queue alone.weekdays at 8 am · urgent tickets with owners and applicable targets
tickets that came back
at noon each friday, read the audits for unsolved tickets our group touched this week. find tickets that left our group and then came back. list the transfers in order. quote a reason only if a comment gives one.fridays at noon · return trips that a shift lead can investigate
handoff to engineering
at 4 each workday, review our open tickets tagged for engineering. pull out the reproduction steps the customer actually tried. look for a related issue and include its reference if present. draft a handoff here with the next missing detail. never add it to the ticket.workdays at 4 pm · a technical handoff that preserves earlier troubleshooting
what it asks you first
choose who can see the comment. the ticket reply action defaults to public. both public and private comments through that action count as sends and ask first by default. for a handoff draft, stay in dusk chat. changing ticket tags is a write and can run without a prompt.
careful with Full access: a bot there with no sending rule can send up to 25 a day without asking. give it Ask every time.
what it cannot do
- recover missing comment text from the comments action. some entries lack a body. report the gap before attributing a request to the customer.
- find archived tickets in the account-wide audit list. use the per-ticket audit action when investigating a known ticket.
- turn a policy target into an exact time remaining on its own. the target action returns the targets applied to the ticket. elapsed time is a separate question.
where the next shift should start
lead with what the customer already tried. asking someone to repeat a failed fix makes a transfer feel like starting over. keep the ticket id, the failed step and the next unanswered question together. for a single urgent ticket already on your screen, work it directly in zendesk.
what it looks like
a fictional example.
before
elliot marsh tried a fresh install. the ticket went from support to engineering and back with a request for the build number.after the bot
next question for elliot: which build failed after the fresh install? skip the reinstall instructions. engineering is waiting on the build number.an illustration with made-up names and numbers.
questions
can the bot tell which group sent a ticket back?
read the ticket’s audit events. ask for each group change in order. follow the remaining pages before deciding that a transfer never happened.
can i have it prepare an internal note without posting it?
ask for the note in your dusk chat. read-only access keeps the draft there until you decide how to use it.
sources
drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].
which urgent zendesk tickets still need an owner?
give the next support shift a ticket handoff
find the intercom customer who still needs an answer
find intercom customers still waiting for a human reply
add new airtable rows without rewriting existing records
turn your notes into a comment on the right asana task