Short answer: Zendesk ticket, internal note, public reply, side conversation, macro placeholder, tags, requester, and SLA fields include composer text areas. Click the Agent Workspace composer, press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux), speak, press again. AICHE does not change ticket status or apply macros.
The Problem
Zendesk Agent Workspace puts a CKEditor composer at the bottom of every ticket with a public reply tab, an internal note tab, and a side conversation panel on the right. Each one needs a different register: empathetic and structured for the customer, dense and factual for the next agent, scoped and specific for the engineer you're pinging. Typing all three under SLA pressure is where the day goes.
Copilot's suggested first replies and "enhance writing" tools help when an existing macro nearly fits, but most of your real work is the paragraph in the middle that no macro covers - the part where you explain why the refund applies to their February invoice but not their March one. That paragraph is what takes the time, and it's the part QA scores on.
What Changes
You stop typing the middle paragraph. You keep your macros, your knowledge panel, your Copilot summary on the right - all of it. You just speak the part that's actually unique to this ticket.
Speaking runs around 150 WPM. Typing under queue pressure with QA looking over your shoulder runs closer to 30 to 40 WPM, because you're correcting tone as you go. A 120-word reply that takes 4 to 6 minutes to type takes about 50 seconds to speak. Multiply that by a 40-ticket day.
How It Works
- Open the ticket in Agent Workspace.
- Confirm the composer tab. Public reply for the customer, Internal note for teammates, or open a side conversation from the right panel.
- Click into the composer body so the cursor is in the text area.
- Press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux).
- Speak the full response. Acknowledge the issue, explain the cause, walk through the fix, close with next steps.
- Press the hotkey again. AICHE transcribes, cleans, and inserts at the cursor.
- Review, set status (Open, Pending, On-hold, or Solved), submit.
The composer accepts the inserted text as if you typed it, so spell-check, formatting toolbar, and the Copilot writing assistant all still work on the result.
Public Replies That Pass QA
Zendesk QA rubrics consistently score on the same things: empathy in the opening, accuracy in the explanation, completeness on next steps, tone throughout. Typed replies under queue pressure lose points on empathy and completeness, because that's what gets trimmed when you're trying to get to the next ticket.
Speaking restores both. You naturally open with "I can see why that's frustrating" because that's how you'd start the conversation in person. You include the third sentence about what to do if the fix doesn't work, because saying it costs nothing. Turn on Message Ready in AICHE settings and the natural speech comes back with punctuation, paragraph breaks, and the professional polish QA reviewers look for.
Pair this with macros, don't replace them. Apply your team's standard macro to set greeting, signature, and structure, then dictate the specific paragraph that addresses this customer. The macro keeps the team consistent. The voice paragraph carries the empathy and detail.
Internal Notes With Real Context
Internal notes in Zendesk are where escalation context lives, and they're almost always too short. "Customer reports intermittent 500s on checkout" is technically accurate and forces the next agent to investigate the ticket from scratch.
Click the Internal note tab (it's a separate tab from public reply, and the composer remembers your last selection - check before you start). Press the hotkey and speak 30 to 45 seconds of context: what the customer reported, environment details they shared, what you already tested, the result, your best guess at root cause, and any account identifiers Tier 2 will need. AICHE inserts it as a structured note. The next agent picks up the ticket with everything they need.
This is the use case where Content Organization (in AICHE settings) earns its keep over Message Ready. Internal notes don't need empathetic phrasing. They need clean headings or numbered points that scan in five seconds.
Side Conversations to Engineering, Legal, Slack, Teams
Open a side conversation from the right panel, pick Slack or email, click the message body, press the hotkey, speak:
"Account ID 88421, production checkout 500s since 14:30 UTC. Repro: add item, apply SAVE20, submit payment. Logs show timeout on payments-api pod pay-7f2a. Customer impact: ~120 failed orders. Need eng decision: rollback deploy v2.14.3 or hotfix rate limit on promo service."
Stop. AICHE inserts the text; you send the side conversation. AICHE does not update ticket status, apply macros, or change tags.
Authoring Zendesk Guide Articles
Every support team has the same backlog: 30 to 50 articles that should be in Guide and aren't, because writing them is a 45-minute task that gets pushed off every sprint. The articles you'd write would deflect hundreds of tickets a month each.
Right after you solve a ticket you know will repeat, open Guide, create a new article, click into the body. Speak for 60 to 90 seconds: what the issue looks like to the customer, why it happens, the steps to fix it, what to do if those steps don't work. AICHE with Content Organization on returns structured prose with headings and a numbered procedure. Add screenshots, set permissions, publish. Two minutes instead of forty-five.
Common Questions
Q: Does AICHE work in the Agent Workspace composer, including CKEditor formatting?
A: Yes. AICHE inserts plain text at the cursor. CKEditor accepts it like typed input, so the formatting toolbar, spell-check, and link tools still work on whatever you dictated.
Q: Will Copilot's enhance writing still work on dictated text?
A: Yes. Once the text is in the composer, Copilot treats it the same as typed text. You can dictate the body, then use Copilot's "more formal" or "simplify" actions on top of it if you want.
Q: Can I dictate into a Zendesk macro before applying it?
A: AICHE inserts at the cursor in the composer, after the macro has been applied. Apply the macro first, then position the cursor where the custom paragraph belongs, then dictate. That's the workflow that keeps macro structure intact.
Q: I keep dictating into the public reply when I meant the internal note. Any way to prevent that?
A: This is a Zendesk UI quirk - the composer remembers your last selected tab, and switching takes a deliberate click. Glance at the tab color before you press the hotkey. Public reply has a different accent color from internal note in every Zendesk theme.
Q: Does it handle ticket-specific vocabulary like account IDs, SKU codes, error codes?
A: Add them to AICHE's custom vocabulary list. Account number formats, product SKUs, internal service names, error codes you reference constantly - dropping them in once means they transcribe correctly every time.
Q: What about voice tickets - can I dictate notes while listening to a recorded call?
A: Yes. Pause the embedded audio player in Agent Workspace, press the hotkey, dictate your summary or next-action note, press again. The recording stays where it is.
Q: Does this work on Linux Zendesk users? Some agent tools don't.
A: Yes. Ctrl+Alt+R fires the global hotkey on Linux. AICHE inserts through the standard input event path, which Zendesk's web composer accepts the same as any other text input.
Result: the 8-hour typing day on a 40-ticket queue becomes roughly 3 hours of dictation and review. QA scores hold or improve because the empathy and completeness that get rushed out during typing stay in when you're speaking.
Try it now: open a ticket you're avoiding because the explanation feels like too much typing, click into the composer, press the hotkey, and talk through the answer the way you would to a colleague.