Booking & Scheduling Platform for Ora*** Wellness, UAECase Study

Bookings arrived through three channels that did not talk to each other — phone calls into each branch, WhatsApp messages to a shared number, and walk-ins — with a paper diary as the only reconciliation point. Double bookings happened weekly. No-shows were the bigger financial problem: appointments are staff-time-bound, and an empty chair cannot be recovered, but the group had no systematic reminder process beyond a receptionist calling when she had time. Staff scheduling added complexity because therapists have different service qualifications, so a booking is only valid if the assigned staff member can actually perform that service at that branch. Ramadan changes operating hours substantially and staff availability with it, so any scheduling model that assumed fixed weekly hours would break for a month each year. Customer communication had to be on WhatsApp — the group was clear that SMS reminders were ignored and email was not read, which is consistent with how the UAE market behaves. Arabic and English were both required.

We built the platform with React and Node.js on PostgreSQL, modelling staff qualifications and per-branch service availability so the system can only offer a slot that is genuinely bookable — a booking requires an available, qualified staff member at that branch, checked at the point of offer rather than at confirmation. Operating hours are defined as schedules with overrides, so Ramadan hours and public holidays are configured once rather than requiring the model to be fought. Confirmations and reminders go through the WhatsApp Business API using pre-approved templates, sent at intervals the group tuned during the first weeks — a reminder too early is forgotten and too late is useless. Customers can confirm, reschedule or cancel by replying, and a cancellation immediately releases the slot back to availability, which is what turns reminders from a courtesy into a revenue mechanism. Payment integrates with a local gateway supporting deposits on higher-value services, since a small prepayment changes no-show behaviour more than any reminder does. The interface is bilingual Arabic and English with proper RTL. All four branches share one customer record, so a client known at one branch is recognised at another. Reception staff kept a manual override for walk-ins and phone bookings, because a system that cannot accommodate a customer standing at the desk gets worked around rather than used. Related: custom software development and mobile app development.