The Zendesk Mobile App

Zendesk publishes an agent app for iOS and Android. It is genuinely useful for a narrow set of jobs and frustrating if you expect the browser in your pocket.

What it is, and what it is not

There are two different Zendesk mobile experiences and people mix them up constantly. The agent app is the one your support team installs to work tickets from a phone. The mobile SDKs are libraries you embed in your own product so your customers can get support inside your app. Different audiences, different products. This page is about the first one.

The agent app is a real native client, not a wrapper around the web interface. That is why it feels quick, and also why it does less. Every screen in it was built deliberately, so anything nobody built is simply absent.

What the Zendesk mobile app does well

The app is built around triage and reply, and it does both properly.

Views. Your saved views come across, so the queue you look at on a laptop is the queue you see on a phone.
Reading a ticket. Full conversation history, requester details, the organization, tags and custom field values.
Replying. Public replies and internal notes, with macros available so you are not typing a long answer with your thumbs.
Property changes. Assignee, status, priority, group. The bread and butter of triage.
Search. Ticket and user search, good enough to find the thing somebody just messaged you about.
Attachments. Photos from the camera roll, and taking a photo directly, which is quietly excellent for field teams.

That list covers roughly what an on-call person needs at eleven at night. It's not a substitute for a working day.

What it cannot do

This is the part worth reading before you tell a team they can work from their phones.

Admin is out. You cannot build triggers, edit automations, change ticket forms, manage users in bulk, or touch anything in Admin Center in a meaningful way. If configuration is your job, the app is not your tool.

Reporting is out too. Explore is a browser product. There is no dashboard on the phone, so the manager who wants to glance at CSAT over coffee is opening a browser tab like everybody else.

Apps and integrations are the bigger gap in practice. Your sidebar apps, the order lookup, the billing panel, the internal CRM widget your team relies on all day, none of that renders. Agents who have quietly built their entire workflow around one sidebar app find the mobile app almost useless, and they are not wrong.

Merging is another one. Merge is an interface action in the web agent view, and duplicate cleanup isn't something you do from a phone. Same for side conversations, ticket forms with heavy conditional logic, and anything involving multiple browser tabs, which is most of real support work.

Notifications, the actual reason to install it

Push notification is the feature that justifies the app, and the one teams configure worst.

You choose what you get notified about, and the sensible setting is narrow: tickets assigned to you, and updates on tickets you follow. Turn on anything broader and within a week the notifications get muted, which means the on-call escalation you built the whole thing for gets muted too.

A pattern that works: one trigger that fires only on genuine escalations, notifying a specific group. Everything else stays silent. A phone that buzzes twice a day gets looked at. A phone that buzzes forty times gets left face down.

Worth knowing: notification delivery depends on the operating system and the device power settings as much as on Zendesk. Aggressive battery optimisation on some Android handsets delays push, so if you're building an out of hours process around it, test on the actual phones your team carries before you trust it.

When agents actually use it

Honestly? Four situations, and they are all edges.

On-call and out of hours. Something broke at the weekend, somebody needs to acknowledge it and set expectations. The app is perfect for exactly this.

Commuting triage. Twenty minutes on a train, reassigning and prioritising overnight arrivals so the queue is sane when the team logs in.

Managers checking a specific ticket. The escalated one, the angry one, the one the CEO asked about.

Field and site work. Engineers who are physically somewhere, taking a photo and dropping it on a ticket. This is the use case where the app is not a compromise but the best tool available.

What it isn't is a way to avoid buying laptops, or a way for a team to work a full shift. Anyone who tries lasts about a day.

FAQ

Frequently asked questions

Are the iOS and Android apps the same?

Near enough. The Zendesk iOS app and the Zendesk Android app share the same feature set, and both are built for triage and replies rather than for administration.

Is the Zendesk mobile app free?

Yes, the agent app itself costs nothing extra. It signs in with an existing agent seat, so you pay for the licence, not the app.

Can I do admin work from the Zendesk mobile app?

No. Triggers, automations, forms, fields and Admin Center settings are browser only. The app is built for reading and answering tickets.

Do sidebar apps work on mobile?

No. Marketplace and custom sidebar apps do not render in the mobile app, which is the single biggest gap for teams whose workflow depends on one.

Can I merge tickets from the mobile app?

No. Merging is a web agent interface action, so duplicate cleanup waits until somebody is back at a keyboard.

Does the mobile app work offline?

Not meaningfully. You can read recently loaded content in some cases, but assume it needs a connection to do anything useful.

The queue is the same size on any screen

Phone or laptop, roughly a tenth of what an agent triages is a ticket somebody already opened. Ticket Merger catches those before anyone reads them twice.

Start free trial

14-day free trial. No credit card required.