Fusha or dialect? Choosing your register
Modern Standard Arabic is not the safe option and dialect is not automatically better. A decision framework, and the cases where fusha genuinely wins.
The question usually gets asked as if it were a moral one: do we "preserve" fusha or "descend" into dialect? It is in fact purely operational — which register serves this piece of copy, for this audience, in this position?
Should you write social content in fusha or dialect?
It follows the content type, not which one is safer. Use your market's dialect for everyday and community posts, the sender's language for replies, easy modern fusha for announcements that cross markets, and fusha for legal, policy and crisis copy. Decide once per type and write the decision down.
The rule in one line
Dialect for closeness, fusha for authority. If the copy needs to sound like it came from a person, use dialect. If it needs to sound like it came from an institution, use fusha.
Where fusha genuinely wins
Fusha is not a fallback. It is the correct choice in specific places:
- Messages read across several markets at once. A pricing announcement, a service change, a statement.
- Legal and corporate content. Terms, policies, reports.
- Crises. In an apology or a correction, composure is the asset and closeness is a liability.
- When you have nobody to review a dialect. Well-executed fusha beats clumsy dialect, always.
Where fusha loses
- Everyday posts. They read as adverts, and adverts get skipped.
- Replies to comments and DMs. Answering a dialect comment in fusha creates instant distance.
- Entertaining content. Lightness does not survive in fusha.
- Search. People search what they say: «كابشن» far more than «تعليق», «السوشيال ميديا» far more than «وسائل التواصل الاجتماعي».
The third register everyone forgets
Between stiff fusha and local dialect sits easy modern fusha: short sentences, everyday vocabulary, no ornamentation. This is the best option for brands serving more than three markets without a local team — it reads neither formal nor as belonging to one market.
Most people complaining that "fusha is cold" mean ornamental fusha, not this.
A decision framework
- Is the message aimed at one market? If yes, dialect.
- Does it carry a legal or financial commitment? If yes, fusha.
- Do you have anyone to review a dialect? If not, easy modern fusha.
- Is this a reply to a person? If yes, use their dialect.
The same message at three registers
A price change, which is exactly the kind of message where the register decision has consequences:
- Ornamental fusha: «نتشرف بإحاطتكم علماً بتحديث هيكل الأسعار». Nobody talks like this, and it reads as evasion.
- Easy modern fusha: «حدّثنا الأسعار اليوم. إليك ما تغيّر ولماذا». Clear, calm, works in every market.
- Dialect (Saudi): «غيّرنا الأسعار — وترى نوضّح لك ليش». Close, and possibly too close for a message about money.
The second is usually right for this kind of announcement, and it is the register most brands skip entirely because they think the choice is only between the first and the third.
The mistake in both directions
Two failure modes, equally common:
- Dialect where authority was needed. An apology in dialect can read as unserious. A pricing change in dialect can read as evasive. When you are asking to be believed rather than liked, composure is the asset.
- Fusha where closeness was needed. A reply to a customer complaint in ornamental fusha reads as a form letter, which is precisely the wrong signal when someone is already annoyed.
A register table you set once
The point of a framework is stopping the weekly argument. Decide once, per content type:
- Everyday posts → dialect of your primary market
- Replies → the sender's language, always
- Announcements across markets → easy modern fusha
- Legal, policy, crisis → fusha
- Entertaining or community content → dialect
Write it down somewhere your team can see. Most register inconsistency is not disagreement, it is the absence of a decision.
What to test first
- Audit last month's posts and label the register of each. Most brands find they were inconsistent without intending to be.
- Fix replies first. It is the cheapest change and the one customers feel most directly.
- Try easy modern fusha on your next cross-market announcement instead of either extreme.
Where to start
Choose the register once per content type, not per post. A small table settles it: posts in dialect, replies in the speaker's dialect, announcements in fusha, legal in fusha. Then stop reopening the decision every week.
Intilq sets the market per brand and per campaign, with pan-Arab fusha as its own option. The detail is in Arabic social media content, in your dialect.