Most clinics, salons and studios in Dubai still take bookings the same way. Someone calls, or sends a WhatsApp message, and a name goes into a paper diary or a shared spreadsheet. That works until it does not, and the breaking point is predictable: a second stylist, a second treatment room, or the first week where three people all believe the six o'clock slot is theirs.
Here is the short version of what we tell people who ask us to build them a booking system. For most service businesses, an off the shelf product plus deposits plus automated reminders solves the actual problem, and custom development would be money spent on something the market already solved well. The one group that genuinely needs custom work is the group holding patient data, because UAE health rules change where that data can sit and how it has to be handled.
The numbers, up front. A booking system added to an existing website starts from around AED 4,000, the band our published website development cost guide already uses for that scope. A clinic booking system that only sends appointment reminders and holds no clinical records starts from around AED 12,000, which is the patient-communications band in our healthcare app guide. Once clinical notes, consent flows or health information exchange integration are in scope, the anchor moves above that. Custom software beyond that starts from around AED 15,000, per our custom software cost guide. Final pricing depends on scope. We build web and booking systems for UAE businesses from our Dubai and Bengaluru teams [23].
What a booking system actually has to do
A booking system has seven core jobs: resource calendars, durations and buffers, deposits, cancellation windows, automated reminders, packages, and walk ins.
Resource based calendars. The bookable unit is a person or a place: a stylist, a dentist, a trainer, a treatment room. Every mainstream platform is built this way, so multiple staff with different working hours and days off is a baseline feature rather than an upgrade.
Durations and buffers. Each service has a length, and often a gap attached to it. A colour treatment needs twenty minutes of processing with nobody in the chair. Setting this per service is standard.
Deposits and prepayment. SimplyBook.me ships a named deposits feature [13], Fresha supports payment policies including prepayment and stored card details [16], and Setmore takes a percentage deposit at booking with the balance due on the day through a connected payment provider [18]. This is the most commercially important item on the list.
Cancellation windows. A stated window, agreed at the moment of booking rather than explained afterwards. SimplyBook.me ships this as a cancellation policy feature and is explicit that the platform enforces the rule at booking rather than refunding the client for you [14]. That decision stays with you.
Automated reminders. Email, SMS and increasingly WhatsApp. The reminder itself is standard. What varies sharply is how many messages a plan includes before you start paying per message.
Recurring bookings and packages. Weekly tutoring, a block of ten physio sessions, class credits at a studio. If you sell blocks rather than single visits, the system has to book against a balance.
Walk ins. A walk in has to occupy the same calendar as a pre booked slot or you will double book on your busiest day. This is the most common gap in cheap website widgets, which assume every customer books in advance.
Salon, studio, tutor, home services: what changes by vertical
Those seven are constant. What differs is which carry the weight.
- Salons, barbers and spas. Deposits and no shows are the whole commercial argument, and retail sales sit alongside services, which is why salon focused platforms bundle a point of sale.
- Fitness studios. Classes are many to one, so you need capacity limits, waitlists that promote automatically when someone drops out, and credit packs rather than single payments.
- Tutoring centres. Recurring weekly slots, package credits, and a split between the parent who pays and the student who attends. Who receives the reminder is a real design question.
- Home services. Travel time between jobs and a service radius. Most salon first tools model this poorly, so test it first.
- Clinics, dental and aesthetic. All of the above, plus patient records, consent capture and insurance details at booking. That gets its own section.
How deposits and reminders reduce no shows
Three settings reduce no shows: a deposit charged at booking, a cancellation window the client accepts, and two automated reminders. Nobody can tell you your no show rate, and be suspicious of anyone who tries. The percentages that circulate come from two places: booking software vendors selling subscriptions, and international clinical studies that are not about UAE service businesses. Neither describes your reception desk.
So measure it. For one month, count booked slots, count the ones nobody attended, and multiply by what that time is worth at your prices. That is your business case, and the only one worth putting in front of an owner.
The mechanism is not in question. An empty slot cannot be resold at short notice, so a no show costs you the whole slot rather than a margin on it. A deposit moves the client from having nothing at stake to having something at stake. A reminder removes the most common innocent reason for missing an appointment, which is forgetting.
Three settings do most of the work:
- A deposit, as a percentage of the service price or a flat amount, charged when the booking is made.
- A cancellation window stated at the booking step and acknowledged by the client, not mentioned later.
- Two reminders. One a day or two ahead, one on the morning of the appointment.
On payments, most booking platforms either connect to a provider you already use or bundle their own processing, and bundling usually costs more. Fresha publishes an in platform rate of 4.90 percent plus AED 0.75 per transaction [15], above typical standalone UAE gateway rates. Our UAE payment gateway comparison has the full breakdown.
Automatically charging a stored card after a no show is a booking platform feature rather than something a gateway offers. Ask about it specifically, and make sure the client agreed to it in writing at the booking step. A charge the customer did not knowingly accept becomes a dispute, and disputes cost more than the no show did.
WhatsApp and SMS appointment reminders: the UAE rules
A reminder for an appointment the client booked themselves is a utility message under Meta's rules rather than marketing, provided it carries no promotional content.
Meta defines three template categories for messages sent outside the twenty four hour customer service window. Utility templates follow up on a user action or request and carry no promotional intent. Marketing covers anything promotional or persuasive. Authentication is restricted to one time passcodes [9]. An appointment reminder for a booking the client already made is the textbook utility example.
The trap is mixing. Add an offer to a reminder and Meta reclassifies the whole template as marketing, which changes both the approval bar and the cost. Send the reminder clean and send offers separately.
Templates need approval before use. Meta documentation states that review can take up to twenty four hours, that a rejected template cannot be used until fixed and resubmitted, and that a template's status can change later based on usage and quality feedback [10]. Build your reminder templates early, not the week you launch.
On cost, one recent change matters. Meta deprecated conversation based pricing on 1 July 2025 and moved to per message pricing for template messages, charged by category and recipient country [11]. Utility messages sent as a reply inside an already open service window are treated differently from those opening a new conversation. We are deliberately not quoting a rate, because these change: pull current figures from Meta's pricing documentation or WhatsApp Manager when you compare vendors [12]. Our own WhatsApp Business API guide covers providers and setup,.
One practical note. The free WhatsApp Business app suits a single operator replying by hand, but it does not connect to a booking calendar. Automated reminders need the paid WhatsApp Business Platform.
SMS and the TDRA rules
TDRA regulatory policy on unsolicited electronic communications is the document to know. Three things in it matter here.
First, timing. Marketing electronic communications must not be sent to mobile customers between nine at night and seven in the morning, leaving a seven in the morning to nine at night window [7].
Second, consent. Opt in is the default rule for marketing, that consent has to be recorded and retained, and every marketing message needs a free and effective way to unsubscribe [7]. The obligations sit on the licensed operators and flow down into their contracts with the businesses sending through them, so your aggregator will hold you to them.
Third, the line between a reminder and a marketing message. TDRA defines marketing in terms of offering or advertising goods, services or business opportunities. A factual reminder about a booking the client made is not doing that. The policy does not name appointment reminders as an explicit carve out, so the safeguard is content discipline: who, what, when, where, and how to cancel. Consent is what separates the two, so keep two records, one for appointment contact and one for marketing opt in. Check TDRA for current guidance before you launch a campaign [8].
We are not printing a fine figure for either regime, because none appears in the primary policy text.
Clinic booking systems in the UAE: where custom is usually right
A clinic booking system holding patient data must keep that data inside the UAE by default under DHA policy, which is where the buy advice flips.
If you are licensed by a UAE health regulator and your system holds patient data, off the shelf stops being automatically correct. The Dubai Health Authority publishes a Health Data Protection and Confidentiality Policy stating that protected health information should not be transferred to a country or territory outside the UAE, except for transfers falling within the exemptions in the UAE ICT health law [1]. Those exemptions are named and narrow, and sit in Ministerial Decree No. 51 of 2021 [2], which alongside Federal Law No. 2 of 2019 and Cabinet Decision No. 32 of 2020 is listed on DHA's licensing and regulations page [3].
Read plainly: for a facility under DHA jurisdiction, patient data stays in the UAE by default. That rules out a number of otherwise excellent international booking platforms, because you cannot choose their hosting region.
The same policy sets a consent standard. Patients must consent before their health information is processed, consent to share records through the NABIDH health information exchange must be clear, simple, unambiguous and easy to understand with an opt out available, and non health uses of patient information need separate written consent [1]. A salon style booking form does not meet that bar.
Two things we will not tell you. We are not stating a records retention period, because the DHA policy points to the underlying law rather than restating a figure and we could not verify a period from primary legal text. And we are not quoting a penalty amount, because no primary DHA, DoH or MOHAP document we read states one. Ask your regulator for both.
There is a scope question worth asking before you spend anything. A widget capturing a name, a phone number and a time slot for a purely cosmetic service is a different risk case from a platform storing clinical notes or diagnostic data. The second sits inside protected health information territory, alongside NABIDH in Dubai, which DHA reports connects more than 1,500 providers and holds more than 9.5 million electronic medical records [4], and Malaffi in Abu Dhabi, which DoH describes as connecting more than 2,700 facilities [5]. Which bucket you are in is a question for your regulator, not a sales team. Personal data outside the health regime sits under the UAE Personal Data Protection Law [6], covered in our PDPL compliance guide.
If your booking system will hold clinical records, the cost anchor moves. A reminders-only clinic app starts from around AED 12,000 in our healthcare app development guide, and anything holding notes, consent flows or health information exchange integration sits in that guide's higher bands. Final pricing depends on scope.
What an online appointment system costs off the shelf
Off the shelf booking software runs from free to a few hundred dirhams a month, per published vendor pricing pages. Verify current figures before deciding.
| Vendor | From | Notes |
|---|---|---|
| SimplyBook.me | Free tier, paid from around 11.90 euros a month billed yearly [13] | Free tier: one provider, fifty bookings a month |
| Zoho Bookings | Free for one staff member, paid from around 6 US dollars a month [20] | Payments on higher tiers |
| Vagaro | From around 23.99 US dollars a month for one calendar [17] | Extra calendars charged separately |
| Fresha | Independent plan from around AED 149.95 a month [15] | Processing 4.90 percent plus AED 0.75 per transaction |
| Booksy | From around 29.99 US dollars a month [19] | Plus a fee per extra team member |
| Calendly | Free tier, paid from around 10 US dollars per seat a month billed yearly [21] | Built for meetings, not clinics |
| Zenoti | No public price list [22] | Positioned for multi site chains |
The pattern is the same everywhere. The calendar itself is cheap or free. Paid tiers exist to unlock reminder volume, deposits, multi staff and multi location, and API access. That is the real shape of the decision, not which booking page looks nicest.
When a custom build is actually the right call
Four situations genuinely justify building.
Patient data with clinical requirements. Hosting location and consent handling are design decisions, not settings.
A booking flow the platforms cannot express. Multi resource bookings where one visit consumes a clinician, a room and a machine at once. Sequenced appointments across departments. Zone based dispatch. If you keep hearing that a workaround is possible, that is a warning.
Booking that has to live inside an existing system. Sometimes the answer is not a new booking product but a connection between the one you have and your CRM, EMR or point of sale. A standard integration between two systems with published APIs starts from around AED 1,500, and a complex one from around AED 4,000, per our systems and API integration guide. Check your platform exposes an API on the plan you are buying.
Brand and language control. A booking flow that has to sit inside your own site, in Arabic and English with a proper right to left layout, is a website build question. Our small business website guide covers that end.
Outside those four, buying is usually better, and we will say so.
Real client stories
These are anonymised situations from booking and web work we have done.
The clinic group that did not need us to build. A multi branch aesthetic business asked for a custom booking platform. In discovery, their services turned out to be entirely cosmetic, they stored no clinical notes, and their real problems were double bookings between branches and reminders sent by hand. We recommended an off the shelf platform on a multi location plan and spent our time on configuration and deposit policy instead. The build would have solved nothing the product did not.
The dental practice where hosting was the whole project. A practice had shortlisted an international booking product and asked us to integrate it with their records. The blocker was not integration. It was where patient data would sit. We stopped and pointed them to their regulator to confirm their classification first. That conversation was cheaper before the subscription than after it.
The studio that fixed no shows with two settings. A fitness studio was losing peak slots to people who booked and did not attend. No new software was involved. We turned on a deposit for peak classes, wrote a cancellation window into the booking step, and set up a waitlist that promoted automatically when someone dropped. They tracked their own numbers before and after, which is the only comparison that meant anything.
How SKIMBOX approaches booking systems
We start by asking what breaks today, not what to build. If an off the shelf product plus deposits and reminders solves it, we will say so and help you configure it properly, because a well set up subscription beats a badly scoped build every time. Where a build is right, we scope the smallest useful first version, connect it to the systems you already run, and raise data residency, consent and language decisions at discovery rather than after the code is written. For anything touching patient data, we ask you to confirm your position with your regulator before we design around it.
A booking system added to an existing website starts from around AED 4,000. A clinic system that only sends reminders and holds no clinical records starts from around AED 12,000, with records and consent flows priced above that. Custom software beyond that starts from around AED 15,000. Final pricing depends on scope.
See our web development services and app development services, or contact us to talk through what your calendar actually needs.
References
[1] Dubai Health Authority - Health Data Protection and Confidentiality Policy. dha.gov.ae
[2] Ministry of Health and Prevention, UAE - Ministerial Decree No. 51 of 2021 on cases in which health data and information may be stored or transferred outside the country. mohap.gov.ae
[3] Dubai Health Authority - Licensing, Regulations and Laws. dha.gov.ae/en/licensing-regulations-laws
[4] Dubai Health Authority - NABIDH newsroom coverage. dha.gov.ae/en/media/news/932
[5] Department of Health, Abu Dhabi - Malaffi. doh.gov.ae/en/featured/malaffi
[6] U.AE Official UAE Government Portal - Data protection laws, Federal Decree-Law No. 45 of 2021. u.ae/en/about-the-uae/digital-uae/data/data-protection-laws
[7] TDRA - Regulatory Policy, Unsolicited Electronic Communications. tdra.gov.ae
[8] TDRA - Telecommunications and Digital Government Regulatory Authority. tdra.gov.ae
[9] Meta for Developers - WhatsApp template categorization. developers.facebook.com
[10] Meta for Developers - WhatsApp template fundamentals. developers.facebook.com
[11] Meta for Developers - Conversation-based pricing, deprecated. developers.facebook.com
[12] Meta for Developers - WhatsApp pricing updates. developers.facebook.com/docs/whatsapp/pricing/updates-to-pricing/
[13] SimplyBook.me - Official pricing. simplybook.me/en/pricing
[14] SimplyBook.me - Cancellation Policy custom feature. help.simplybook.me
[15] Fresha - Official pricing. fresha.com/pricing
[16] Fresha - Set up payment policies. fresha.com/help-center
[17] Vagaro - Pro pricing. vagaro.com/pro
[18] Setmore - Take payments from the booking page. support.setmore.com
[19] Booksy - Biz pricing. biz.booksy.com/pricing
[20] Zoho Bookings - Official pricing. zoho.com/bookings/pricing.html
[21] Calendly - Official pricing. calendly.com/pricing
[22] Zenoti - Pricing page. zenoti.com/pricing-zenoti
[23] SKIMBOX - Internal experience building web and booking systems for UAE businesses, 2026. skimbox.co



