Field Service

uFieldService

Engineer execution, native to Business Central.

Field service operations are often split across multiple systems and manual steps. uFieldService centralises the engineer-execution side of that workflow. Engineers receive digital work orders with customer details, asset history, work instructions and required materials — sourced from either the Project module or the Service module of Business Central, whichever fits the job. Engineers register their own time and time for coworkers, add materials by scan, work fully offline, communicate with customers from the app, and capture a customer signature on-site. Everything posts straight back to Business Central — no re-keying, no paper bridge.

uFieldService image 1
Functionalities · 10
uFieldService · Customer Communication

The customer hears from you, on the right day, at the right time.

"Engineer is 20 minutes out." "Running 30 minutes late — your slot is now 11:30." "Job complete, your signed report is attached." Sent from inside the work-order flow — by the engineer, the dispatcher, or automatically. No "I tried to call but…".

ETA notifications, automated
When the engineer flips to Travelling, the customer gets an ETA. When ETA slips, the customer hears about it before they wonder. Configurable per customer, per work type.
Signed report — instantly
On sign-off, the customer's preferred contact receives the signed work order with photos and parts breakdown. Branded, archived, on file.
Localised, branded templates
Per-customer language and branding. A Dutch customer gets Dutch; a German customer gets German — under your logo, your tone, your contact details. Templates configured once, applied everywhere.
What you see

The communication that customers actually want.

Customers do not want surprise visits, late surprises, or vague aftermaths. They want a window, an update if it slips, and a clean report afterwards. uFieldService sends those three things by default — in the customer's language, under your brand, on the channel they prefer.

  • ETA SMS / email when the engineer goes en route
  • Slip notifications when traffic or job overrun changes the ETA
  • Booking confirmation when an appointment is scheduled
  • Sign-off email with the signed report and photo evidence
  • Per-customer language and branded templates
  • Per-customer channel preference (email or SMS)
uFieldService image 2
When this matters

Signals you'd reach for this.

01
"What time are you coming?"
A customer call asking for an ETA is a customer who should already have one. Automated ETAs end the calls.
02
No-shows because the booking never landed
A customer who did not get a confirmation forgot or did not know. A booking confirmation closes that loop on day one.
03
Disputes start from silence
A customer who has not heard about the work since the engineer left is the customer most likely to dispute the invoice. A signed-report email closes the loop.
04
Customer language is ignored
A Dutch site getting English messages is subtle disrespect; cumulative damage. Per-customer language settings prevent it.
FAQ

The questions everyone asks first.

Still wondering? Ask us directly →

Email and SMS. Each customer can have their preferred channel set per message type; the system uses it automatically.

See uFieldService in a 30-minute demo.

A real screen-share with someone who built it. No slides.

The uTools suite

Other apps that pair well with uFieldService