Voice to Text for Zendesk
Support agents spend their days typing the same explanations over and over. Every ticket needs a thorough response. Every escalation needs internal notes. Every resolution needs documentation. Your fingers ache but the queue never shrinks. Blurt lets you write support content at the speed of speech. Hold a button, speak your response, release. Your words appear instantly in any Zendesk text field. No templates, no copying, no shortcuts that sound robotic. Just your natural voice, transcribed perfectly.
The Typing Problem
Ticket responses take longer to type than to solve
You figured out the customer's problem in 30 seconds. But explaining the solution takes 5 minutes of typing. You need to acknowledge their frustration, walk through the steps clearly, and close with next actions. By the time you finish one thorough response, three more tickets have landed in your queue. You start cutting corners, sending shorter replies that generate follow-up questions. The queue grows anyway.
Internal notes become cryptic shorthand
You're supposed to document what you tried, what you learned, and what the next agent needs to know. But typing detailed internal notes on every ticket? That would double your handle time. So you write 'checked settings, escalating to tier 2' and hope whoever picks it up can figure out the rest. They can't. They message you on Slack asking what you already tried. The context you had is gone.
Macros feel helpful until customers notice
You rely on macros to save time, but customers can tell when they're getting a canned response. They feel dismissed. You want to personalize each macro, adding context about their specific situation, but typing those customizations defeats the purpose of the macro. So you send the generic version and hope they don't notice. They notice.
Knowledge base articles never get written
You've answered this question fifty times. You know you should write a help article so customers can self-serve. But drafting a comprehensive article means typing paragraphs of step-by-step instructions, adding context, anticipating edge cases. That's a 30-minute project you don't have time for. The article stays unwritten. You keep answering the same question manually.
End-of-day documentation is pure dread
Your shift is ending but you have six tickets that need final notes before handoff. Each one requires context about what happened, what's pending, and what the next agent should do. Your wrists are tired from eight hours of typing. You rush through the notes, writing just enough to check the box. Tomorrow's agent will be confused, and you'll get a Slack message asking for clarification.
How It Works
Blurt works anywhere you type in Zendesk — ticket responses, internal notes, macro customizations, knowledge base articles, side conversations. Anywhere there's a cursor.
Hold your hotkey
Press your chosen shortcut. A small indicator shows Blurt is listening.
Speak your response
Talk naturally. Explain the solution, add context, document your findings. Blurt handles punctuation automatically.
Release and send
Text appears in the Zendesk field. Review, edit if needed, submit. Done in seconds, not minutes.
Real Scenarios
Writing thorough ticket responses without the typing time
A customer can't log into their account after a password reset. You know exactly how to help them. Click into the reply field, hold your hotkey, and speak: 'Hi Sarah, I'm sorry you're having trouble logging in after resetting your password. This sometimes happens when browser cookies aren't cleared. Please try these steps: First, clear your browser cache and cookies for our site specifically. Second, close all browser windows completely and reopen. Third, go directly to our login page and try your new password. If you're still having trouble after that, let me know and I'll check your account settings on our end.' Forty seconds of speaking creates a warm, detailed response that would have taken three minutes to type.
Adding rich internal notes for the next agent
You've spent 20 minutes troubleshooting a complex billing issue. Before escalating, you need to document everything. Hold the button: 'Customer was charged twice for their March subscription. Verified in Stripe that both charges went through on March 1st and March 3rd. First charge was the normal renewal. Second charge appears to be from a failed payment retry that succeeded late. Refunded the duplicate via Stripe dashboard, confirmation number RF-7829. Customer should see refund in 3-5 business days. No further action needed but flagging for billing team review.' The next agent has complete context. No Slack messages required.
Personalizing macros for specific situations
You need to send the standard 'feature request received' response, but this customer has been asking for this feature for months. Insert the macro, then hold your hotkey to add personalization: 'I also wanted to mention that I've noted in your account that you've asked about this feature several times. I've flagged your request as high-priority for our product team, and I'll personally follow up with you when we have an update.' The response feels human and attentive, not robotic.
Drafting knowledge base articles from your expertise
You've explained the same integration setup to dozens of customers. Time to finally write that help article. Open the knowledge base editor, hold the button, and teach: 'Setting up the Zendesk integration takes about five minutes. Before you start, make sure you have admin access to both platforms. Step one: In your Zendesk admin panel, go to Apps and Integrations, then click Marketplace. Step two: Search for our app and click Install...' Ten minutes of speaking produces a complete first draft. Edit for formatting, add screenshots, publish. The article that's been on your to-do list for months is finally done.
Capturing customer communication in side conversations
You need to loop in a vendor about a customer issue. In the side conversation panel, hold your hotkey: 'Hi team, we have a customer experiencing shipping delays on order number 78234. They placed the order on December 15th and tracking hasn't updated since December 18th. Customer is getting frustrated as this was supposed to be a holiday gift. Can you please check the status and let me know if we need to reship?' The detailed context helps the vendor resolve it faster.
Documenting escalation paths for complex issues
This ticket needs to go to engineering, but you need to document everything you've tried. Hold the button and walk through it: 'Escalating to engineering. Customer is experiencing intermittent 500 errors on their API calls. Verified their API key is valid and has proper permissions. Tested the same calls from our end and they work fine. Customer's error logs show the failures happening between 2-4pm EST, suggesting possible rate limiting or load issues on our side. Customer impact is high — they're a enterprise account processing 50K daily transactions.' Engineering gets a complete picture without playing twenty questions.
Writing customer satisfaction follow-ups
A difficult ticket was resolved and you want to check in. Hold the button: 'Hi David, I wanted to follow up on the database migration issue from last week. I know it caused some disruption to your team's workflow. Has everything been running smoothly since we applied the fix? If you're still experiencing any slowdowns or errors, please let me know and I'll prioritize looking into it. We really appreciate your patience while we worked through this.' A thoughtful follow-up that builds customer loyalty, dictated in 20 seconds.
Zendesk macros and text shortcuts are great for repetitive responses, but they produce identical text every time. Customers recognize canned responses. Blurt lets you speak naturally, creating unique responses that address each customer's specific situation. You get the speed of macros with the warmth of personal communication. And unlike browser-based dictation, Blurt works reliably with sub-500ms transcription and automatic punctuation.
| Blurt | Typing manually | |
|---|---|---|
| Every response sounds personal, not canned | ✓ | — |
| Works in any Zendesk field — tickets, notes, knowledge base | ✓ | — |
| Same hotkey works in every app on your Mac | ✓ | — |
| Sub-500ms transcription, no processing delays | ✓ | — |
Frequently Asked Questions
Start Typing Faster Today
Free to try — no credit card required
Download Blurt