Draft a helpdesk macro while keeping the ticket in view

Decide whether you are writing a reply, a note or an action

A macro may do more than insert text. Zendesk's documentation, for example, describes macros as manually applied prepared responses or actions. That distinction matters when drafting with AI: a clear customer reply says nothing about whether changing a ticket's status or assignee is appropriate.

Before opening the overlay, name the artifact. Is it a public acknowledgement, an internal escalation note, or text for an automatic response you will configure separately? Keep the permitted actions in a distinct brief. A paragraph saying that a case has been escalated must not be used before the actual handoff has happened.

Prepare a compact handoff brief

Suppose a fictional support team needs an escalation macro for a recurring export error. The customer supplied an error code and attempt time; the case now requires a specialist. No resolution time has been agreed. The draft should acknowledge the handoff and state the next update only if the team has an approved rule for it.

Copy only the relevant, permitted facts and remove unnecessary identifiers. State what has already been checked, what remains unknown and what the specialist needs. The overlay does not infer these facts by looking at your helpdesk window.

Open, draft, compare and return

This is a drafting loop. The shortcut opens the overlay; it does not create a saved macro, apply ticket actions or send an approved answer. If the request needs only one sentence, keep the prompt and output short rather than generating an entire response library.

1. On macOS, press ⌘⇧K by default to open Colay. If you changed the shortcut in Settings, use your configured combination.
2. Paste the brief and approved rules. Select available agents and use Ask separately when alternative formulations would help.
3. Compare the public reply and internal note independently. Choose wording that accurately reflects work already done and the next permitted action.
4. Return to the helpdesk and paste the reviewed text into the appropriate draft field. Configure and save any macro actions in the helpdesk itself, using its normal permissions and review process.

A copyable prompt for a macro with clear boundaries

If you are authoring an automatic acknowledgement instead, replace the handoff rule with the actual trigger and approved service message. Generation does not configure that trigger. Review whether the text will still be true for every ticket that receives it.

Draft an escalation macro from this permitted context: [symptoms, checks completed, missing information]. Approved handoff rule: [rule]. Channel and tone: [details]. Return three separate blocks: customer-facing message, internal specialist note, and a configuration checklist for me to verify in the helpdesk. Give a concise and a more explanatory customer version with identical commitments. Do not claim that escalation, reassignment or any other action has occurred unless the facts say it has. Do not invent a resolution time, field name or integration. Mark variables clearly and list missing decisions outside the customer text.

Test the saved macro as a support artifact

Use a test or otherwise appropriate non-customer case in your existing process. Inspect public versus internal visibility, placeholder values, line breaks and any status or assignee changes. Check the full result before submitting the ticket. A well-written message can still be harmful if an internal note is exposed or a case is marked solved accidentally.

Save a short description of when to use the macro and when to avoid it. If agents regularly remove the same sentence, revise the brief and the saved template together. Colay can help with the next wording pass; your helpdesk remains the place where the macro is stored, applied and governed.

Questions, answered