Interactive example
The report, with the controls working.
Switch the period, filter by workflow, read the chart bar by bar, and work through the queue of things waiting on a person. Sample data, so the shape is the point.
Calls answered
64
this week
Texts sent
82
this week
Bookings made
24
this week
Reviews requested
16
this week
All workflows · this week, by day
186 in totalWaiting on a person
5 waiting · 0 handled- Who
- Mara Lindqvist
- What
- Rear fence, roughly 30 metres, with two gates
- Reach
- Replied by text; prefers a call after 5 pm
Why it is waiting
A fence quote needs a look at the ground first, so the request is held for a person rather than priced from a message.
- Who
- Dev Raman
- What
- Wants to talk through a warranty claim on last month’s job
- Reach
- Any time after 3 pm, on the number he called from
Why it is waiting
When a caller asks for a person, the line takes a message and stops there. The claim is yours to handle, with the message attached.
- Who
- Priya Castellano
- What
- Move Thursday 10:00 to a Saturday after 4 pm
- Reach
- Text, same number
Why it is waiting
Saturday after 4 pm is outside the hours set for booking, so the Thursday slot is held and the change waits for you.
- Who
- Tom Achebe
- What
- Replied to the review request: the gate latch still sticks
- Reach
- Text, same number
Why it is waiting
A reply that mentions a problem goes to a person, not to a review link.
- .
- Who
- Hana Bishop
- What
- Full-day job: lift and re-lay a patio
- Reach
- Text, same number
Why it is waiting
Jobs marked as two-person are held until someone confirms the crew, then booked.
Handled
00Nothing yet. Items you mark handled move here.
What this is built from
Calls
Answered by the phone assistant, with what each caller asked for.
Texts
Sent from your business number: replies, reminders and confirmations.
Calendar
Bookings made, moved and freed, in the calendar you already use.
Review requests
Sent after a job is marked finished, and any reply to them.
A worked example. Names, times and details are scripted for the demo.
What it shows
Four questions it answers at a glance.
Enough to know whether the systems are doing their job, without opening four other tools to find out.
What came in
Calls the phone assistant answered, enquiries taken, and the ones that arrived outside working hours.
What went out
Texts, reminders, confirmations and review requests, with the time each one was sent.
What was booked
Appointments made, moved and freed up, against the calendar they landed in.
What is waiting
Enquiries flagged for a person, and anything that has been sitting longer than it should.
Where it stops
Three things it deliberately avoids.
Reporting that overclaims gets believed once and distrusted permanently. These are the lines it holds.
It reports activity, not revenue
Saying a system earned you money means knowing what would have happened without it, which nobody does. It reports what happened and leaves the arithmetic to you.
It does not score your team
It is there to show whether the systems are doing their job, not to rank the people around them.
It does not replace your customer records
Where you already keep them somewhere, that stays the place they live and this reads from it. Two systems disagreeing about the same customer is worse than either one alone.
Questions
Practical detail.
An add-on to an automation plan, from $199 a month.
It is added on top of a plan rather than sold on its own — a report with nothing running behind it has nothing to report.
Related reading