The Zoho CRM mobile app on the road

This guide looks at the Zoho CRM mobile app: what field sales actually use day to day, and how an admin should set it up before the phones go out. Field sales means selling in person at the customer's site, rather than from a desk. The Zoho CRM mobile app is the phone and tablet version of Zoho CRM. It is available for Android and iOS through Google Play and the App Store.

A CRM, or customer relationship management system, is the system of record for your accounts, contacts, deals and pipeline stages. If that term is new, our short explainer on CRM covers the basics. The mobile app puts that record in your rep's pocket. The question for you is which parts of it they will open between visits, and which parts will sit unused.

The features field reps lean on form a short list. They check in at the customer, they record what was said by voice, they glance at the pipeline before and after a meeting, and they need all of it to work when the signal drops. The sections below take each in turn. Then comes the admin setup, a worked example, a checklist table and what it means for a UK business.

Why reps avoid the CRM, and what the app has to fix

The problem the app must solve is data entry. SPOTIO's 2026 State of Field Sales survey found that 65% of field reps spend five or more hours each week on manual CRM data entry. Only 3% of teams have fully automated the process. The same survey found that reps spend only about a quarter of their time on direct selling and customer conversations.

Zoho reports a similar picture on its own page for sales reps: 71% of sales reps say they spend too much time on data entry. A Zoho community article gives the reason. Most sales representatives are not fond of using a CRM because they enter data manually and spend hours making reports.

When a rep waits until the evening to type up a day of visits, details go missing. LogicNotes, a field sales software company, notes that many CRMs are still slow to update from the field, especially on mobile. SPOTIO's survey also ranked lack of visibility due to missing or incorrect data as the second internal challenge for the B2B field sales leaders it asked.

So judge the app by one test. Can a rep capture a visit in the car park before driving on to the next call? A guest post on Zoho's blog in 2013 put the principle well: the key to a successful CRM implementation is a win-win for sales reps as well as their management. Managers only get clean data if reps get time back.

Check-ins: proof of the visit without a report

A check-in is a tap on the phone that records a rep's visit at a customer's location. The Google Play listing for the app describes it plainly: check in at a client's location to record your visit. The rep does not write a visit report to show they were there. The record does it for them.

Check-ins sit alongside the map features. Zoho's mobility page says prospects can be viewed as clusters in a map view, and the Play listing says reps can locate customers and sales opportunities nearby and navigate to them. This is what reps use when a meeting cancels at short notice: find the nearest open account and call in instead of driving back.

Decide what a check-in is for

Settle the purpose before you switch it on. If it is for the rep's own activity history, say so. If managers will use it to review visit patterns, say that too, at rollout and in writing. The app listing declares that it may collect location data, and reps will notice. An unexplained location feature is a quick way to lose the team's goodwill.

Know the limit on territories

SPOTIO reports that territory management in Zoho CRM is a Professional-tier feature and is limited on the mobile app, with the map view better on desktop. The practical split is simple. Plan territories on the desktop, and let the phone handle the day's visits and check-ins.

Voice notes and call logs: capture before you forget

The second feature reps rely on is voice capture. The Play listing says reps can log calls and capture the details of the conversation by attaching voice notes. Caller ID shows when a lead or contact is calling, so the rep knows who is on the line before answering.

Zoho's mobility page goes further with Zia, the built-in AI assistant in Zoho CRM. It says reps can converse with Zia to capture notes, update deals, create tasks or make calls, and can ask Zia for a deal summary. Our post on what Zia actually does in Zoho CRM covers the wider picture. Check your edition first: SPOTIO reports that Zia's mobile features are limited to the Enterprise tier.

A voice note is raw material, not the record

Reports and dashboards read fields, not audio. Agree with the team which details must go into fields after every call, typically the next step, its date and any change to the deal. Everything else can stay in the recording. Without that rule, the most useful facts from a visit end up in audio files nobody replays.

One more capture feature earns its place. The app can scan a business card and convert it into a CRM contact. For reps who meet new people at trade events or on site, that removes another round of typing.

The pipeline on the road

A sales pipeline is the set of open deals grouped by stage, from first contact to won or lost. Our glossary entry on the sales pipeline explains the idea in full. On the road, reps look at it in short bursts: before a meeting to see what is open with this account, and after it to move the deal on.

Before the meeting: Related Lists

Related Lists show all the records linked to a parent record, such as the deals, tasks and events attached to an account. A rep who opens the account in the car sees open deals and recent activity in one place. From the deals list on that account they can press + New Deal to create a deal that is already linked to the account.

Across the day: dashboards

The Zoho CRM home page can carry dashboards such as Pipeline By Stage, Events, Tasks and Calls. Zoho's mobility page says interactive dashboards can be opened with voice commands. For a rep, Tasks and Events answer "where next"; for a manager, Pipeline By Stage answers "what is moving".

After the meeting: keep sensitive edits deliberate

LogicNotes recommends that sensitive stage, close-date, forecast and account changes stay human-managed. In practice, let reps update stage and next step from the phone, but treat close dates and forecast values as deliberate edits a person makes, not something a voice assistant fills in on its own.

Offline access and its gaps

Offline mode means the app keeps working without a signal and syncs, that is, sends your changes to the central CRM, when the connection returns. Zoho's mobility page says you can update information offline and sync later. The Play listing mentions offline access and automatic sync across devices.

SPOTIO describes Zoho CRM's offline mode as full: create contacts, update deals and log activities without signal, with sync on reconnect. In SPOTIO's comparison, Zoho CRM was among the tools with the fullest offline mode.

The need is concrete. LogicNotes lists where field reps lose signal: customer sites, conference halls, rural routes, basements and car parks.

Where the gaps are

The vendor pages tell you offline mode exists. They do not tell you exactly how each action behaves in your own configuration, with your custom fields, workflows and check-ins. That is the gap, and only testing closes it.

Run a flight-mode test before rollout. With the phone offline, create a contact, log a call with a voice note, move a deal stage and try a check-in. Reconnect, then open the desktop and confirm every item arrived as expected. Brief reps on the result, so they know what to trust when the signal goes.

The settings an admin sets before handing out phones

An admin is the person who configures Zoho CRM for everyone else. Five settings decide whether the app fits a rep's routine. Our guide on how to customise your CRM covers the desktop screens behind them.

A layout is the arrangement of fields on a record screen. Layouts can remove unwanted fields, and conditional layout rules show a field only once set criteria are met. Roles form your organisation's hierarchy, and Profiles set what each user can see and do. Workflows can send emails, create tasks and update fields, and the mobility page says reps can trigger custom workflows from the phone.

When Svennis sets up the app for a field team, we go through a normal visit with a rep on their own phone and remove every field they skip. We run the flight-mode test before go-live, because offline surprises are the complaint we hear most often afterwards.

Setting	What to set	Why reps care
Layouts	A short field layout for deals and accounts	Fewer fields to scroll past on a small screen
Conditional layout rules	Show extra fields only when a stage needs them	Screens stay short until detail is required
Roles and Profiles	Reps edit their own records; managers see the team	Clear access, and location data kept to those who need it
Workflows	Create a follow-up task when a call is logged	The next step appears without typing
Home dashboards	Tasks, Events and Pipeline By Stage	The day's plan on one screen
Offline test	Flight-mode test of every visit action	No surprises in a basement or on a rural road

Five settings decide whether the app fits a rep's routine, from layouts to workflows

	What it controls for the rep on the phone
Layout	Removes unwanted fields from the record screen
Conditional layout rules	Shows a field only once set criteria are met
Roles	Places each user in the organisation's hierarchy
Profiles	Sets what each user can see and do
Workflows	Sends emails, creates tasks, updates fields; reps can trigger them

Worked example: a five-rep B2B team

Take a small B2B team with five reps who spend most of their time visiting prospects, much like one described in a Reddit thread on field sales CRMs. The owner wants visits recorded and follow-ups kept. Here is a setup that follows the checklist above.

Roles and Profiles. Create a Sales Manager role above a Field Rep role. Give reps a profile that lets them edit their own accounts and deals, and give the manager visibility of the whole team.
Layout. Build a "Field Visit" layout on Deals with Stage, Next Step, Next Step Date and Amount near the top. Add a conditional layout rule that shows a Lost Reason field only when Stage is set to Closed Lost.
Workflow. When a call is logged against a deal, create a follow-up task for the deal owner.
Home page. Put Tasks, Events and Pipeline By Stage on each rep's home page.
Check-ins. Switch them on and tell the team in writing what is recorded and who sees it.
Offline. Run the flight-mode test on one rep's phone and fix anything that fails.

A rep's day then runs like this. At 8am they open Tasks and Events. At the first customer they check in, open the account's Related Lists, and after the meeting log the call with a voice note, move the stage and set the next step. The workflow adds the follow-up task. If a later meeting cancels, the map view shows nearby prospects.

LogicNotes advises starting a rollout with one bottleneck, one territory and one success metric. Here that could be one rep's patch, measured by how many visits have a next step recorded the same day.

What this means for a UK business

Two points matter most for a UK firm: signal and data.

Signal first. LogicNotes names rural routes, basements and car parks among the places field reps lose coverage. If your team covers rural areas or visits sites with poor reception, offline mode is not a nice extra. Make the flight-mode test part of your rollout, not an afterthought.

Data second. The Play listing declares that the app may collect location, personal info and other data types. The Play listing includes a data safety summary, but that is the developer's own label, not a contract. Before rollout, check Zoho's data processing terms and where your data is hosted. The listed developer address is in Pleasanton, California. Check-ins create a record of where your staff were, so write down why you use it, tell your reps before you switch it on, consider a data protection impact assessment, and limit who can see it through Roles and Profiles. Our sister site's page on UK GDPR is a useful starting point before you write that down.

Finally, confirm your edition before you plan. SPOTIO lists territory management as a Professional-tier feature and Zia's mobile features as Enterprise only. If your rollout depends on either, check what your licence includes before you promise it to the team.

Practical next steps

You can do most of this in a week without new software. Work through the list in order.

Ask two reps what they do between visits. Write down the five or six actions they repeat. That list is your mobile scope.
Cut the layout. Remove every field those actions do not need, and use conditional layout rules for the rest.
Set Roles and Profiles, with location visibility limited to those who need it.
Add one workflow that creates a follow-up task when a call is logged.
Run the flight-mode test and brief the team on what works offline in your setup.
Pilot with one territory and one measure, such as visits with a next step recorded the same day.

If your team is new to the system, start with the basics of Zoho CRM. If you would rather have the layouts, workflows and mobile setup built and tested for you, see how we approach Zoho CRM implementation.

Sources

Looking for a Zoho partner in the UK? Svennis has been a Zoho Premium Partner since 2011, with more than 200 implementations delivered. See how we work as a UK Zoho Partner.

Zoho CRM Mobile App: What Field Sales Actually Use Day to Day