Operator guide · Bookings · 7 min guide

A WhatsApp booking is a request until your team confirms it.

An automated WhatsApp flow should collect the details your team needs, check them against the rules you approved, and save the result as a pending request. A staff member then confirms, offers another time or declines, and the customer is told the outcome. Nothing is described to the customer as confirmed until that approval happens, and anything outside the agreed rules goes straight to a person.

Reviewed by: HumAI delivery teamLast reviewed:

01

Agree what “pending” and “confirmed” mean

Most booking confusion comes from a customer believing a slot is held when it is not. Define the states before building anything, and use the same words in the customer message, the staff view and any report.

  • Pending: details collected, waiting for staff
  • Confirmed: a named staff member approved it
  • Alternative offered: waiting for the customer to accept
  • Declined or cancelled: closed, with a reason recorded
02

Collect only the fields the approver needs

List the fields your staff actually check before saying yes: service, preferred day and time, branch, name, contact number and any rule-specific detail such as a referral or a deposit policy. If a required field is missing, the flow asks for it once, in plain words, rather than guessing. If the customer cannot provide it, the request is saved as incomplete and marked for a person.

03

Offer alternatives without promising them

Where your system allows availability to be read, the flow can suggest open times. Where it does not, it can ask for two or three acceptable windows instead. Either way, the suggested time is still a request: staff confirm it, because calendars change and some bookings need judgement about who should see the customer.

04

Illustrative record (not a real customer)

This is the kind of summary a staff member receives. It is labelled Illustrative: the clinic, the person and the details are invented to show the structure.

  • Request: dental cleaning, main branch
  • Preferred: Tuesday after 4 pm; also accepts Thursday morning
  • Customer: name and number captured; first visit
  • Missing: none. Insurance question answered from approved information
  • Status: pending staff approval
  • Exception noted: customer mentioned swelling, so the request was flagged for a staff call before booking
05

Write the exceptions down before launch

Some messages should never be handled as a routine booking: urgent symptoms, complaints, requests for a specific practitioner outside their schedule, group or corporate bookings, or anything the approved information does not cover. Each exception gets a route — who receives it, how fast, and what the customer is told meanwhile.

06

Close the loop with the customer

After approval, the customer receives the confirmed time and any preparation notes your team approved. If staff offer a different time, the customer can accept or ask for another. Track how long requests stay pending; a fast reply that leads to a slow confirmation still leaves the customer waiting.

A safe booking flow has

  1. 01Clear pending and confirmed states
  2. 02A short list of required fields
  3. 03Alternatives that staff still confirm
  4. 04Written exception routes
  5. 05A confirmation message after approval
  6. 06A measure of time spent pending

Sources and further reading

Read next

All guides