[object Object]

The Freshdesk and Freshservice mobile apps cover triage and reply well. They cover workflow automation, custom apps, and complex forms poorly. Designing assuming feature parity with web is a mistake.

What works well on mobile

  • Reading tickets, replying, basic status changes
  • Push notifications for assignment and SLA breach
  • Simple approvals (Freshservice change requests)
  • Voice-to-text replies via OS keyboard

What does not work well

  • Marketplace apps render either incompletely or not at all
  • Complex custom forms with conditional logic
  • Long-running workflows that require multiple field updates
  • Bulk operations on tickets
  • Custom dashboards (web-only)

Plan workflows for mobile-first agents

If your front-line agents work primarily on mobile, simplify their ticket form. Move complex fields to a “Detailed update” screen accessed only when needed. Keep the mobile default form to under six fields.

Push notification routing

Mobile push uses the same assignment rules as web. Watch out for SLA-warning pushes at 3 AM in time zones you forgot about. Configure quiet hours per agent at Admin → Agents → Working Hours.

Approvals on mobile

Freshservice change approvals work cleanly on mobile. Approvers can read the change details, see linked CIs, and approve or reject. Use this as your channel of choice for time-sensitive changes.

Mobile approval payload includes:
  - change.subject
  - change.risk
  - change.impact
  - linked CIs (read-only summary)
  - approver action: approve / reject + comment

Offline behavior

The app caches recent tickets but not full history. Replies composed offline queue and send on reconnect. Custom field updates often fail silently offline — do not rely on offline custom field edits.

App version drift

Freshworks ships frequent app updates. Force-upgrade after major Freshservice releases. Older app versions may not render new field types (multi-select, lookup) correctly.

What to do this week

Audit mobile-agent ticket forms for complexity, set quiet hours per agent timezone, shift change approvals to mobile, and push your team to the latest app version after every quarterly release.

[object Object]
Share