Voice to Text for Freshdesk
Support agents spend hours typing ticket responses that could be spoken in seconds. Every customer needs a thoughtful reply. Every escalation needs detailed internal notes. Every common question deserves a polished canned response. Your typing speed becomes your bottleneck. Blurt lets you write support content at the speed of speech. Hold a button, speak your response, release. Your words appear instantly in any Freshdesk text field. No hunting for templates, no robotic shortcuts. Just your natural voice, transcribed perfectly.
The Typing Problem
Ticket responses take forever to type
You diagnosed the customer's issue in under a minute. But explaining the solution clearly? That takes five minutes of careful typing. You need to acknowledge their frustration, walk through each step, and set expectations for next steps. By the time you've crafted one thorough response, four more tickets have appeared in your queue. You start rushing, sending shorter replies that generate follow-up questions. The queue keeps growing.
Internal notes become useless abbreviations
You're supposed to document everything you tried, what you discovered, and what the next agent should do. But writing detailed internal notes on every ticket would double your handle time. So you write 'tested, escalating' and hope whoever inherits the ticket can figure it out. They can't. They ping you asking what you already checked. The context that took you 20 minutes to gather is lost in translation.
Canned responses sound canned
You rely on canned responses to save time, but customers can tell when they're getting a template. They feel brushed off. You want to personalize each one, adding specific details about their situation, but typing those customizations defeats the purpose of the shortcut. So you send the generic version and hope they don't notice. They always notice.
Knowledge base articles stay on the to-do list
You've answered this exact question a hundred times. You know you should write a help article so customers can find the answer themselves. But drafting a comprehensive article means typing paragraphs of instructions, adding context, covering edge cases. That's a 45-minute project squeezed between ticket replies. The article never gets written. You keep answering the same question manually, over and over.
Shift handoffs lack real context
Your shift is ending but you have eight tickets needing notes before handoff. Each one needs context about what happened, what's pending, and what the next agent should prioritize. Your wrists hurt from typing all day. You rush through the notes, writing just enough to close the loop. Tomorrow's agent will be confused, and you'll get a message asking for clarification on your day off.
How It Works
Blurt works anywhere you type in Freshdesk -- ticket responses, internal notes, canned responses, knowledge base articles. 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 Freshdesk field. Review, edit if needed, submit. Done in seconds, not minutes.
Real Scenarios
Writing thorough ticket responses without the typing time
A customer reports they can't access their dashboard after a recent update. You know exactly what's wrong. Click into the reply field, hold your hotkey, and speak: 'Hi Marcus, I'm sorry you're having trouble accessing your dashboard. This issue is related to a cache conflict from our recent update. Please try these steps: First, clear your browser cache and cookies completely. Second, log out and close all browser windows. Third, open a fresh browser window and log back in. If you're still seeing the issue after that, try using an incognito or private browsing window. Let me know how it goes, and I'll dig deeper if needed.' Forty-five seconds of speaking creates a warm, actionable response that would have taken four minutes to type.
Adding detailed internal notes for escalations
You've spent 25 minutes troubleshooting a complex integration issue. Before escalating to tier 2, you need to document everything. Hold the button: 'Customer's Salesforce integration stopped syncing contacts yesterday. Verified their API credentials are valid and permissions are correct. Tested manual sync from our admin panel and it fails with a 403 error. Checked their Salesforce connected app settings and everything looks normal. Customer mentioned they recently changed their Salesforce admin password, which might have invalidated the OAuth token. Recommend having tier 2 check the token refresh logic. Customer is on Enterprise plan, high priority.' The next agent has complete context without asking a single question.
Creating personalized canned responses
You need to send the standard shipping delay notification, but this customer has been waiting for two weeks already. Insert the canned response, then hold your hotkey to personalize: 'I also want to apologize specifically for the extended delay you've experienced. I've flagged your order for priority handling and added a complimentary upgrade to express shipping at no additional cost. I'll personally monitor this and follow up with you tomorrow with a tracking update.' The response feels human and attentive instead of automated.
Drafting knowledge base articles from experience
You've explained the same password reset process to dozens of customers this week. Time to write that help article. Open the knowledge base editor, hold the button, and teach: 'How to reset your password. If you've forgotten your password or need to change it for security reasons, follow these steps. Step one: Go to the login page and click Forgot Password below the sign-in button. Step two: Enter the email address associated with your account. Step three: Check your inbox for our password reset email, which usually arrives within two minutes. Step four: Click the reset link in the email and choose a new password...' Eight minutes of speaking produces a complete first draft. Edit for formatting, add screenshots, publish. One less question in tomorrow's queue.
Documenting complex troubleshooting steps
You just spent 30 minutes on a call helping a customer configure their email forwarding. In the internal notes, hold your hotkey: 'Walked customer through full email forwarding setup. Their issue was incorrect MX record configuration, not a problem on our end. Had them log into their domain registrar and update MX records to our specified values. Propagation takes 24-48 hours. Scheduled follow-up for Thursday to confirm everything is working. Customer was confused about DNS settings so I explained it step by step. They now understand the difference between MX and CNAME records.' Future you or your colleagues will know exactly what happened.
Writing customer satisfaction follow-ups
A difficult ticket was resolved last week and you want to check in. Hold the button: 'Hi Jennifer, I wanted to follow up on the billing discrepancy we resolved last week. I know it caused some frustration on your end, and I wanted to make sure everything has been working smoothly since we processed the correction. Have you had a chance to verify that your account balance is accurate now? If you notice anything else that looks off, please don't hesitate to reach out directly to me. We really appreciate your patience while we sorted this out.' A thoughtful follow-up that builds customer loyalty, dictated in 25 seconds.
Capturing callback notes after phone support
You just finished a 15-minute phone call with an upset customer. Before the details fade, hold your hotkey: 'Phone call with Sarah Chen regarding order 78432. She was frustrated because she received the wrong size. Apologized and offered full refund plus 20% discount on replacement order. She accepted. Processing refund now, confirmation number coming via email. She'll place the new order herself using discount code SORRY20 I created for her. Mood by end of call was positive. She mentioned she's been a customer for three years and this was her first issue.' The entire call is documented in 40 seconds.
Freshdesk canned responses and text shortcuts are great for repetitive scenarios, but they produce identical text every time. Customers recognize template responses instantly. Blurt lets you speak naturally, creating unique responses that address each customer's specific situation. You get the speed of canned responses 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 templated | ✓ | — |
| Works in any Freshdesk 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