A veterinary chain ended the 8am phone rush with online booking that respects the schedule

Representative examplesEvery case study in this library is an illustrative composite of the kind of engagement we deliver — written to show our method and standards, not to name clients.

Where they started

Four veterinary practices across neighbouring suburbs, each with its own consulting rooms, reception desk, and head vet, run as one chain with a phone number per site. Consults are booked by phone almost exclusively, and mornings begin with owners calling before work — the receptionists spend the first hour of every day as telephone operators. Each practice holds its own appointment records and has evolved its own booking habits over the years; the chain has no shared view of capacity across its four calendars and no online presence for booking at all.

What it was costing

All four practices took bookings by phone, concentrated in the 8-9am rush when owners call before work. Hold music, abandoned calls, and double-booked consult rooms were daily facts — and after-hours emergencies filled the line, drowning the bookings.

What they could see

• The phones open to a queue at eight; callers hear hold music while reception juggles walk-ins at the desk in front of them.
• Two vets arrive for the same consult slot in the same room because each practice double-books its own way.
• After-hours emergency calls land in the same queue as routine booking requests, and urgent callers wait behind them.
• Reception telephones the day's patients one by one from a printed list to remind them of appointments.
• Reception staff had heard automation means redundancy and greeted the project with the enthusiasm of people clearing their desks.

The constraints we worked inside

• Vet time is the constraint: bookings must respect consult length per appointment type, not just slots.
• Emergency calls must always reach a human — the phone line cannot become a booking menu.
• Reception staff feared being automated out of a job; the design had to make them clearly more valuable.

What had been tried before

A temporary receptionist was hired to cover the morning phones across the two busiest practices.

The queue outlasted the budget line; adding a second voice moved callers from one hold queue to a different hold queue.

A booking request form was added to the chain's website for routine appointments.

Requests landed in an inbox nobody owned; by the time reception read them, owners had already phoned anyway, and the form trained nobody.

The phone system was upgraded with queuing and callback options before we were involved.

Queues manage callers; they do not reduce them. The eight o'clock problem arrived just the same, now with a callback feature nobody trusted.

What we proposed

Routine consults move online into real per-vet calendars, where each appointment type carries its own duration — vaccinations, checkups, and follow-ups no longer consume identical slots. The phone stays what it must be: urgent calls reach reception first, and after-hours emergencies route to the on-call vet directly, tested end to end before launch. Around each visit, workflows handle the reminders, prep instructions, and follow-up checks that currently consume reception's mornings, while reception keeps every part of the day that needs a human voice — and stops dialling the reminder list one patient at a time.

Just as important is what we ruled out, and why:

• A standalone booking SaaS — It would book the slots but not own reminders, follow-up, or emergency routing — a second system for reception to babysit.
• A full phone-tree booking menu — Emergencies must always reach a human, and an owner with a sick animal will not navigate options first.
• Booking through social media and email — Channels nobody staffs reliably at eight in the morning recreate the queue with worse visibility; bookings need to land in real calendars.

How the work ran

Delivered by the systems pod — automation specialist over 6 weeks, with working increments reviewed with the client every week.

The stack, and the reasoning

GoHighLevel calendars

Per-vet calendars with real durations per appointment type; the alternative — generic slots — is precisely how double-booked rooms happened.

Opportunities & Pipelines

Each booking is an opportunity moving through preparation, visit, and follow-up, giving reception one live picture of the day instead of a printed list.

SMS/email reminders

Reminders, prep instructions, and post-visit checks send themselves; no-shows and phone volume both fall as a consequence rather than as a target.

After-hours routing

Emergency calls route to the on-call vet directly with a tested fallback chain; the booking line never becomes a menu.

What went wrong

How we worked together

Cadence

A pilot at one practice with a weekly Thursday call alongside its practice manager, then a fortnightly rollout call per remaining site with the same agenda.

Client side

Practice managers owned staff adoption at each site; head vets owned the appointment-type durations only they could judge.

Decisions

The pilot practice set the defaults, and the other three held veto points over anything that touched their consult rooms — most vetoes were about vaccine lengths.

They provided

Each practice's appointment-type list with realistic durations, access to the on-call rota, and front-desk time for training on the pilot site.

What changed

The headline: 8-10am inbound call volume, measured across the first full month — −57%, read from Phone system logs. A second check: double-booked consult rooms since launch at 0.

Mornings changed shape: reception greets owners in the lobby instead of apologising into a handset, and the eight o'clock queue thinned to the calls that genuinely need a person. The reception team, who expected to be automated out of a job, instead stopped dialling reminder lists by hand — and were the system's loudest defenders within a month. Head vets start consult days on time because the calendar finally respects what a vaccination actually takes.

The result was read from Phone system logs against the pre-engagement baseline over the stated window, with a guardrail check on double-booked consult rooms since launch. Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.

What they own now

• Per-practice calendar configurations with the duration table each head vet signed off.
• The reminder and prep-instruction message templates, editable by practice managers.
• The after-hours routing setup with a documented rota-update procedure and fallback chain.
• A training recording for new reception staff covering the pilot site's routine.
• A per-practice dashboard of bookings, no-shows, and call volume for the chain's managers.