Which Arabic should your content use: Modern Standard Arabic or dialect?

The common shorthand is that Modern Standard Arabic is formal and dialect is friendly. That description is a starting point at best, and too crude to decide with on its own. Standard Arabic can be warm, direct and modern when it is written well, and dialect can be stiff, awkward or condescending when it is applied to the wrong message.

The more useful question is what the communication has to do. A recruitment notice, a regulator-facing statement, a regional brand line and a customer service reply are different jobs, and they do not all fail in the same way when the variety is wrong.

This is a Communication decision before it is an Arabic one. Purpose sets what the text is for, Audience sets who is actually reading or listening, and Context sets where it appears and what surrounds it. Only once those are settled does Voice determine how the organisation should sound while doing it.

Treating variety as a Voice question alone is one of the more common causes of inconsistent Arabic. An organisation ends up choosing a register because a designer, an agency or a platform preferred it, rather than because the purpose and audience required it.

Each factor can move the decision on its own. When they conflict, reach and risk usually pull towards standard Arabic, while audience proximity and channel intimacy pull towards dialect.

• Purpose: informing, positioning, persuading, instructing or reassuring
• Audience: a defined national audience or a mixed regional readership
• Context: what surrounds the text and what the reader expects to find there
• Channel: a published document, an interface, a feed, a call or a chat window
• Reach: one market or several markets reading the same wording
• Risk: what happens if the wording is quoted, disputed or misread
• Voice: whether the organisation is speaking as an institution or as a person

A message with wide reach and high risk rarely belongs in dialect. A message with a narrow audience and a conversational channel rarely benefits from heavy standard Arabic.

These are working rules rather than absolutes. Each one can be overridden, but the override should be a deliberate decision that is recorded, not an accident of who wrote the copy.

• Corporate website: standard Arabic throughout, written in a modern and readable register, because the site is read across markets and is the reference version of the organisation's language
• Press releases and statements: standard Arabic as the default, because the text is usually written to be quoted, republished and archived, and any dialect element should be a deliberate exception
• Executive thought leadership: standard Arabic with a personal register, allowing sentence rhythm and expression to carry the individual's voice rather than switching variety
• Regional social campaigns: often standard Arabic written for speech rather than for documents, so one line can run across several markets, though a campaign built market by market may reasonably use dialect in each
• Market-specific consumer campaigns: dialect where the idea depends on how people in that market actually speak, and where the campaign is genuinely built for that market rather than exported to it
• Customer service, IVR and chat: dialect or a lightly conversational standard Arabic often suits the human-sounding parts, while terms, policies, amounts and anything the customer may rely on later are usually clearer in standard Arabic

The general tendency is clear enough to work with. The closer the communication is to a record, the stronger the case for standard Arabic. The closer it is to a conversation with a specific market, the more dialect earns its place.

Using different registers in different channels is not inconsistency. An organisation becomes inconsistent when nobody decides which channel uses which register, or when the same term appears in three forms because three teams chose separately.

A governed voice system keeps the variation intentional. It sets the default variety for each channel, names the exceptions, fixes terminology, titles and brand language in standard Arabic so they do not shift when a dialect campaign is produced, and states who approves a departure from the default.

With that in place, a customer can move from a dialect chat reply to a standard Arabic policy page and still recognise the same organisation. Without it, the same customer meets what feels like two different companies.

When a decision is unclear, the fastest route is to test the message against a small number of conditions.

• If the text may be quoted verbatim or held to later, then standard Arabic unless there is a specific reason not to
• If one wording will run in more than one market, then standard Arabic written for the ear
• If the message depends on a local expression, joke or cultural reference, then dialect is usually the better fit, and the result should be treated as a market-specific asset
• If the reader is being asked to act on figures, terms or commitments, then standard Arabic for that part is usually safer, even inside a dialect conversation
• If a person is speaking as themselves and the channel is conversational, then dialect or a lightly conversational standard Arabic
• If the choice is being made for visual or stylistic reasons only, then it has not been decided yet

Read the Arabic aloud as the intended reader, in the place the text will appear, then ask two questions. Would this person say it this way, and would the organisation be comfortable seeing this exact wording repeated somewhere it cannot control?

If the answer to the first is no, the register is probably too distant. If the answer to the second is no, the variety may be too local for the risk involved. When both answers are yes, the choice is defensible, and it is worth writing into the voice system so the next team does not have to decide it again.