Zendesk Internal Notes and Handover Standards for Agents
Make tickets readable by whoever picks them up.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Write a standard for internal notes and handovers in Zendesk. Typical complex tickets: [TICKET_TYPES]. Shift patterns: [SHIFT_PATTERNS]. Problems: [PROBLEMS]. A colleague should continue the ticket without asking questions, so write for a reader who knows nothing: no abbreviations, the order number, the customer's exact error message quoted, and times with time zone. Note format: summary of the issue, what has been tried, what the customer was told, what is outstanding, next step with date, and relevant links, with an example for an invented billing ticket. Handover at shift end as a list of tickets with a status and a decision needed, posted or spoken before leaving, and a quick check before reassigning. Never put in notes opinions about the customer, full card numbers or passwords. Monthly review of five tickets per agent for note quality with a friendly feedback template. Keep the note format to six lines that fit on one screen, and give an example of a poor note rewritten as a good one. Say how a supervisor can check quality without reading every ticket.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.