dusk bot
use casescustomer support inbox

dusk botuse cases

give the next support shift a ticket handoff

the hardest ticket to spot is the quiet one where you owe someone a call. give a bot your zendesk handoff view.

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

ask it to read the last exchange on each ticket and pull out promises coming due. you get a short list in chat before the next shift takes over.

pixel art: a blue pixel bot and a yellow pixel bot beside a mailbox with a letter and two chat bubbles, on a lemon field in front of green terraced fields, one saying "who owes the reply?"

the routine

start with the queue the outgoing shift actually uses. copy its view id into the message.

paste this into a chat with your bot

at 3:45 each weekday, read the tickets in our zendesk handoff view (id 358214). read the comments on each ticket. who owes the next move? list our dated promises first, oldest due first. include the ticket number, the promise and who made it. then list customers who answered our last question and still need help.

put missing comments or unclear owners under 'open the ticket'. tell me if you only saw part of the queue. write the handoff here. leave the tickets alone.
when
weekdays at 3:45 pm, before shift change
needs
the handoff view id and read only zendesk access

what comes back looks like this (an example, not a real inbox)

example handoff
#681 | bridget promised a replacement tracking number by 4 pm. customer still waiting.
#694 | customer sent the requested photo. support owes the next reply.
#703 | latest comment has no readable text. open the ticket.

what the incoming shift needs to know

give the next person a reason to open each ticket. “waiting” can mean the customer owes a photo. it can also mean a colleague promised to call before closing. put the promise beside its deadline. preserve the time zone if the writer gave one.

follow a ticket past its status

read the conversation before deciding who owes a reply.

  1. list tickets in the named zendesk view and follow additional result pages.1
  2. read each comment in date order. distinguish an internal note from a reply the customer received.
  3. quote the few words that set a deadline. carry forward an older promise until a later reply settles it.

hand the decision to the incoming agent

open the live ticket before contacting anyone. another agent might have replied during the handoff. let the shift lead choose an owner for unresolved promises. if you need someone to respond to emergencies as they happen, a scheduled dusk bot handoff is the wrong tool.

the guard rails

  • keep zendesk read only. the handoff belongs in the bot chat.
  • leave attachments and customer contact details out of the summary. a ticket number gets the agent back to the original.
  • sending a customer reply through a connected app asks first by default.4

try it in 2 minutes

  1. choose a zendesk view the shift lead knows
  2. try one ticket with a dated promise
  3. compare the handoff with the last public reply

what it looks like

an invented shift change at a repair desk

before

the subject still says “broken clasp”. the customer sent a photo yesterday. bridget later promised tracking by closing time.

after the bot

the handoff leads with the tracking promise. the next agent looks up the replacement shipment instead of requesting the same photo again.

an illustration with made-up names and numbers.

what it could save you

about 8 minutes per handoff with these timings

12 minutes reading the queue by hand
- 4 minutes verifying the handoff
= 8 minutes per shift change

a rough estimate. it assumes:

  • time both methods on the same view
  • include time spent opening ambiguous tickets and correcting the list
  • count the handoff only. customers still need answers

mistakes people make

sorting by the latest update alone

look back for outstanding promises. an internal spelling correction can bring an older case to the top.

treating a private note as a customer reply

identify who could see the comment before saying the customer has an answer.

questions

can the handoff catch a promise on a quiet ticket?

yes, if the ticket belongs to the view and its comments include the promise. a view limited to today's updates can miss it.

what if a ticket has no readable last comment?

keep the ticket number in the handoff. an agent can open the original before taking it off the list.

sources

  1. composio: zendesk actions, checked 20 november 2026
  2. dusk bot docs: files and connected apps
  3. dusk bot docs: routines
  4. dusk bot docs: a bot’s computer

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