Home/The assistant

What it handles

An assistant on the phone, not a phone menu.

Press one for bookings was never the answer. This picks up, listens, answers the question actually asked, and books the appointment, inside the same conversation the caller would have had with a person.

Four parts

The call, the booking, the messages, the record.

01

The call

  • Answers day and night, weekends included, with no queue
  • Speaks naturally, and copes with a caller who changes their mind mid sentence
  • Recognises a returning caller by their number
  • Passes to a person the moment it should, with the summary attached
02

The booking

  • Reads live availability, so a taken slot never gets offered
  • Holds the slot while the caller decides, then reads it back before confirming
  • Handles a reschedule or a cancellation on the same call
  • Respects appointment length, turnaround time, and who is qualified to take it
03

The messages

  • Confirmation by WhatsApp where a number exists, SMS where it does not
  • The business hears about every booking, on its own number
  • A reminder call on the day, early enough that a slot can be refilled
  • A review request once the visit is done, on the channel the client already used
04

The record

  • Every call written down as searchable text
  • What was asked, what was answered, and what was booked
  • Anything it could not answer flagged, so the gap gets closed
  • Export in full, at any time, in open formats

The diary under load

Push it past capacity and read what it says.

A booking system earns trust by being honest at the limit. Raise the demand past what the team can absorb and this diary names the requests it cannot place, rather than quietly squeezing them in on top of somebody else.

Long day, 09:00 to 19:00

Rules
Capacity
Bookings placed
--
Day ends
--
Diary filled
--
Rebuild
-- ms

Routine Priority Urgent

Demonstration diary. Every number here gets computed on this page, and none of it describes real bookings.

Diary assignments as text

    Turn off linked visits

    The diary fills tighter and the day ends sooner, because nothing waits on a first appointment. Neater, and wrong wherever the follow-up genuinely has to come second.

    Cut it to two people

    Watch the day stretch and requests fall past the end. That count is the honest cost of a thin rota, visible before the week starts rather than after.

    Open late slots

    Capacity appears, and the striped blocks show precisely which bookings bought it. Nothing gets hidden inside an average.

    Interfaces

    It has to sit inside the tools already in use.

    Interface types and the standard approach taken
    ConnectionApproach
    Phone numbersA new number, or a redirect from the existing one. The number printed on the van and the website stays exactly as it is.
    CalendarsGoogle Calendar, Outlook, and standard iCalendar feeds, read and written in both directions.
    MessagingWhatsApp Business and SMS, with the business name showing as the sender wherever the network permits it.
    Existing systemsDocumented HTTP interfaces with versioning, so a booking can land in whatever system already holds the customer list.
    Data exchangeOpen formats such as CSV and JSON, exportable in full, at any time, with no charge for leaving.

    Delivery

    What a build includes.

    • The answers it gives, agreed line by line before it ever takes a live call
    • A number you can ring yourself, as many times as you like, before anything switches
    • Calendar and messaging connected to the tools the team already opens
    • Escalation rules written down: what it passes to a person, and to whom
    • Plain English documentation, with the answers in a file anyone on the team can edit
    • A support window after go-live, with the scope written down rather than implied

    Ring it before you buy it.

    Ask for a number you can call yourself. Hearing it handle your own awkward questions tells you more than any demo video.