dusk bot
routineszendesk urgent tickets

dusk botroutines

which urgent zendesk tickets still need an owner?

put unassigned urgent tickets at the top of the shift handoff. an incoming lead needs to see which customer problems still have nobody on them.

by the dusk bot team · checked · how we made this

this routine searches one zendesk group for new and open tickets with urgent priority. the bot returns ticket numbers and assignees in dusk chat so the lead can divide the work.

pixel art: a green pixel bot and an indigo pixel bot beside a tile saying Zendesk, a briefcase and two chat bubbles, on a lilac hill in front of green terraced fields, one saying "who has this ticket"

the message

paste this into a chat with your bot

at 3pm each weekday, search zendesk for urgent tickets in the support group called "returns desk". run separate searches for new and open status. read all matches, confirm group and priority, and combine the results by ticket id.

show unassigned tickets first in this chat. then list tickets with an assignee. within each group put the oldest creation time first. include id, subject, status and assignee, using the id if a name is unavailable. leave ticket bodies out.

never reply, reassign or change a ticket. keep quiet on a complete empty handoff. if either status search fails or cuts off, say which part is missing.
when
at the weekday 3pm shift change in the support group’s time zone
needs
a read-only zendesk connection with ticket search and access to the handoff group. put your shift’s group name in the message.

what comes back

an example, not a real run

afternoon shift · returns desk
unassigned: #763 · new · cannot open return label · opened 12:09
assigned: #754 · open · replacement stuck at dispatch · ellen frost · opened 10:18

make it yours

  • choose the right shift. replace 3pm with the hour someone actually takes the desk. include weekends if you staff them.
  • split a crowded handoff. show unassigned subjects in full and give only numbers for tickets a teammate already owns.
  • include pending work deliberately. give pending tickets their own list if the next shift also chases customer confirmations.

when it goes wrong

  • the subject says urgent but the ticket never appears. this search uses the priority field. inspect the ticket’s priority before widening the query.1
  • a group looks like an owner. inspect the assignee field. routing a ticket to a team still leaves someone to take it.
  • a missing subject breaks the list. zendesk can return a blank subject. keep the ticket number and mark the subject blank.1

give the incoming lead a queue they can claim

take the first unassigned ticket and open its history before handing it to someone. an old creation time tells you how long the ticket has existed. it says nothing about when the customer last heard from support.

for a deadline that expires before shift change, use your live escalation process. dusk bot’s handoff is the wrong place to wait for that alarm.

questions

will a solved urgent ticket stay on the list?

the handoff only includes new and open work. a ticket can keep its urgent priority after a resolution and still fall outside both searches.

can a high-priority ticket appear too?

only if you widen the priority rule. ask for a separate high-priority section so a long list of those tickets never buries an unassigned urgent one.

sources

  1. composio: zendesk actions, checked 20 november 2026
  2. dusk bot docs: routines
  3. dusk bot docs: connected apps

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].