Freshservice

The Onboarding Reality: What Happens When You Open Freshservice

Freshservice hits you with a login screen immediately. No guest mode. No demo without an account. If your organization does not use Freshservice, you cannot get past this wall. For IT agents who do have credentials, the app loads into a dashboard that shows your open tickets, pending tasks, and a "To-Dos" list. The interface is clean but sparse compared to the web version. The first thing you notice is the notification bell. It promises to keep you updated. But that promise breaks quickly for many users.

Real experiences show a pattern. Multiple users report that notifications do not sync with the desktop app. You clear a ticket on your laptop, but the phone still shows it as unread. Other users say notifications appear very late unless the app is open. One reviewer described the notifications as "awful" and recommended muting them entirely. This is not a minor glitch. For an IT agent who depends on real-time alerts, a broken notification system defeats the purpose of a mobile app. You open the app expecting to see what needs your attention. Instead, you see stale data or nothing at all.

The "To-Dos" module sits at the center of the mobile experience. Freshservice markets it as an industry-first feature that lets agents prioritize their day in a single window. In practice, it shows a list of tasks assigned to you. You can mark them complete, adjust priorities, or add notes. The module works as described, but it does not solve the notification problem. If you do not know a ticket was assigned to you, the "To-Dos" list only helps after you open the app. Agents who rely on push notifications find themselves opening the app manually throughout the day just to check for updates. That defeats the "on the go" flexibility the app promises.

How Two Features Clash in Real Workflows

Freshservice offers a barcode and QR code scanner for asset management. You can point your phone at a laptop or monitor, scan its asset tag, and pull up its full record in the CMDB. This works well when the app is responsive. The scanner is fast, and the asset details load quickly. But the scanner lives inside the same app that freezes on the logo screen for some users. If you are in a server room scanning dozens of devices, a freeze forces you to force-kill the app and restart. That breaks your workflow.

The asset scanner also depends on the app's backend sync. If the app is frozen or struggling with background data, the scanner may not load at all. One user noted that the app's background data method seems to use something other than FCM, which is generally faster and more reliable. This creates a cascading problem. The asset scanner is useful, but the app's instability makes it unreliable in high-pressure situations. IT agents who manage large inventories may prefer the desktop version for bulk updates. The mobile scanner works best for quick, single-device lookups when the app behaves.

Another workflow clash involves the "To-Dos" module and the ticketing system. The "To-Dos" list shows your assigned tasks, but it does not show the full ticket history or all associated comments. To see those details, you must open the ticket itself. This adds extra taps. If you are working through a long list of tickets, the extra navigation slows you down. The app offers 9+ default views and unlimited custom views, but these views only organize tickets. They do not reduce the number of steps needed to act on a ticket. Users who want a streamlined mobile experience find the app clunky and missing features.

The Real-World Performance: Ads, Bugs, and Crashes

Freshservice does not show ads. It is an enterprise tool, so the focus is on functionality, not monetization through advertising. But the app has a different kind of friction: bugs and crashes. Multiple users report that the app freezes on the Freshservice logo and never loads. The only fix is to force-kill the app in settings and reopen it. This cycle repeats for some users daily. One reviewer called the app "borderline unusable" because of this issue.

Background freezing is another common complaint. The app stops responding when left in the background for a while. When you return to it, it may be frozen or slow to respond. This affects notifications as well. If the app is frozen in the background, it cannot receive push notifications reliably. Users report that notifications appear very late unless the app is open. This creates a catch-22. You need notifications to know when to open the app, but the app only works well when it is already open.

The app's performance issues extend to specific modules. The Projects module, for example, hangs or becomes unresponsive for some users. Workflow automations can break after orchestration automations are applied. These are not isolated incidents. The Freshservice outage history shows 75 outages since March 2023. Performance degradation in the US region occurred in June 2026. The Middle East region experienced a partial outage due to connectivity issues with the cloud provider. These outages affect both the web and mobile versions, but mobile users feel them more acutely because they cannot switch to a different device easily.

On the positive side, the app's core ticketing functions work when the app is stable. Creating tickets, assigning them to agents, changing priorities, and adding private notes are all straightforward. The canned responses feature saves time for common replies. The search function for users and knowledge base works well. Users who can tolerate the bugs find the app useful for quick updates and on-the-go responses. But the stability issues remain a significant barrier to consistent use.

Version History and What Actually Changed

The most recent changelog for Freshservice introduces an Email AI Agent. This feature auto-resolves employee requests over email using the knowledge base. It deflects repetitive tickets, but it requires setup in the web version. The mobile app benefits from this because fewer repetitive tickets reach agents, reducing the overall workload. However, the Email AI Agent does not fix the notification or freezing issues. It is a backend improvement that agents may not notice directly.

The changelog also notes that business rules set on service items are now honored on journey tasks. This is a behind-the-scenes fix that improves workflow consistency. The "minor bug fixes and improvements" line is vague. It does not specify which bugs were fixed. Given the complaints about freezing, notifications, and background performance, users would benefit from more transparency about what was actually addressed. The lack of detail in the changelog makes it hard to know if the developers are working on the most critical issues.

Version history from APK sites shows multiple updates in 2026. Versions 8.9.1, 8.9.2, and 8.11.1 were released between May and July 2026. The frequent updates suggest active development, but the persistent complaints about the same issues indicate that the fixes are not reaching the root causes. The app size varies between 55MB and 224.3MB depending on the version and architecture. This is not unusual for enterprise apps that bundle multiple features and libraries. But the size does not correlate with stability. The app remains buggy despite the updates.