Bookings · 4 min read
Can I take bookings in Arabic?
The short answer
Yes, and the part that matters is what happens next. A request records the language it arrived in, so the confirmation or decline you send back goes out in that language. Phone numbers stay in Latin digits on purpose, because that is what people dial from.
On this page
Plenty of businesses here run bilingually without thinking about it. The sign is in Arabic, the menu is in both, and people message in whichever they prefer. Then the website arrives and quietly forces everyone into English.
Booking is where that hurts most, because a booking is not a page view. Someone is handing you their name, their number and a date, and asking you to reply.
What a booking request actually carries
When a visitor asks to book something on a Helm site, the request lands in your dashboard as Pending. It carries their name, their email, their WhatsApp number if they left one, the space or slot they want, their preferred date, and any message they added.
You open it and choose Confirm or Decline. That step is deliberately one-way: once you have answered, the request moves to Confirmed or Declined and shows how you replied, so nobody gets emailed twice by accident and your history stays readable.
The reply is the part people remember
Here is the detail that matters for a bilingual business, and the one most systems get wrong. The request records the language it came in. If someone books in Arabic, the confirmation or decline they receive goes out in Arabic.
That sounds small. It is the difference between a business that happens to have an Arabic page and a business that actually operates in Arabic. Somebody who wrote to you in their own language and got a reply in English has learned something about how you see them.
Those guest emails are optional — you switch them on in Settings. Some businesses would rather reply on WhatsApp, and that is a legitimate choice; the point is that it is a choice rather than a limitation.
Numbers stay in Latin, deliberately
Phone numbers, dates and prices stay in Latin digits in both languages. This is not laziness. It is what people copy, dial and read back over the phone, and switching them to Arabic-Indic numerals is the kind of authentic-looking decision that makes a booking harder to act on.
The same instinct applies across the site. Most Arabic website mistakes are not translation errors at all — they are layout and detail decisions made by someone reading it in the wrong direction.
Where this breaks on other systems
Two failure modes are common. The first is a booking widget from a third party that has no Arabic at all, so your beautiful bilingual site hands the customer off to an English form at the last step.
The second is subtler: the form is translated, but the reply is not. You get the booking, the customer gets an automated English confirmation, and the bilingual experience ends exactly where trust is being decided.
If you are adding Arabic to a site that already exists, the layout work is the real job and the booking flow is worth testing end to end rather than at the form.
What you still have to do yourself
The system carries the language. It does not write your content. Your space names, your descriptions and your policies need to exist in both languages and read naturally in both, and machine translation is obvious to native readers in a way it is not to you.
You also still have to answer. A booking request sitting Pending for two days is a worse experience than no booking system, in any language.
Who answers, and what happens to the ones you do not
Anyone on your team can see the bookings. Confirming, declining, removing a request and changing the settings are for Owners and Editors, which matters more in a family business than it sounds — the person who opens the shop is often not the person who should be committing the calendar.
The list filters to All, Pending, Confirmed, Declined or Unread, and new requests carry a dot until somebody has looked at them. Confirmed bookings are kept as your record. Declined ones, and the ones nobody ever answered, are cleared out over time so the list stays about what is actually coming.
That last detail is worth a moment. A booking system quietly accumulates the requests you ignored, and a list that is nine-tenths regret is a list nobody opens. The clearing is not tidiness, it is what keeps the thing usable in month six.
The module's own documentation exists in Arabic as well, which matters if the person running the dashboard is not the person who built the site.
If you only change one thing
Take the reply seriously. Plenty of businesses here manage bookings without paying commission to a marketplace, and plenty take reservations without a booking platform at all. What separates the ones people come back to is not the form. It is that the answer arrived quickly, and in the language the question was asked in.