House of Havana
A booking system for a six-branch beauty studio — not a brochure.
A bilingual Arabic and English site where a customer picks a service, a branch and a time, and gets a WhatsApp confirmation. Behind it sits the system the studio actually runs on — customer accounts, an admin side, and automated email.
Visit houseofhavanaeg.com- Client
- House of Havana
- Sector
- Beauty studio, Cairo
- Languages
- Arabic & English
- What we built
- Digital Operations
- Delivery
- About two months
- Status
- Live, launched July 2026
Six branches, and every booking going through a person.
House of Havana runs six branches. What they needed from a website was not a brochure with an address on it — they needed the booking itself to happen on the page. A customer had to be able to see what the studio actually offers, choose the branch that suits them, and hold a time, without anyone on the other end picking up a phone.
It also had to work in both languages. A large part of the audience reads Arabic and a large part reads English, and a booking flow that only half of your customers can follow is a booking flow that loses half of your customers. Arabic meant proper right-to-left layout throughout, not a translated page bolted onto an English one.
And a booking that arrives is only half the job. Someone still has to confirm it, move it when a customer needs a different day, or cancel it — and the customer has to be told each time. Done by hand across six branches, that is a full-time job in itself.
A bilingual site built around a branch-aware booking flow.
We built the whole site in Arabic and English with full RTL, and put a booking flow at the centre of it. The customer chooses a service from the studio's live catalogue, chooses one of the six branches, chooses a time slot, and submits — and the confirmation comes back over WhatsApp, which is where this audience already is.
Everything else on the site exists to get someone into that flow with their questions already answered: services grouped by category so people can find their treatment, an FAQ for the ones who need reassurance before booking, and testimonials for the ones who need proof.
Underneath all of it is a database with two doors into it. Customers get accounts and manage their own bookings; the studio gets an admin side to confirm, reschedule and cancel — with the customer emails going out on their own.
Service, then branch, then time.
Three decisions, in the order a customer actually makes them. Screenshots below are the live site.
-
Choose a service
The catalogue is grouped by category, so a customer scans to their treatment instead of reading a flat list of every service the studio offers.
-
Choose a branch
All six branches in one list. The booking carries the branch with it, so the request lands with the team that will actually take the appointment.
-
Choose a time
Slots across the working day, plus a “flexible on timing” option for customers who would rather the studio suggest one. Then confirmation over WhatsApp.
Two sides of one system.
The booking form is the part customers see. Behind it is a database both sides work from — customers through one door, the studio through the other.
Their bookings, in their own account.
A customer signs in with an email address or a phone number and sees every booking they have made, with its current status. They can act on those bookings themselves, rather than ringing a branch to ask where things stand.
Confirm, reschedule or cancel — and the email sends itself.
The studio works the same bookings from the admin side: confirm, reschedule, cancel. Each status change sends the customer an automatic email, and the same system carries discount announcements and newsletters — so keeping customers informed stops being a job someone has to remember to do.
This is a Digital Operations build — the point where a website stops being a brochure and starts running part of the business.
Everything the studio needed to take a booking without a phone call.
- Bilingual Arabic & English with full RTLBoth languages built as first-class versions of the site, not a translation layer.
- Multi-branch bookingSix branches selectable in the flow, with the booking routed by the branch chosen.
- Service-category filteringTreatments grouped so customers reach the right one quickly.
- WhatsApp confirmationThe booking is confirmed on the channel this audience already uses daily.
- Dynamic service catalogueServices are data, not hard-coded pages — the studio's list can change without a rebuild.
- FAQThe questions that used to be asked on the phone, answered before the booking.
- TestimonialsProof from existing customers, placed where a first-time visitor hesitates.
- Customer accountsSign-in by email or phone, with every booking and its status in one place.
- Admin booking controlConfirm, reschedule and cancel bookings straight from the database.
- Automated emailBooking-status updates, discounts and newsletters, sent without anyone chasing them.
Built mobile-first, because that is where the bookings come from.
The booking flow was designed for a thumb before it was designed for a cursor. Every step of the form — service, date, time, branch — stacks into a single column with touch-sized controls, and the WhatsApp confirmation lands in an app the customer already has open.
The Arabic version gets the same treatment, mirrored end to end rather than reflowed.
Discovery, build, launch — about two months, end to end.
Discovery started with how the studio already runs: which services get asked for, how a booking reaches a branch, what staff end up repeating on the phone all day. From there the whole thing took roughly two months — the bilingual site, the booking flow, customer accounts, the admin side and the automated email, built and reviewed in one continuous pass instead of staged handoffs and sign-off queues. The site went live and started taking bookings straight away.
~100 bookings a day, since launch
Taken through the site's own booking flow, across all six branches.
Our read is that removing the phone-call step — book on the page, confirm on WhatsApp — is what let the studio reach that volume as quickly as it did.
What impressed us most was the usability — the site feels smooth and professional, but the different sections are simple yet extensive, with the right calls-to-action in the right places. That's a big part of why we hit the booking numbers we did, so fast. But beyond the design, it was the process — Webify didn't just build a website, they got involved in how our business actually runs day to day. They understood our goals and our vision and translated that into the site itself. That level of consideration, down to the smallest details, is what made this work.
Need the website to run part of the business?
This was built as Digital Operations — portals, dashboards and the systems behind them. Send a short brief and we'll come back within two working days — a short call to understand the work, then a clear scope, a fixed figure and a delivery date. No obligation, and no pressure to sign anything.