Zendesk Talk on Mobile

Zendesk Talk mobile is the weakest part of the Zendesk mobile story, and there are two good workarounds.

How Talk normally works

Zendesk Talk is browser-based voice. Calls arrive in the agent interface, the audio runs over WebRTC in the browser tab, and a ticket is created for the call with a recording attached if you have recording enabled. No handset, no desk phone, no separate application.

That design is why Talk feels seamless at a desk and awkward everywhere else. The call lives in the browser, and the browser is where the agent already is. Take the browser away and the model has to change.

For the wider setup, routing and pricing picture, see Zendesk Talk and voice. This page is only about the mobile part.

What Zendesk Talk mobile actually does

Do not assume the Zendesk agent app turns your phone into a full call centre handset. Voice support in the mobile app has been limited and has changed between releases, so verify what your current app version supports before designing a process around it.

What's reliably true on mobile:

You can see call tickets. Calls that came in and were handled elsewhere appear as tickets like anything else.

You can read the transcript or play the recording, subject to how your account is configured.

You can follow up. Adding notes, changing status, reassigning: all normal ticket work.

What you shouldn't count on is a mobile agent reliably receiving inbound queue calls the way they would in the browser. If someone tells you the team can cover the phone line from their handsets using the app alone, ask them to prove it on the exact app version and handsets in use, on a real call, before you publish the rota.

The forwarding route

Talk supports forwarding an incoming call to an external number. This is the simplest way to get support calls onto a mobile device and it works because it does not involve mobile software at all.

The call rings a normal phone. The agent answers it like any other call. Zendesk still logs the call and creates the ticket, since the call passed through Zendesk before it was forwarded.

What you lose is everything screen-shaped. No customer record in front of the agent, no ticket history, no ability to type notes while talking unless they also have a laptop open. They are working from memory and writing it up afterwards, which means writing it up worse.

It is the right answer for out of hours cover and for genuinely occasional calls. It's the wrong answer for a team whose main channel is the phone.

When to use a softphone instead

A softphone is a SIP application on a phone or laptop that registers to a voice platform and behaves like a real desk phone: hold, transfer, queue presence, mute, DTMF, all of it.

Go this way when voice is a primary channel rather than a courtesy. The pattern is a proper telephony platform for the call handling, integrated with Zendesk through CTI so screen pop and call logging still work, and Talk used lightly or not at all.

Voice is over about a fifth of your volume. Talk is good, and dedicated voice platforms are better at voice.

Agents work from anywhere, including phones. Softphone apps are built for exactly this and Talk is not.

You need queue features Talk doesn't offer, like sophisticated skills routing, whisper coaching or callback queues.

Call quality and network variability matter. A native SIP client generally handles a shaky mobile connection better than a browser tab.

The integration route is well trodden. Several telephony vendors publish Zendesk apps that pop the customer record on ring and write the call back to a ticket, which gives you most of the Talk benefit with a real voice stack underneath.

A workable hybrid

Most teams that get this right run something simple. Talk in the browser during working hours, since it is already paid for and the ticket integration is native. Forwarding to a mobile for on-call and out of hours, with the agent expected to write the ticket up afterwards. And a softphone only for the people whose job is genuinely the phone.

One operational detail worth setting up regardless: make sure the out of hours forwarding path still creates a ticket. If a forwarded call bypasses Zendesk entirely, the conversation vanishes from your queue, the customer emails the next morning because nobody followed up, and you now have a support interaction with no record and a second ticket about the same thing.

FAQ

Frequently asked questions

Is there a Zendesk Talk app for phones?

Not a dedicated one. Zendesk voice on mobile means the agent app's limited call handling or forwarding to a real number, and a Zendesk Talk softphone on the desktop is what most teams end up using instead.

Can I take calls with Zendesk Talk mobile?

Not reliably through the agent app alone. The dependable route is Talk forwarding calls to an external number, or using a softphone with a CTI integration.

Does a forwarded Talk call still create a ticket?

Yes, because the call passed through Zendesk before forwarding. What the agent loses is the on-screen customer context while they are talking.

What is a softphone?

A SIP application on a phone or computer that behaves like a desk phone, with hold, transfer and queue features. Better than a browser tab for heavy voice use.

Should we replace Zendesk Talk with a dedicated voice platform?

If voice is more than roughly a fifth of your volume, or you need advanced routing, usually yes. Integrate it back into Zendesk with CTI so tickets still get created.

Can agents see call recordings on mobile?

Generally yes, since the recording is attached to the ticket. Availability depends on your plan and recording configuration.