Right-to-Left and Arabic Support in Chatbots

When you do not need to think about RTL yet

Right-to-left work is a real task, and there is no point doing it before it earns its place. Most teams arrive here from one of a few positions, and the honest advice changes at each.

Your customers read in English

If people write to you in English and you are not offering Arabic support yet, none of this applies. Do not switch a widget to a right-to-left layout that nobody will read that way. It only makes your English widget look off. Come back when Arabic is actually on the plan.

You are still deciding whether to answer in Arabic

Layout belongs to the launch, not the research. If you have not yet decided to answer in Arabic at all, settle that first. The Arabic chatbot guide covers whether it is worth doing and what it takes. The layout is the second decision, and it only matters once the first one is a yes.

It is a static page, not a chat widget

A right-to-left landing page is a web design job, handled once in your site's CSS. This checklist is about the chat widget specifically. The widget is often a separate component with its own settings, and it has its own ways of getting RTL wrong even when the page around it is perfectly fine.

But if you are about to put Arabic in front of real customers, the rest of this is the checklist to run before you do.

What actually breaks when Arabic goes on

These are the parts that look broken on day one if nobody checked them. Each one is a thing to verify, with a plain description of what it is and why it matters here.

The whole widget flips, not just the message text

A right-to-left layout means the entire widget mirrors, so the avatar, the header, the timestamps, the input field and the quick prompts all move to the side an Arabic reader starts from, not only the reply text inside a bubble.

This is the distinction that catches everyone. Many tools will happily render Arabic characters correctly inside a message bubble while the frame around that bubble stays left-to-right. The send button stays bottom-right where an English thumb reaches. The close button, the scroll, the way messages line up: all still arranged for a reader who starts on the left.

So it is worth saying clearly. Right-to-left is a layout setting. The language the bot replies in is a different setting. A bot can answer in flawless Arabic inside a widget that is still laid out for English, and it often does, because the two switches are separate and only one of them got flipped.

Mixed-direction content that does not scramble

Mixed-direction (bidirectional) content is an Arabic sentence that also contains left-to-right pieces, like an English brand name, a price, a phone number or a URL, and each piece has to stay readable.

Arabic runs right-to-left. Numbers and Latin text run left-to-right. So a single sentence often carries both directions at once, and this is the single most common thing that looks broken in a UAE widget. Picture an Arabic reply that quotes a price as AED 1,250, points to a phone number starting +971, and links to yourstore.ae/returns. Done wrong, the digits reorder, the price flips, or the URL splits apart in the middle of the line.

You cannot catch this by typing a one-word greeting. You catch it with test sentences that carry all of it at once: a brand, an AED price, a +971 number and a link, sitting inside real Arabic. That is the content your customers actually send.

A font that is actually built for Arabic

Legibility means the widget renders Arabic in a typeface designed for the script, at a size and line height that keep it readable, rather than a Latin font falling back to whatever the device happens to have.

Arabic letters join up and change shape depending on where they sit in a word, and the dots and marks above and below need vertical room. A font chosen for English will fall back to a system Arabic face that may be too thin, too tight, or simply different from one phone to the next. Line height that looks comfortable for Latin text can crowd Arabic badly. Pick a font that supports Arabic properly and look at it on a real device, not only your laptop.

Dates and numbers in the form your customer reads

Formatting means dates, times, currency and digits appear the way a UAE reader reads them, which is a choice you make rather than something that happens automatically when the text turns Arabic.

Some Arabic contexts use Eastern Arabic numerals (the ٣٤٩٩ form). Most UAE commerce uses Western digits (3,499). Prices might read AED 3,499 or 3,499 درهم, and dates might run day-month-year. None of that is decided for you when the bot starts replying in Arabic. Pick one convention, apply it everywhere, and make sure VAT-inclusive prices are still labelled clearly once the layout has flipped.

Buttons and quick prompts on the correct side

Alignment means the interactive parts, the quick-prompt chips, the buttons, the input field and the send icon, sit where a right-to-left user reaches for them, mirrored from the English layout.

Quick-prompt chips that hug the left edge. A send arrow still pointing left-to-right. A cursor that starts on the wrong side of the box. Each is small on its own, and together they tell an Arabic reader the widget was bolted together in a hurry. When the layout mirrors properly, the send control moves across, the chips flow in from the right, and the arrow icon flips to match.

Three ways chatbots handle right-to-left

Tools sit in one of three places on this, and the gap between them is exactly what you are checking for before launch.

1. No right-to-left at all: Arabic poured into an English widget

The widget only knows one direction. Arabic text goes into the bubbles and the characters render, but the frame stays left-to-right and nothing mirrors. It fits almost nowhere for a real Arabic audience, maybe a single Arabic sentence on an otherwise English site. It fails the moment a customer opens it, because the controls are on the wrong side and the mixed content has nowhere sensible to go.

2. Direction on the text, not the layout

The message text flows correctly (often through a browser setting that reads direction automatically), so the words inside each bubble read the right way. Better than nothing, and fine if your audience is mostly English with the occasional Arabic message. It fails as a real Arabic experience, because the quick prompts, the buttons, the avatar and the input all stay on the English side. The reply reads correctly inside a widget that clearly does not.

3. A real RTL mode for the whole widget

One setting mirrors the entire component: layout, controls, alignment and text together. This is what a serious Arabic launch needs. It rarely fails outright, but two honest catches remain. You still have to turn it on, because it is a deliberate toggle and not the default. And you still have to test mixed content, fonts and formatting, because a mirrored frame does not by itself guarantee that a price or a URL behaves. If you want the underlying ideas from scratch, Arabic chatbots for UAE businesses and bilingual customer support both go deeper.

The pre-launch checklist

Run this before Arabic goes in front of a customer. Group by group, on a real device, with real content. It is not a one-time toggle you tick and forget.

Layout

• The whole widget mirrors, not just the reply text: avatar, header, close button and scroll all on the correct side.
• The send button and input field sit where a right-to-left reader reaches, and the send arrow points the right way.
• Message bubbles align from the right, and the customer's messages and the bot's sit on the sides you intended.
• The widget still mirrors correctly on a phone, not only on a wide desktop screen.

Mixed-direction content

• An Arabic sentence that contains an English brand name keeps the brand readable and in place.
• A price such as AED 1,250 or 1,250 درهم reads in the right order, with the digits not reversed.
• A UAE phone number starting +971 stays intact and left-to-right inside the Arabic line.
• A URL such as yourstore.ae/returns does not break apart or reorder in the middle of a sentence.
• Punctuation (the Arabic comma, the question mark, brackets) sits on the correct side of the phrase.

Typography and legibility

• Arabic renders in a font built for the script, not a Latin font falling back to a system default.
• Line height and spacing leave the dots and marks room, so the text is not cramped.
• The same font renders consistently on iPhone, on Android and on desktop, not only on your machine.

Dates, numbers and formatting

• You have decided on Western digits (3,499) or Eastern (٣٤٩٩) and applied one choice everywhere.
• Currency shows the way your customers read it, and VAT-inclusive prices are still labelled clearly.
• Dates and times follow one convention across every reply.

Buttons, prompts and controls

• Quick-prompt chips flow in from the right and wrap correctly when the text is long.
• Buttons and links are aligned to the right-to-left layout, not left-anchored out of habit.
• The welcome message, any proactive message and any menu read right-to-left too.

None of this proves itself from a screenshot. The next section is how to test it so the problems actually surface before your customers find them.

How to test it, not with a single hello

Most broken Arabic widgets passed a test. The test was one person typing a greeting on a laptop. Here is what a real one looks like.

Have you sent real Arabic sentences, not one word?

A single مرحبا tells you almost nothing. Send the questions your customers actually ask, the ones that carry a price, a brand name, a phone number and a link inside a full Arabic sentence. Mixed-direction problems only appear when the sentence is mixed, so a greeting sails through while the widget is quietly broken.

Did someone who reads Arabic look at it?

You can spot a flipped button. You cannot always spot Arabic that reads awkwardly, or a font that looks wrong to a native eye, or a line that a reader trips over. Get someone who reads Arabic every day to open the widget and tell you what feels off, before a customer does it for you.

Did you test on a phone, the kind your customers use?

Most UAE support happens on mobile. A layout that mirrors cleanly on a laptop can crowd, clip or misalign on a phone, and iOS and Android do not always behave the same way. Open it on both, on a real handset, not just a resized browser window.

Did you switch on the RTL layout, or only the Arabic replies?

These are two different settings, and this is the mistake behind most half-flipped launches. The bot can answer in Arabic while the widget still sits left-to-right, because turning on Arabic does not flip the layout for you. Confirm both are on, on purpose.

Did you walk the whole journey, not just the first bubble?

The welcome message, the quick prompts, a handover to a person, an error state, an empty search. Each of these can quietly fall back to left-to-right if only the message text was handled. Click through the entire path a customer takes, in Arabic, and watch for the moment it reverts.

The landscape: how a few tools handle it

A short, fair pass over tools UAE teams tend to weigh, including ours. This is lighter than the checklist on purpose, because the checklist is the part that decides your launch. Whatever you pick, test the live widget rather than trusting a feature line in the docs.

Zendesk

A mature helpdesk with Arabic support and a large regional footprint. Best if you already run it for ticketing and want the bot to match. Where it struggles: check how completely the live web widget mirrors and how it handles your own mixed-content test strings, because right-to-left polish is not its headline, and the suite is heavy for a small shop.

Intercom

A polished messenger with strong AI answering. Best for well-funded software teams that want the slickest experience. Where it struggles: verify the whole-widget RTL behaviour on your own Arabic sentences with prices and links, and note that premium pricing is a lot for a small UAE retailer.

Crisp

A lighter, affordable live-chat and bot widget popular with SMBs. Best for a small team that wants something simple. Where it struggles: confirm the depth of its right-to-left layout and its Arabic font handling before you assume Arabic looks right, because it is a general tool rather than an Arabic-first one.

Verloop.io and Yellow.ai

Regional and enterprise conversational platforms with real Arabic presence, and in Yellow.ai's case Arabic at scale across many channels. Best if you are large, multi-channel, or WhatsApp-heavy. Where it struggles: both are more platform than a small business needs if all you want is a website answer box that reads correctly in Arabic.

matram.ai

Our tool. Point it at your website, sitemap, PDFs or a connected Notion or Drive, and it answers on your site or in Facebook Messenger in 95+ languages including Arabic, replying in the language the customer wrote in and linking to the page each answer came from. The widget supports a right-to-left layout. Best for a UAE team adding Arabic website support from its own content without a heavy rollout. One honest thing: turning on RTL is a deliberate step in the widget settings, not something that happens automatically when the bot starts replying in Arabic, so you still switch it on and still run the checklist above. And if your customers live entirely on WhatsApp, that is on our roadmap rather than live, so a messaging-native platform will fit better today.

Where to start, by situation

A rough map from where you are to where to begin. Scale here is loosely how much Arabic and mixed content your widget will actually carry.

To weigh the volume behind any of this before you commit, the chatbot ROI calculator works from your own message counts rather than a vendor's claim.

What getting this wrong costs

The setup is an afternoon. The cost of skipping the checklist shows up somewhere the invoice never mentions.

Start with the first impression, because in Arabic you only get one. A customer in Deira opens your widget, sees the send button on the wrong side and a price that reads backwards, and draws the obvious conclusion: this business does not really speak to me. It does not matter that the bot's Arabic underneath was perfect. She read the layout before she read a word, and she closed the tab. You do not get a second launch to that customer.

Then there is the cost that hides. A widget that looks broken in Arabic teaches your Arabic-speaking customers to switch to English, or to give up and message someone else. So your dashboard fills with English conversations and you quietly decide Arabic demand was low. It was not low. It was badly served, and the number that was meant to tell you filed the failure as an absence.

So before you flip the switch, ask the harder question. Not whether the bot speaks Arabic, but this: if an Arabic reader opened this widget on their phone right now, would it feel built for them, or translated at them?

Frequently asked questions