A bilingual Arabic–English studio, from booking to InstaPay

A typical boutique studio in Cairo, Riyadh or Dubai serves two audiences at once. Some of its customers prefer Arabic; others grew up switching between Arabic and English mid-sentence and book in whichever their phone is set to. Many pay by transfer (InstaPay, a mobile wallet, a bank app) or in cash at the desk, and few want to save a card with a studio.

Much studio software was designed for the opposite: English-only screens, Arabic as an afterthought or not at all, and payments that assume a card on file. Studios fill the gap with WhatsApp: screenshots of transfers in one chat, class changes in another, a front desk translating policies on the fly. This guide is about closing that gap properly — serving two languages and local payments in a way that customers find natural and staff find calm.

Bilingual is not "translated"#

A studio is bilingual when an Arabic-speaking customer never has to switch to English to do anything (book, cancel, pay, read a policy, understand a reminder) and an English-speaking customer never has to switch to Arabic. That is a higher bar than having a translation file.

Write both, do not translate one#

The texts customers actually read deserve to be written in each language, not run through a translator:

• Class descriptions. "Reformer Flow: a 50-minute full-body class for all levels" reads differently in Arabic, and should. Describe what the class is, who it suits and what to bring, in each language.
• Your policies. Booking, cancellation, freezing and refund rules need to be unambiguous in both languages. A policy a customer did not understand is a refund conversation waiting to happen.
• Payment instructions. Write them as steps, not a paragraph: the InstaPay handle, the wallet number, the bank details, and exactly what to write as the reference.
• Announcements and offers. A message that sounds natural in Arabic converts better than a literal translation of an English one.

In Owelz, each of these has its own English and Arabic text: class descriptions, the public studio page, the transfer details customers read before paying, broadcasts, promotion messages, the line that comes with a voucher, and the refund policy customers read before they pay. Instructors write their own public bio in both languages too.

Let each customer choose#

The language belongs to the customer, not the studio. Owelz records a preferred language for each customer, and every automatic message (booking confirmations, the reminder three hours before class, your package is running low, a spot opening on a waiting list, an offer) goes out in that language, in the app and by push, and by email where missing it would cost the customer something. The customers app itself switches between Arabic and English, right to left in Arabic, on iPhone, Android and the web.

Names in both scripts#

At the desk, a customer called "Nour" on Instagram may be «نور» on the transfer screenshot. Owelz keeps a customer's name in Latin and Arabic, and the desk searches by name, phone, email or customer code, so the person in front of you is found, however their name was typed.

Staff work in their language too#

Bilingual matters behind the desk as much as in front of it. The Owelz dashboard runs fully in Arabic or English, and so does the instructor app: instructors switch it to Arabic from their profile, and the alerts they receive follow. Error messages explain what went wrong in the reader's language, and the activity log writes each entry in the language of the person reading it. A front-desk team that thinks in Arabic should not have to work in English.

Local payments, without the screenshot chaos#

A common payment flow in an Egyptian studio looks like this: the customer sends an InstaPay transfer, takes a screenshot, sends it on WhatsApp with their name, and someone at the studio matches it to a package, eventually. It works until the studio has two hundred customers and three admins, and then it becomes a steady source of mistakes.

It is not a niche habit. The Central Bank of Egypt has reported more than 16 million InstaPay users, and Egypt's telecom regulator counted 46.3 million active mobile wallets in a single quarter's report. Transfers are how your customers pay. The job is to make them orderly.

Turn the screenshot into a request#

The fix is to move the transfer out of WhatsApp and into the booking app, attached to the package it pays for:

1. The customer picks a package in the app and reads your transfer details, in their language.
2. They transfer the amount and upload the screenshot as proof, with their reference.
3. Every admin is notified, and the request waits in one queue, with the customer, the package, the amount, the reference and the proof image.
4. You check the proof against your bank or wallet statement and confirm. The sale is recorded, the money appears in the wallet, and the customer holds the package.
5. Or you reject with a reason they read ("The amount received is 500; the package costs 800"), and they can send a new proof.

That is exactly how payment requests work in Owelz. Requests do not expire on their own, confirmed and rejected requests keep who reviewed them, and when a customer is buying at an offer price, the amount is worked out by Owelz, so nobody can type a lower one. One rule is worth repeating: the amount on screen is what the customer typed; the proof image is the evidence. Match it against your statement before you confirm.

One wallet for every way you are paid#

At the desk, customers still pay in cash, by card machine, by InstaPay or from a wallet. Each sale in Owelz records its payment source, and everything lands in one wallet, with a cash box you settle, so at the end of the day "how much came in by InstaPay?" has an answer that does not involve scrolling through a chat.

Prices people can read#

Small things make prices trustworthy in two languages: the studio's currency on every amount, written the way each language reads it, and the same Latin digits customers see in their banking apps. Owelz labels every amount with your studio's currency in the dashboard, the customers app and the instructor app.

Built for the region's calendar#

A bilingual studio also runs on the region's calendar. Ramadan changes the timetable, Eid closes the studio, and national days matter in some countries and not others. Owelz knows the seasons for studios in Egypt, Saudi Arabia and the UAE, suggests seasonal offers only where they apply, and handles studio closures by extending every running package automatically. Reminders and quiet hours follow your studio's own time zone. Our guide to Ramadan, Eid and summer closures covers the details.

WhatsApp, where it belongs#

WhatsApp is not going anywhere, and it should not. It is where a customer asks a quick question and where a personal message wins someone back. What it should not be is your booking system, your payment ledger and your announcement channel all at once.

In Owelz, every customer on a follow-up list has Call, WhatsApp and Email one tap away, and tapping them logs the outreach. Your public studio page keeps your WhatsApp number behind a Show contact click, so it reaches people interested in your studio rather than every scraper on the internet. Bookings, payments and reminders run in the app; conversations stay human.

A checklist for a properly bilingual studio#

• Class descriptions and policies written in both languages, not translated.
• Each customer's preferred language recorded, and every automatic message following it.
• Transfer instructions published in both languages, as steps.
• Transfers arriving as requests with proof, confirmed or rejected with a reason.
• Every desk payment recorded with its source, in one wallet.
• Staff and instructors working in the language they think in.

Owelz was designed in the region for exactly this studio: Arabic and English everywhere, transfers with proof instead of screenshots in chats, and a calendar that knows when Ramadan is. Book a demo below and we will show it to you in the language you prefer.