Choosing a CRM for a team that works in English, Arabic and Persian

Published 3 November 2026 · 7 min read

Short answer: A multilingual CRM is not one that translates everything. It lets each person pick their own interface language, lays out right-to-left and left-to-right text correctly, stores customer data exactly as typed, and finds a name no matter which keyboard it was typed on. Test those four things with your own real data before you buy.

The real problems of a three-language team

Picture a distribution company in Dubai run by a Persian-speaking founder. The sales manager writes reports in English, two account managers talk to Gulf customers in Arabic, and the warehouse team and the founder think and type in Persian. Customers include local traders, overseas suppliers and buyers in Europe. This is common, and many CRMs handle it poorly.

The problems show up in small, daily ways:

• Mixed scripts in names. One company appears as "Al Noor Trading" on its invoice, as "النور للتجارة" on its business card, and as "نور" in a salesperson's notes. Without a rule, the same customer ends up in the CRM three times.
• Right-to-left next to left-to-right. Arabic and Persian run right to left; English, email addresses, product codes and phone numbers run left to right. A single line such as a Persian note that mentions an English model number can display in a scrambled order if the system does not handle direction properly.
• Search that misses. Arabic and Persian share an alphabet, but some letters are different characters on the two keyboards. The Arabic ي and the Persian ی look almost the same, as do ك and ک. A name typed by an Arabic speaker may not be found when a Persian speaker searches for it, and the CRM silently reports "no results".
• People switching languages mid-conversation. A call with a customer may start in Arabic, move to English for technical details and end with an internal note in Persian. The record is naturally mixed, and the system should not fight it.
• Different preferences inside one team. The owner may want the screens in Persian, while a newly hired sales manager in London is far faster in English. Forcing one interface language on everyone slows someone down every single day.
• Customer data in the customer's language. An address in Sharjah, a contact name in Toronto or a company name registered in Persian should be kept exactly as the customer writes it.

What "multilingual" should mean in a CRM

For a team like the one above, it should mean four specific things.

1. Interface language per person

Menus, buttons and messages should follow each user's own choice, not a single company-wide setting. The customer list is shared; the language of the buttons around it is personal.

2. Correct layout in both directions

When the interface is in Arabic or Persian, the whole screen should mirror to right-to-left: menus on the right, text aligned right, tables reading from the right. When it is in English, it should be a normal left-to-right layout.

3. Data stored as typed, never auto-translated

This is the point teams most often get wrong. Translating the interface is helpful. Translating the data is harmful. If a CRM "helpfully" translates a company name or a call note, you lose the exact wording, search stops working and the record no longer reflects what really happened. A good CRM translates its own labels and leaves your data alone.

4. Search that understands letter variants

Search should treat the Arabic ي and the Persian ی as the same letter, and the same for ك and ک. Without that, a three-language team will create duplicate customers simply because nobody could find the existing one.

A checklist for evaluating vendors

Do not rely on a feature list. Run each test below in a trial account with a handful of your own real customer names.

What to test	How to test it	What a good result looks like
Interface language per user	Two colleagues log in at the same time with different language settings.	Each sees their own language; the data is identical.
RTL and LTR layout	Switch between Arabic or Persian and English.	The screen mirrors fully; nothing overlaps or is cut off.
Mixed text in one field	Write a Persian note that includes an English product code and a phone number.	The note reads in the correct order after saving.
Data kept as typed	Save a company name in Arabic, then view it with the interface in English.	The name is shown exactly as typed, not translated or transliterated.
Letter variants in search	Save a name with an Arabic keyboard and search for it with a Persian keyboard.	The record is found.
Untranslated screens	Open every screen your team will use daily in each language.	You know in advance which screens are not yet translated.
Dates and calendars	Enter a follow-up date and view it in each language.	You understand which calendar is used for entry and for display.

The last two rows matter because no product is perfect. Knowing the gaps before you commit is far better than discovering them in week three.

Rollout tips that prevent a mess

A few agreements at the start save months of cleanup later. If you are new to CRM rollouts in general, our plain-English guide to what a CRM is covers the basics.

• Agree on a naming convention for organizations. For example: the official registered name in its original script as the main name, and other spellings kept in the notes or description. Write the rule down and share it.
• Agree on how person names are written. Decide whether a contact's name is entered the way the contact writes it or the way your team says it, and stick to one choice.
• Keep one shared glossary of stage names. If your pipeline stage is called "Quote sent" in English, decide what it is called in Persian and Arabic, and use exactly those terms in meetings and reports. A manager reviewing the pipeline in English and a salesperson working in Persian must mean the same thing by the same stage.
• Search before you create. Make "search first, then add" a team habit.
• Let people write notes in the language they think in. A clear note in Persian is more useful than a confused one in English. Our article on building a sales follow-up process explains how to make every note end with a next action.

How Melal CRM handles this today

Melal CRM is aimed at B2B sales teams whose staff or customers work in Persian as well as English or Arabic. Here is what it does, and what it does not yet do.

• Three interface languages. Each person can switch between Persian, Arabic and English from the top bar. The choice applies to that browser, so colleagues can work in different languages at the same time.
• Left-to-right English. The English interface is laid out left to right.
• Your data is never translated. Customer names, notes and other information you enter stay exactly as they were typed, whichever interface language anyone uses.
• Arabic and Persian letters match in search. In most search boxes, Melal CRM treats the Arabic ي and ك as the Persian ی and ک, so a name typed on an Arabic keyboard can be found from a Persian one.

What to know before you choose it: translation of the screens into English and Arabic is still in progress. Menus, the top bar with its notification bells and parts of the screens are translated; other screens are still in Persian. Date entry currently uses the Persian calendar (the top-bar date shows the Gregorian calendar in English). Voice entry and the in-app AI training assistant work in Persian. In practice, Melal CRM is a good fit today for teams where at least the people doing daily data entry are comfortable with Persian, and where English or Arabic is needed mainly for some colleagues and for customer data.

Beyond languages, the same account covers organizations and contacts, conversation logs with next follow-up dates, deals and pipelines, proforma invoices and inventory. You can see the full list on the features page, and trading businesses in the Gulf may find CRM for trading and distribution companies in the UAE useful.

The simplest way to see whether it fits your team is to try it with your own customer names. Request a demo and the Melal team will set up a trial account for you.

Frequently asked questions

Related: What is a CRM? · Sales follow-up process · CRM for UAE trading companies