Appointments booked while the enquiry is still warm
Someone asks for a time on WhatsApp, the phone or a web form. The system reads the request, checks what is genuinely free in the calendar you already run, books it, confirms it, and reminds them. What it cannot answer, it hands to a named person with the reason attached.
The workflow, end to end
- Integration
The request arrives
A WhatsApp message, a call, a web form or a portal enquiry. All of them land as one request rather than in four different inboxes.
- Automated
It is read for what was actually asked
Who it is, what they want, where, and when they can come. A returning customer is matched to their record instead of being asked again.
- Automated
Real availability is checked
Against the working calendar: staff on duty, room or bay capacity, service duration, travel or buffer time, and the rules you set for how far ahead a slot can be offered.
- Automated
The slot is written and confirmed
Written into the calendar or system your team already works in, then confirmed to the customer on the channel they wrote from. There is no second diary to reconcile.
- Your team
Anything unclear stops and names a person
An urgent or clinical question, a request with no suitable slot, a payment or consent problem, or a customer who wants to negotiate goes to a named member of staff with the message and the reason attached.
- Automated
Reminders, changes and no-shows are worked
Reminders go out before the appointment, cancellations and reschedules are handled in the same thread, and the freed slot goes back into availability without anyone watching for it.
It books into the calendar you already run
Your practice management system, dealer management system, CRM or shared calendar stays the system of record. The booking is written there, under permissions you grant and can withdraw. Nothing is migrated and your team does not get a second place to look.
Availability is the hard part, not the chat
Anyone can send a reply. What makes a booking system useful is refusing to offer a slot that does not exist: duty rosters, capacity, service length, buffers, and the rules about how far ahead and how late a booking may be taken. Those rules are agreed in writing during the design stage and enforced in the build.
The customer never waits for office hours
Requests arriving at night, over a weekend or during a rush are answered in seconds rather than on the next working morning, in the language they were written in. That is when most enquiries are lost.
A person still decides the things a person should
The system books, reschedules and reminds. It does not judge urgency, give advice, or approve exceptions. Where the request needs a human, it stops and says why rather than producing a confident answer.
What you get
A working booking system on your data
Answering on your channels, booking into your calendar, running against your rules.
The rules, written down
Availability, approvals, escalation and reminder policy agreed before the build and documented afterwards.
An exception queue with owners
The short list of requests that genuinely need a person, named and timed.
A management view
Bookings made, cancellations, no-shows, exceptions waiting and how long they have waited.
Where it fits
Healthcare
Clinics and multi-site providers: appointments, intake and coverage checks before arrival. Live today as Ideora Health.
Automotive service
Service centres and dealer groups: bookings against real bay and advisor capacity. Live today as Ideora Auto.
Real estate
Brokerages and developers: site visits and viewings booked against an agent’s real calendar. Live today as Ideora Property.
Dental, diagnostics and veterinary
The same shape as a clinic: recurring visits, recalls, preparation instructions and a front desk that should be working exceptions, not a phone queue.
Salons, spas and fitness
Service duration, the specific person requested, and chair, room or class capacity, with waitlists when a slot frees.
Professional services
Legal, accounting and advisory consultations: intake questions answered first, then a slot with the right fee earner, and conflicts or eligibility routed to a person.
Home services and field visits
Installation, repair and survey visits booked against an engineer’s route and working hours rather than a promise to call back.
Education and coaching
Demo classes, admissions interviews and tutoring sessions booked against a teacher’s timetable, with reminders that cut the no-show rate.
What it connects to
These are the systems this workflow usually runs on. Anything outside the set is scoped as work, priced, and agreed before the build rather than absorbed into the timeline.
What you keep control of
What it may book without asking
Which appointment types complete on their own, and which wait for a person, is agreed in writing at the design stage and changed by you afterwards rather than by a model update.
The rules that decide a slot
Working hours, duration, buffers, capacity, how far ahead a booking may be made and how late it may be changed. Your rules, stated explicitly, enforced in the build.
Escalation and who owns it
Every case the system will not answer has a named owner and a reason attached, so an exception queue is a short list of real decisions.
A full record of every booking
What came in, what was matched, what was written and when. You can reconstruct any appointment end to end without asking us.
Questions we get asked
- Do we have to change our calendar or booking software?
- No. It books into the system you already run. If a direct connector does not exist, we agree a supervised route at the scope call rather than asking you to migrate.
- What happens when someone asks for a time that is not free?
- It offers the nearest alternatives that genuinely exist. If none of them work, the request goes to a person with the conversation attached rather than sitting unanswered.
- Can it handle cancellations and rescheduling?
- Yes, in the same thread as the original booking, and the freed slot goes back into availability immediately.
- Will it answer questions that are not about booking?
- Only the ones you have approved. Anything clinical, legal or commercially sensitive stops and names a person. That boundary is agreed in writing before anything is built.
- We are not in healthcare, automotive or real estate. Can you still build it?
- Yes. Those three run in production today, so the pattern and the connectors are proven. For another operation it is a fixed-scope build against your rules, and we will say at the scope call if we think it is a poor fit.
Book a call about your booking process
Thirty minutes on how appointments reach you today, where they wait, and which part a system can take first. You keep the map either way.