Bilingual CRM setup: running Arabic and English in one HubSpot portal

Gulf businesses rarely serve one language. The wrong answer is two portals. The right answer is one portal with language as a first-class property.

Make language a governed property

Add a single-select preferred language property on the contact, set it at capture (form field, portal source or inference) and never let it be free text. Every downstream decision — template, owner, sequence, survey — reads this one field.

Localise templates, not just words

Arabic email and page templates need right-to-left layout, correct typography and mirrored components, not a translated English template. Build a parallel template set and keep the structure identical so reporting stays comparable.

Route by language and territory

Assign owners with a rule that considers language first, then territory or product. A fast reply in the wrong language is still a lost lead. Set separate SLA targets per language if your Arabic-speaking coverage is thinner.

Keep one data model, two content layers

Pipelines, deal stages, lifecycle stages and properties stay identical across languages. Only content varies. This is what lets leadership compare Arabic and English funnels in the same dashboard.

Handle names and addresses properly

Store the original script alongside a transliterated version when your team needs both. Normalise country, city and emirate as select fields so segmentation survives spelling variants.

Report language as a dimension

Break down conversion, cycle time and pipeline by language. In most Gulf portfolios the gap between the two funnels is significant, and it is the fastest signal about where enablement or content investment is missing.

Test what customers actually receive

Render every Arabic template on mobile mail clients before launch. Broken RTL rendering is the most common and most damaging localisation defect — it reads as carelessness to exactly the audience you are trying to win.