Industry · Service teams
Customer operations for teams that book time.
Clinics, studios, repair shops and agencies. Requests arrive as messages and the work is a booking, a reschedule or a follow-up. BlendDesk runs those as jobs, with hard guardrails on the questions a model should never answer.
Illustrative demo with fictional data.
What it looks like
A request, three slots, a booking and a guardrail.
Nile Physio is fictional. The shape of the conversation is not.
The request arrives
Someone asks for an appointment on WhatsApp. The thread opens with their history attached, so a returning patient is not treated as a stranger.
Scout checks real availability
It calls the booking tool you connected and offers only slots that exist. It cannot offer a slot it did not read.
The booking is confirmed
The chosen slot is written back, confirmed in the thread, and a reminder is scheduled as a utility template before the appointment.
The clinical question stops it
A question about whether the treatment is safe after surgery hits a hard guardrail. Scout does not answer; it hands the thread to the clinic team with the question highlighted.
Start here
The jobs behind a booking.
A service business runs the same mechanisms as a store, pointed at a calendar rather than a warehouse.
- Lead qualificationService messageSort enquiries before a person replies, and route by service and location.
- Order statusService messageThe same lookup pattern, pointed at a booking instead of an order.
- Order confirmationUtility templateAppointment confirmations and reminders, as utility templates.
- AutomationsReminders, reschedules, no-show follow-ups and SLA escalations.
Guardrails
Some questions must never be answered by software.
A clinic is the clearest case, but every service business has its own version of this list.
- Clinical or legal advice
- Never answered. The thread is handed to a qualified person with the question highlighted.
- Prices not in your published list
- Never quoted. Scout says a person will confirm, and a person does.
- Cancellations and refunds
- Proposed by Scout, executed only after a human approval that is recorded in the trace.
- Anything outside the scenario
- Escalated rather than improvised. Meta's policy requires a human escalation path, and the handoff carries the full history.
Source: WhatsApp Business Messaging Policy, updated 23 September 2026.
Answer → Resolve → Act → Improve
The lifecycle of one request.
The same four stages, with a calendar at the centre instead of an order.
- Answer
- WhatsApp, Instagram, email and web chat arrive in one thread per person, with their previous visits and notes beside it.
- Resolve
- Scout answers what you have approved — opening hours, location, preparation, pricing pages, cancellation policy — and nothing else.
- Act
- Book, reschedule, cancel and remind, against the calendar you connected, with approvals wherever a change affects a person's time or money.
- Improve
- Score the agent against real past requests, see which ones it should never have handled, and tighten the scenario before anybody complains.
Message economics
Reminders are utility. Offers are not.
An appointment reminder is about a booking the customer already made, so it is a utility template. A promotion for a new treatment is marketing, at roughly eighteen times the rate.
- Appointment reminder (Egypt)
- $0.0036
- Utility template — about an appointment the customer already booked.
- Promotional message (Egypt)
- $0.0644
- Marketing template, requiring opt-in. About eighteen times the utility rate.
- Answering a question they asked
- Service message
- A message from the customer opens a 24-hour window. Meta began charging for service messages on 1 October 2026, with the first 1,000 per business phone number per month free.
Source: Meta WhatsApp per-message rate card, Egypt, retrieved 2 November 2026; category, window and service-message rules from Meta developer documentation.
Meta bills these fees, not us, and we never mark them up. BlendDesk charges for seats and AI resolutions.
Questions buyers actually ask.
Will Scout give medical or legal advice?
No. That is a hard guardrail, not a prompt instruction: the category is blocked and the thread is handed to a qualified person with the question highlighted.
Can it book into our calendar?
If the calendar or practice-management system exposes an API, it is connected as a tool and the call shows up in the trace. Booking is a state change, so you decide whether it needs an approval.
What about no-shows?
Reminders go out as utility templates before the appointment, and a no-show triggers a follow-up automation that offers the next available slot rather than a phone call that never happens.
We have several branches. Does routing handle that?
Yes. Location is a captured field, and routing rules send the thread to the branch team that can actually serve it, with an SLA on the queue.
How do we know what the agent said to a patient last Tuesday?
Open the run trace: what it read, what it decided, which tool it called, which guardrail fired and what was sent, in order, with timings.
Bring your booking flow.
Book a demo and we will run a real request end to end — availability, confirmation, reminder and the guardrail that stops it.