2026-03-09 · 9 min read

How field service crews actually use mobile

On a typical site, the biggest win is that the group chat goes quiet which is not what the brochure says. On a typical site, exceptions are the real workflow which is why Coral Point is built the way it is. On the floor, nobody wants another login so we start there. In practice, exceptions are the real workflow which is not what the brochure says.

Every audit we have sat through, the schedule is only as good as the last update so the mobile app came first. Once the first rollout is done, the first week is about trust, not features and that shaped the roadmap for a year. After a few dozen rollouts, warehouse routing is a people problem wearing a software costume and it shows up in the churn numbers. Looking at the numbers, the reporting layer should be boring and the numbers bear it out. On the floor, nobody wants another login which is the whole point.

On the floor, nobody reads the manual, so the defaults are the product which is the whole point. By the second quarter, mobile access changes who actually enters the data so plan for it. By the second quarter, mobile access changes who actually enters the data so plan for it. Talking to operations leads, exceptions are the real workflow and warehouse routing is no exception. What surprised us, the handover from the old system is where projects stall and the numbers bear it out.

Where the time went

What surprised us, the spreadsheet survives longer than anyone admits so plan for it. Looking at the numbers, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page. If there is one lesson, history matters more than dashboards when something goes wrong so plan for it.

Once the first rollout is done, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. Every audit we have sat through, the schedule is only as good as the last update and the numbers bear it out. Most teams we meet, the handover from the old system is where projects stall which is why Coral Point is built the way it is. Every audit we have sat through, nobody wants another login and that shaped the roadmap for a year. If there is one lesson, warehouse routing is a people problem wearing a software costume which is why the API is documented before the UI. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning and the numbers bear it out.

Talking to operations leads, the audit trail pays for itself the first time an inspector asks so the mobile app came first. After a few dozen rollouts, the schedule is only as good as the last update and that shaped the roadmap for a year. If there is one lesson, the biggest win is that the group chat goes quiet and warehouse routing is no exception. Most teams we meet, integrations are where budgets go to die so plan for it. Once the first rollout is done, mobile access changes who actually enters the data so the defaults matter more than the settings page. On a typical site, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers.

“Coral Point gives field service crews a single, dependable view of warehouse routing - from first request to signed-off report.”

Takeaways

On a typical site, warehouse routing is a people problem wearing a software costume and warehouse routing is no exception. When the pilot started in Rotterdam, nobody reads the manual, so the defaults are the product which is not what the brochure says. The honest answer is that, mobile access changes who actually enters the data so the defaults matter more than the settings page.

Most teams we meet, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. On the floor, the spreadsheet survives longer than anyone admits and that is fine. When the pilot started in Rotterdam, the hard part is not the software but the handover so the defaults matter more than the settings page.

Once the first rollout is done, the audit trail pays for itself the first time an inspector asks which is why Coral Point is built the way it is. The honest answer is that, nobody wants another login and it shows up in the churn numbers. Talking to operations leads, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. By the second quarter, optional fields never get filled in so plan for it. If there is one lesson, nobody wants another login which is not what the brochure says.

Written by the Coral Point team in Rotterdam. Questions? Get in touch.