Field service: mobile app and dispatch portal for B2B…

Mobile and web development

The Challenge

Opaque field status and phone chains

Technicians documented via messenger, SMS or paper. The control centre could not see reliable job progress; escalations surfaced too late.

Dispatchers called repeatedly because photos, materials and times never arrived centrally. Customers waited for updates although work was already done.

We needed visibility in the field—not another WhatsApp group per region.

ERP and field teams without a shared language

ERP knew orders and invoices but not live locations or media on tickets. Conversely, material postings and completion times from the field were missing in ERP.

Dispatchers switched between ERP screens, phone and messenger to reconstruct job status—error-prone at high daily volume.

Target state: one ticket, one status, offline-capable

Leadership and dispatch wanted near-real-time status, mandatory documentation and ERP back-sync without media breaks—even in dead zones on industrial sites and rural routes.

Technicians should work without training marathons; dispatch needed skills, priorities and capacity in one portal.

Emergency jobs and maintenance contracts should share one priority logic—visible to control centre and field teams.

Executive reporting should come from the same system as operational field status—without Excel consolidation.

Technicians should capture materials and time once—without double entry in ERP at end of day.

Our Solution

Mobile UI and web back office

Mobile architecture and central job logic

The app guides tickets with required fields, photos and time capture; data is stored locally in dead zones and synced safely later. Dispatchers manage priorities and skills in the web portal.

Built along our web and mobile development service; examples in the app development blog category.

Phase 1: app rollout and offline buffer

Pilot regions received the Flutter app first with local SQLite buffer and conflict rules for concurrent edits. Signatures and photos attach to the job in an audit-safe way.

Onboarding used short workshops; required fields prevent empty completions.

Offline queue was tested under real dead zones on industrial sites.

Pilot regions validated sync conflict rules before nationwide rollout.

Phase 2: ERP connectivity and monitoring

ERP connectivity uses versioned REST and webhooks; monitoring surfaces integration issues before customers notice.

OpenAPI docs and a sandbox ease follow-on changes by internal IT.

A job is truly done when status is in the system—not when someone calls the control centre.

Results

Faster response, fewer callbacks

The control centre sees near-real-time status instead of guesses; rework from missing photos or dimensions decreased. Escalations surface earlier because required fields block incomplete closes.

Materials and time flow into ERP without double entry.

Average callbacks per completed ticket dropped in the first rollout region versus the prior period.

Customer satisfaction improved because completion status and photos appeared promptly in the portal.

Measurable effects after rollout

Internal metrics show shorter response times on emergencies and fewer callbacks per completed ticket.

Dispatch plans capacity from reliable actual data instead of phone callbacks.

ERP sync errors surface via monitoring before finance starts manual corrections.

Engineering and architecture were delivered by Groenewold IT Solutions in Leer (East Frisia)—Made in Germany with phased regional rollout.

Field UX and offline strategy

Required fields without bureaucracy

Technicians capture status, photos and time in guided steps. Validation runs before sync; incomplete closes stay marked locally.

Queue and conflict resolution

Local queues upload idempotently; conflicts follow a documented rule (office vs last field update) with audit entries.

Integration and operations

ERP webhooks and error transparency

Webhooks push critical status to ERP; failed jobs appear in a dashboard with retry and manual intervention.

Scaling by region

Phased rollout per region allowed lessons before nationwide use; feature flags ship new modules without forcing app-store updates for everyone.

Training materials and short videos for dispatchers and technicians were provided per rollout wave.

Security and privacy in the field

Device and token management

App installation follows MDM policies; API tokens rotate without forcing re-login during the workday.

Media and signatures are transmitted encrypted and stored on the job with permission checks.

Logging for audit

Status changes and sync events are logged audit-safely; exports for internal review are available on demand.

Retention periods for photos and personal data follow the customer's privacy policy.

Features

Feature overview

Flutter app for iOS and Android with offline support
Dispatcher web with capacity and priority rules
Media and signatures tied to the job
ERP sync via REST and secure authentication

Common questions about the field service app and dispatch portal

How does offline capability work for technicians in the field?

Jobs, photos, time and materials are buffered locally and synced idempotently when online—no data loss in dead zones. Required fields and media stay tied to the ticket. The stack builds on Flutter development with a robust sync layer, combined with app development and backend APIs.

Which devices and platforms are supported?

iOS and Android from one codebase; dispatchers use the web portal in the browser. Device policies (camera, signature, storage) are agreed with IT and field teams before rollout. Additional web features can be added via web app development.

How is privacy handled for photos, location and customer data?

Roles, tenant separation and encryption in transit and at rest; access only for authorised profiles. Media and signatures remain auditable on the job—not scattered in private messengers. Regulatory requirements shape architecture and operations, similar to GDPR-compliant software development.

How is ERP connectivity implemented for jobs and materials?

Versioned REST and webhooks; monitoring surfaces integration issues early. The system of record and conflict rules (office vs. field) are documented. We use API integration and, where needed, system integration.

How is rollout managed for field teams and the control centre?

Phased rollout by region; pilot with key users and training on required fields and escalation paths. Dispatchers learn priority and capacity rules in the portal; technicians start with a manageable job set. See also mobile app references.

Field service: mobile app and dispatch portal for B2B maintenance