iPhone Dictation Not Working in Zendesk? 10 Fixes That Work

Short answer: If iPhone dictation is not working in Zendesk, open the ticket and tap the reply box until the keyboard appears, then tap its mic key. A ticket you are viewing has no keyboard. Choose public reply or internal note, then submit, because dictated text stays a draft until sent.

Support work does not wait for you to get back to your desk. A customer replies while you are on the train, an escalation lands in your queue during lunch, or you finish a call and want to log what was said before the details fade. You open Zendesk on your iPhone, and speaking the reply is far quicker than thumbing it out. Then there is no mic to tap, or the words go into the wrong place, or the reply you dictated on the way home turns out never to have reached the customer.

Four facts about Zendesk on iPhone explain almost all of it. First, Zendesk has no dictation of its own in the reply box. On iPhone the mic lives on the keyboard, the keyboard only appears when a text field has the cursor, and a ticket you are reading is not a text field, however much text is on it. Second, a ticket reply has modes. A public reply goes to the customer, an internal note goes only to your team, and it is easy to dictate into the one you did not mean. Third, nothing you write in a ticket is final until you submit it, so a dictated reply is a draft until you tap the submit button. Fourth, Zendesk is a work app, and many organizations restrict which keyboards can be used inside work apps.

So most Zendesk dictation problems on iPhone are about getting a cursor into the right box, choosing the right mode and making sure the reply is actually sent, not about your microphone. This guide goes through every cause in order, starting with the most common. If dictation is failing in every app on your phone and not only in Zendesk, start with our complete guide to iPhone dictation not working instead. The same fixes apply to Zendesk on iPad, and exact button names can vary a little between versions of the app and how your admin has set up your account.

How dictation reaches Zendesk on iPhone

It helps to know the path your voice takes, because every fix below is about one stage of it. When you tap the mic on a keyboard, the keyboard records you, turns your speech into text and hands that text to whichever app currently has the cursor. Zendesk never hears your voice. It only receives text, exactly as if you had typed it.

That has three consequences. If Zendesk shows no keyboard, there is nothing to tap, so the problem is the screen you are on, not dictation. If the keyboard appears but the wrong kind of keyboard, the problem is a setting or a company policy. And if text appears but is wrong, in the wrong box or never sent, the problem is the ticket form, not your microphone. Sorting your symptom into one of those three buckets saves a lot of time.

The 30-second Notes test

Before you change anything in Zendesk, rule out the phone itself. Open the Notes app, tap into a new note and tap the mic key on the keyboard. Say a full sentence, such as "Thanks for your patience, I have checked your order and it ships tomorrow."

• Words appear in Notes: dictation works on your phone, so the problem is something specific to Zendesk. Carry on with the fixes below.
• No mic key, or nothing happens: the problem is the phone, not Zendesk. Check Settings, then General, then Keyboard, and make sure Enable Dictation is on, then see our guide to iPhone dictation not working.
• Words appear, but only on Wi-Fi or only on mobile data: the connection is the problem. Switch networks and try again.

This single test splits every problem into two groups and stops you from changing settings that were never broken.

The 10 fixes, in order

1. Open the ticket, then tap into the reply box

This is the cause behind most "there is no mic" complaints. In the ticket list and in a ticket you are only viewing, there is no text field, so no keyboard and no mic. Open the ticket, then tap the reply or add-comment area so the composer opens and a cursor blinks. Only then will the keyboard slide up with its mic key.

If you opened the ticket from a notification, an email or a search result, the app may land you in the read-only view first. Look for the reply button or the comment box at the bottom of the conversation and tap it. If the keyboard appears and then vanishes right away, tap the composer once more, because the first tap sometimes only expands it.

2. Choose public reply or internal note on purpose

The composer usually lets you switch between replying to the customer and leaving a note for your team. Dictation goes into whichever one is selected, so a wrong choice can send an internal remark to a customer or hide a reply the customer is waiting for. Before you tap the mic, glance at the mode label and the recipient line.

A good habit is to say the mode out loud to yourself as you pick it: "public" or "note". It takes a second and prevents the two most expensive mistakes in a help desk, which are an internal comment that reaches the customer and a customer answer that stays internal.

3. Check the recipients and the requester

If your words landed but the wrong people will see them, the recipients are the problem, not dictation. Look at the To and CC lines before you submit. A reply to an existing conversation normally goes to the requester and anyone already copied, and adding a CC by voice can attach the wrong person if the keyboard misheard a name. Read each address once, because a misheard email address looks very similar to the right one.

When a ticket has several people on it, take a moment to confirm that the customer, not just a colleague, is actually in the recipient list for a public reply.

4. Get a keyboard with a mic on screen

If the keyboard appears but has no mic key, you are on a keyboard that does not offer one, or dictation is switched off. Tap and hold the globe or smiley key in the bottom corner to see the keyboards you can switch to. If a keyboard with a mic is not listed, add one in Settings, then General, then Keyboard, then Keyboards.

Two situations always give you Apple's keyboard whatever you choose. iOS forces it on password and sign-in fields, so if Zendesk has asked you to sign in again, you will get the standard keyboard until you are through. And some organizations use device management policies that allow only Apple's keyboard in work apps. If your keyboard works in Messages and Notes but never appears in Zendesk or other work apps, ask your IT team whether a policy is in place. It is a settings rule, not a fault.

5. Submit the reply, and know what status you are sending it as

A dictated reply sits in the composer until you submit it. If you switch to another app, answer a call or lock your phone, the draft may or may not be there when you return, depending on the app, so do not treat dictating as the same thing as sending.

When you submit, Zendesk usually lets you choose the ticket status that goes with it, such as open, pending or solved. Submitting as solved when you meant pending closes the loop with the customer before they have answered, and submitting as open when you meant solved leaves a finished ticket in your queue. Check the label on the submit button, then confirm the reply shows up in the conversation thread afterward. If it does not, go back to the ticket, check for a leftover draft and send it again.

6. Watch macros and templates

Macros are saved snippets that fill in a reply and sometimes change the ticket in several ways at once. Applying one after you have dictated can replace or add to what you said, and applying one before can leave you dictating into text you did not expect. If your words seem to vanish or double up, look at whether a macro was applied, and apply macros first, then dictate your personal lines above or below the template text.

The same goes for any text your admin has set to appear automatically, such as a greeting and signature. Dictate your message between them rather than over them, or you may overwrite lines that your team expects to see.

7. Watch for mentions, links and formatting

Typing certain characters in a note can open a mention list so you can tag a teammate, and ticket text can turn into links or formatted lines. When you dictate a name, the keyboard produces plain text and Zendesk may not treat it as a real mention, so the teammate gets no notification. If you need someone to be alerted, pick them from the mention list after you dictate rather than relying on the spoken name.

Likewise, if a line you dictated turns into a list or a heading, or a long link breaks across lines, tap into the composer, fix it and read it back before submitting. It is usually a formatting side effect rather than missing words.

8. Stop the keyboard mangling numbers, IDs and product names

Support text is full of things speech software finds hard: ticket numbers, order IDs, serial numbers, plan names and product terms. They can come out as words, with spaces or without the digits you meant. A few habits help:

• Say numbers one digit at a time, with a clear pause between groups, then read the result back against the source.
• Say "dash" or "hyphen" and "slash" out loud when a code needs them.
• Spell an unusual product or customer name once, then correct it.
• For terms you use every day, a keyboard with a personal dictionary saves repeating the correction on every ticket.

Never assume a dictated reference number is right. A wrong digit sends a customer to the wrong order, so read each one against the ticket details before you submit.

9. Find words that landed somewhere else

If you dictated and nothing appeared where you expected, the words may be in another field. Tickets have more than one text area: the subject line, the comment composer, tags, and custom fields set up by your admin. Dictation goes wherever the cursor was, and tapping a field by accident while the keyboard is open moves it.

Scroll through the form from top to bottom and look in the subject, in any text fields below and in the thread itself. Clear anything that does not belong, then tap into the comment box and dictate again. If a customer-facing field now holds an internal remark, remove it before you submit.

10. Free up the microphone, and check dictation on your iPhone

If the mic key does nothing, something else may be using the microphone. A phone call, a voice or video call in another app, a screen recording or a voice memo can all hold it. End or pause them and try again. A call with a customer on speaker is a common culprit on a support team, and dictation will not work until it ends.

Finally, check the basics on your phone. In Settings, then General, then Keyboard, make sure Enable Dictation is on. If you use a third-party keyboard with a mic, make sure it is added and that Allow Full Access is on, because it needs that permission to reach its transcription service. Restarting the phone clears a surprising number of stuck states. Zendesk itself does not need microphone permission for keyboard dictation, because the keyboard does the listening, not the app.

Zendesk quirks that look like broken dictation

A few behaviors are easy to mistake for a dictation fault:

• The reply appears to send but nothing shows. A slow connection can delay the thread update. Pull to refresh before you send it a second time, or you will send it twice.
• Autosave versus submit. A saved draft is not a sent reply. The customer sees nothing until you submit.
• Light agents and limited roles. Some roles can only leave internal notes, so a public reply may not be an option at all. That is a permission, not a dictation fault.
• Several people replying at once. If a colleague answers while you dictate, you may see a warning before you submit. Read their reply first so you do not contradict it.
• Auto-capitalization and punctuation. The keyboard may add or skip capitals and full stops. Read the reply once before submitting, as you would for anything customer-facing.

Quick triage

• No keyboard at all: you are viewing the ticket, not replying. Tap the reply box (fix 1).
• Keyboard but no mic key: dictation is off or you are on a keyboard without one (fix 4, fix 10).
• Apple's keyboard keeps appearing: sign-in screen or a work policy (fix 4).
• Customer did not get my reply: internal note or unsent draft (fix 2, fix 5).
• A teammate got the wrong text: wrong mode or recipients (fix 2, fix 3).
• Numbers and names are wrong: read them back (fix 8).
• Words in the wrong field: check the subject and custom fields (fix 9).

Zendesk on iPhone versus Zendesk on a Mac

Many agents handle the heavy lifting on a laptop and use the phone for quick answers, and dictation behaves differently on each. On a Mac, dictation is not tied to a keyboard on screen, so a hotkey can type into the reply box in a browser tab as soon as the cursor is there. The causes of trouble there are different: browser permissions, the focused window and the system microphone. We cover those in our guide to Mac dictation not working in Zendesk.

On the phone, almost everything comes down to whether a text field has the cursor and which keyboard is showing. Keeping that difference in mind stops you applying a desktop fix to a mobile problem.

A dictation workflow that suits Zendesk on a phone

A few habits make voice replies faster and safer:

1. Read the ticket first. Scroll to the customer's last message so your reply answers what they actually asked.
2. Pick the mode, then tap the composer. Public or note, decided before you speak.
3. Say the whole reply in one go. Speak in full sentences, and say punctuation such as "comma" and "full stop" if your keyboard supports it.
4. Read it back. Check names, numbers, tone and the closing line.
5. Check the status, then submit. Make sure the status on the button matches what you intend.

It is worth the effort because speaking is much faster than typing. Most adults type around 40 words per minute on a full keyboard, and even professional typists usually sit around 80 to 100, while normal speech runs at 130 to 150 words per minute. On a phone the gap is wider still. In a queue where every minute to first reply counts, that difference adds up across a day. Our guide to dictating Zendesk replies by voice walks through the setup in more detail, and our piece on dictation for customer support covers wider workflows.

A keyboard with a mic for every ticket

Apple's dictation is free and built in, but it stops when you pause, it depends on settings that are easy to switch off by accident, and fixing a misheard word means going back and editing by hand on a small screen.

Voice Keyboard Pro is a custom iPhone keyboard with a built-in mic button for dictation in any iOS app, Zendesk included. Open the ticket, tap the reply box, tap the mic, speak, and your words are added at the cursor. Because it is a keyboard rather than a feature of one app, it works the same way in Zendesk, Mail, Slack and everywhere else you type. Like any keyboard, it only appears while Zendesk is showing a text field, so fixes 1 and 5 still apply, and if your organization allows only Apple's keyboard in work apps (fix 4), that rule applies to it too.

A few features help with support work in particular:

• Voice Edit lets you speak a change to fix text, so you can correct a sentence in a reply without selecting and retyping it.
• Two-way translation while dictating, across 24 languages, lets you speak in one language and write in another, which helps when a customer writes in a language you do not use every day.
• Swipe typing is there for the replies you would rather not say out loud in a public place.

Setup means adding the keyboard in Settings and allowing Full Access so it can reach the transcription service. Our guide to enabling Full Access for an iPhone keyboard explains what that permission does. On privacy, our servers store only operational pings. No audio and no transcript content is stored, which matters when your tickets contain customer details. There is a free tier with daily limits, and Pro is $4.99 a month or $34.99 a year. On a Mac, the same app lives in your menu bar: hold a hotkey, speak, release, and the text appears at your cursor. It adds Smart Vocabulary, a personal dictionary with replacement rules for your product names, plus Meeting Mode with speaker detection and AI notes, and calendar meeting detection.

Frequently asked questions

Does the Zendesk app have voice typing?

Not in the reply box on its own. Dictation on iPhone comes from the keyboard, so you open the ticket, tap the reply box so the keyboard appears, and tap its mic key. Any keyboard with a mic works, including Apple's.

Why is there no keyboard when I open a ticket?

You are looking at the ticket, not replying to it. Tap the reply or comment area so the composer opens and a cursor appears. Tickets opened from notifications and search often start in the reading view.

Why didn't my customer get the reply I dictated?

Either it was sent as an internal note, or it is still an unsent draft. Open the ticket, look at the conversation thread, and check that your reply is there as a public reply. If not, send it again with the right mode selected.

Does the Zendesk app need microphone permission for dictation?

No. Keyboard dictation is handled by the keyboard, not by Zendesk. Apple's dictation follows the Enable Dictation setting, and a third-party keyboard with a mic needs Full Access, not a permission from Zendesk.

Why does Apple's keyboard always appear in Zendesk instead of mine?

Either you are on a sign-in screen, where iOS always uses Apple's keyboard, or your organization has a policy that allows only Apple's keyboard in work apps. If it happens only in Zendesk and other work apps, ask your IT team.

Does this work the same way on iPad?

Yes. Zendesk on iPad uses the same reply modes and submit rules, and dictation still comes from the keyboard, so every fix here applies.

What to do next

Run the 30-second Notes test, then work through the fixes that match what you saw. For most people it is fix 1: the ticket was open, but there was no cursor in the reply box, so no keyboard and no mic. If your customer never saw your reply, it is fix 2 or fix 5, and if Apple's keyboard keeps taking over, check fix 4 before anything else. And if you want dictation that works the same way in every app on your phone, try Voice Keyboard Pro's free tier on your next ticket.