Cost

What a booking bot costs

A booking bot that writes into a real calendar is nine to fourteen delivery days. Slot availability and the confirmation message are quick. The cost is the race between two people booking the same slot, reminders that respect the Gulf working week, and cancellations that reach the diary staff actually use.

What a booking bot costs: effort, cost and what moves it

Fixed price: $5,040 USD
Delivery: Awaiting sign-off

Effort: 12 delivery days
Biggest cost driver: Slot holds and concurrency, not the booking screens
Commercial basis: Fixed price agreed before work starts; scope changes quoted separately
Year one, beyond the build: Support retainer, Managed hosting, plus calendar platform licences, deposit processing fees

As of 2025-10-01, Telegram Bot API 13.4

Why this costs what it costs

The demonstration version of a booking bot is genuinely simple, and that is what makes this category so frequently underquoted. Ask for a service, show some times, take a name, send a confirmation. Every part of that is straightforward, and a bot that does exactly that will work perfectly during a demo and cause a specific, predictable problem in its second week of real use.

The problem is the gap between showing a slot and confirming it. Two people open the bot within a few seconds of each other, both see four o'clock available, both tap it. Without a hold — a short-lived reservation taken before the confirmation flow starts and released if the user abandons — the second booking overwrites the first, or both land, and a receptionist finds out when two patients arrive together. This is not an edge case in a busy clinic; it is a weekly occurrence. Solving it properly means designing for concurrency, and that is a real portion of this estimate.

The second cost is the calendar itself. A bot with its own internal calendar becomes a second source of truth within a week, because staff will always also take bookings by phone and by walk-in, and they will always record those in the diary they already use. So the bot must write into that diary, read from it, and cope with a receptionist who moved an appointment by dragging it. That means token lifecycles, timezone handling, and reconciliation when the two views disagree — none of which exists in the demo version.

The third is reminders, which sound trivial and are where the local detail lives. A reminder sent at nine on a Friday morning in the UAE reaches almost nobody, because Friday is a short day or a day off depending on the business. Ramadan changes clinic hours entirely for a month. A bot that schedules reminders on a naive twenty-four-hour rule is measurably worse at reducing no-shows than one that understands the working week it operates in, and the difference is the entire reason the bot was bought.

The breakdown

Work	Days	Cost	What it covers
Service and availability model	2	$840	Services, durations, buffers, staff-specific availability, blackout periods and the rules about who can perform what. Where the real complexity of a clinic lives.
Booking flow	2	$840	Service selection, staff selection where relevant, date and time, contact details, and confirmation copy that is accurate about what is held and what is confirmed.
Slot holds and concurrency	2	$840	Short-lived reservations taken before confirmation and released on abandonment, so two people tapping the same slot cannot both get it. The line that separates this from a demo.
Calendar integration	2	$840	Two-way sync with Google or Microsoft: create, move, cancel, and read changes staff made by hand. Includes the timezone handling that quietly ruins half the year.
Reminders and rescheduling	2	$840	Scheduled reminders that respect the Gulf working week, one-tap reschedule and cancel, and the release of a freed slot back into availability immediately.
Staff admin surface	1	$420	What reception uses in Telegram: today's list, block a period, override a booking, and see who cancelled. Built for a phone because that is where reception actually is.
Deployment and handover	1	$420	Calendar authorisation with the right account, monitoring on token expiry, and a walkthrough with the people who answer the phone.
Total	12	$5,040	Fixed on signature. Scope changes are quoted separately, never absorbed silently.

What moves the number

Calendar availability read at display time is stale by the time the user confirms.

A hold is mandatory, not a refinement. Without one, a busy clinic double-books weekly, and the receptionist stops trusting the bot — after which the bot is abandoned regardless of how well the rest of it works.

Google and Microsoft OAuth tokens are revocable by a workspace administrator.

The integration can stop silently after a policy change on your side. Monitoring on token health is what turns that into a twenty-minute fix rather than a week of missed bookings.

The UAE working week runs Monday to Friday with a short Friday, and Ramadan hours differ.

Reminder timing and availability rules need local awareness rather than a generic scheduler. This is the single largest determinant of whether a booking bot actually reduces no-shows.

Staff count multiplies availability logic more than customer count does.

One practitioner with a fixed schedule is straightforward. Six with different services, different hours and shared rooms is a scheduling problem, and it is the main reason two booking bots differ in price.

Microsoft Graph timezone handling changes behaviour across daylight saving boundaries.

Bookings made by clients in Europe or the UK land an hour out for part of the year unless handled explicitly. It passes testing in the Gulf and fails in March, which is the worst possible time to find it.

Taking a deposit at booking converts this into a payment build.

Deposits bring refunds, reconciliation and no-show policy enforcement, adding four to six days. Worth it where no-shows are the actual business problem, and scoped explicitly rather than assumed.

What year one actually costs

Running cost	Year one	Detail
Support retainer	$3,480/yr	Calendar credentials expire, workspace policies change, and clinic hours change with the season. All three are quiet failures in a booking bot.
Managed hosting	$660/yr	Runtime, the booking record and its backups. The history of who booked what matters more here than most clients expect, particularly in healthcare.
Calendar platform licences	billed by the provider	Google Workspace or Microsoft 365 seats on your own contract, which you almost certainly already pay for. The bot does not need its own seat in most configurations.
Deposit processing fees	billed by the provider	Only where deposits are taken, charged per transaction by your gateway. Usually far smaller than the no-show cost they prevent.

Buying the same thing elsewhere

Where you buy it	What the money buys	What you carry
An off-the-shelf booking platform	A monthly subscription, a booking page, reminders and a calendar sync, working today. For a single practitioner with straightforward hours this is the right purchase and a bot adds little.	Customers leave the chat to reach it, the reminder channel is email or SMS with their open rates, and the availability rules are whatever the platform models. Multi-room, multi-service clinics outgrow it.
Your practice management system's own booking module	Already integrated with your records, your billing and your compliance obligations, with nothing new to reconcile. If it exists and works, use it.	Patient-facing interfaces in practice management systems are typically the weakest part of the product, and adoption suffers accordingly. The bot is often bought precisely because that module went unused.
Reception and a phone	Zero technology cost, complete flexibility, and a human who can hear that a patient is anxious. Genuinely better than a bot for complex or sensitive bookings.	Bounded by opening hours and by one person's attention, and every no-show is a call somebody has to remember to make. The bot is worth buying at the point that attention is the constraint.

Questions about the money

Will it work with the calendar we already use?

Google Calendar and Microsoft 365 are both supported directly, and Calendly where scheduling rules already live there. The bot writes into the diary your staff already keep, because a bot with its own separate calendar becomes a second source of truth within a week.

What stops two people booking the same slot?

A short-lived hold taken the moment a slot is chosen, released automatically if the person abandons the flow. It is the difference between a booking bot and a booking demo, and it is why the concurrency line has two days against it.

Can staff still book by phone?

Yes, and they will, which is why the sync is two-way. A booking taken at the desk disappears from the bot's availability, and one moved by dragging it in the calendar updates the customer. Any design that assumes the bot is the only entry point fails in week one.

How much does it reduce no-shows?

We will not quote a figure, because a number we did not measure in your clinic is a fabrication. What we can say is that a one-tap cancel and reschedule turns a silent no-show into a freed slot, and freed slots are the mechanism through which anything improves.

Does it handle multiple branches?

Yes, and it adds roughly a day for location selection, per-branch availability and routing. It is a common requirement in Dubai and is far cheaper handled at the start than added to a single-branch bot afterwards.

Can we take a deposit to confirm?

Yes, and it changes this from a booking build into a booking and payment build — four to six days more for refunds, reconciliation and policy enforcement. Where no-shows are the real problem it usually pays for itself, and it should be a deliberate decision rather than an assumption.

What about Arabic?

A second language adds roughly a day for the conversation and its reminders. The work is right-to-left layout and mixed-direction strings in inline keyboards rather than translation, and it is priced on the multilingual page.