Writes the handover the outgoing shift never has time to write. At the end of a shift it reads what is still open, works out what the incoming team actually needs to know, and posts one briefing to the channel: what is about to breach, what is waiting on someone, what a customer was promised and by when, and what changed today that will generate tickets tomorrow.
It is written for someone starting cold. A ticket appears in the handover only with the context that makes it actionable — what was tried, what is blocking it, and what the next person should do first. A list of ticket numbers is not a handover.
It reports on work, never on people. No per-agent counts, no comparisons, no throughput. A handover that doubles as a performance report gets sanitised within a week and stops being useful to the shift that needs it.
It reads and writes nothing on the tickets themselves — a handover is a summary, not an intervention.
1Find an agent
Support Shift Handover
Free
One briefing for the incoming shift: what's about to break and what someone was promised.
zendeskslack
ConnectConnecting…Connected
Add your credentials
Zendesk API credential
••••••••••••
Slack bot token
••••••••••••
Encrypted · only sent to zendesk.com
Saved securely
Approve this action?
This agent wants to make a change — you decide.
post_handover
Post the shift briefing to the support channel as one message.
DenyApprove
claude.ai
Claude
Write the handover for the Support group — what does the night…
FindAgent · search_open_tickets
FindAgent · list_ticket_comments
✻ Percolating…
FindAgent
Connected in Claude
01020304
Example prompts
Write the handover for the Support group — what does the night shift need to know?
What did we promise customers today that hasn't happened yet?
Which open tickets will breach before the next shift can get to them?
Before you connect
The credentials this agent will ask you for — the full setup is on the Setup tab.
Needs 2 credentials (2 required) to connect. See setup