Automation

on site

A check-in, as the lone job ends.

When a field service job flagged for lone working reaches its expected finish, an agent messages the engineer on WhatsApp and asks them to check in. Describe it once in Agent Builder. A separate run later reads which lone jobs are still open, and emails the manager. It does not wait on a reply.

how it runs
Built once in Agent Builder, then runs on its own.

how it runs

From a sentence to the manager.

Ben Hale's grounds job at Riverside Care was due to finish at 16:00 on Fri 16/10. This is the agent described and tested, and Matt emailed about the job still open.

01

Describe it

Say when to message and who gets it. Agent Builder plans it: read lone jobs due to finish, then message each engineer on WhatsApp.

One sentence to describe it

01 / 03

before and after

The same lone job, two ways.

Ben Hale's grounds job at Riverside Care, due to finish at 16:00 on Fri 16/10, and Dylan's void still open at 17:30.

  1. The finish

    Without Centrus: Someone remembers to ring at the end of the day

    With Centrus: Asked on WhatsApp as the job reaches its finish

  2. The job

    Without Centrus: A missed call, and no note of it

    With Centrus: Ben closes the job, so it drops off the list

  3. Still open

    Without Centrus: Noticed the next morning, if at all

    With Centrus: Read from the job at 17:30

  4. The manager

    Without Centrus: Hears about it when he next asks

    With Centrus: Emailed the site, the job and the engineer

Centrus AI

in the 30 minutes

  1. 01We start with how your operation actually runs, on the desk and in the field.
  2. 02We show "Lone worker check-ins chased when missed" on a setup that matches yours.
  3. 03We pick out the admin that should run itself first.

Book 30 minutes. Watch it run once.

Found the agent you need, or doing something that isn't on the list? Bring the job you want handed over, and we will show it on a setup like yours. You leave with a plan.

30 minutes / UK team / No lock-inOr see pricing