Call MaggieOne diary that works for the people in it.
Built to help small businesses grow. For a company with field engineers and a department already running the bookings, she helps that department. She doesn't replace it.
What she does for a team today
All of this is built and in use. It runs on the Pro plan for firms of two to roughly thirty engineers; for a larger fleet, talk to us first.
A diary per engineer
Each engineer has their own diary. A job goes only to someone who does that kind of work.
The nearest engineer takes the job
She looks at where each engineer will already be and offers the slot beside the nearest job, so a new booking doesn't send someone across the county.
Morning run sheets
Each engineer is texted the day's jobs, in order, every morning.
Running late
An engineer texts "30 late" and the customers still to be seen that day are told.
A day off, handled
One code moves a whole day's jobs to other engineers or other days, and tells every customer.
Customers kept informed
Confirmations, reminders the day before, and the chance to move or cancel by text, so slots are refilled rather than lost.
Priority callers
Name the customers who matter most, a letting agent or a contract client, and the owner is texted the moment one of them rings.
Reminders to rebook
Annual services and certificates come due; customers are texted and book by replying.
Every call accounted for
A booking, a message or an enquiry that went nowhere: someone is told after every call, so nobody rings and goes unnoticed.
In development: the dispatcher's assistant
This is planned work, written here as a plan. It isn't available yet, has no price and no date. It's being built for companies with a scheduling team, to help that team.
What it's being built to do
- Nothing in a diary changes without a person approving it. The assistant proposes; a dispatcher decides. That's the whole design.
- Engineers ring the assistant, not the dispatcher, for "where am I next" and "I'm running late". It re-plans the rest of that engineer's day, tells the affected customers, and sends the dispatcher a one-line summary to approve or override.
- Overnight it checks tomorrow's diaries for impossible travel and clashes, and gives each dispatcher a short list to approve at 08:00.
- Keeping a change as it is asks for a reason from a short list, and the reason teaches the planner: a customer's preferred engineer is remembered, a skills gap is corrected, an access note is kept.
- Every approved change is credited to the person who approved it: the miles and the late visits they saved that week.
- Engineer skills and van stock, so a job goes to someone who can do it and has the parts.
Who it's for, and who it isn't
For the people already running the bookings. The assistant takes the calls and the re-planning they do by hand all day and hands back decisions, with the saving shown before the button. It doesn't take their seats.
The aim is a diary that's easier to run, fewer wasted miles, and customers told before they have to ask. Nobody's job goes; the day gets more efficient.
If your company has field engineers and a scheduling team, and the diary is the thing that wears people down, we'd like to talk before it's finished, so it's built around how your team actually works.
Register interest
No price and no sign-up for larger companies yet. Tell us about your team and we'll come back to you.
Email info@sunnysocialsltd.com
Or ring Sunny on 07503 423527
Say roughly how many engineers you have and what runs the diary today. That's enough to start.
A smaller team of two to thirty engineers can start today on the Pro plan. Also see: plumbers, garages.