When a customer writes a review in Najdi Arabic — informal contractions, خشيت and وش و يبغى scattered through their complaint — and your business replies in a stiff formal MSA register borrowed from a government ministry, you have not responded. You have posted a form letter. The reviewer notices. So does every local customer who reads the exchange looking for a reason to trust you.
Dialect routing is the practice of matching the linguistic register of your reply to the dialect markers in the reviewer's text. It is not about mimicking slang or performing a regional identity you do not have. It is about signalling that the person reading the review is local, present, and speaking with genuine familiarity rather than through a filter of polished corporate distance. In Arabic specifically, where dialect differences between Najdi, Hijazi, Khaleeji, and Egyptian carry deep identity weight, this signal compounds trust in ways that no amount of polished MSA prose can replicate.
This playbook covers the entire workflow: how to detect dialect cues, how to route each review to the right reply, how to build a team structure that sustains this at scale, the failure modes you will encounter, and how to measure whether any of this is actually moving your numbers.
For the underlying principles of tone and apology structure in Arabic review replies, see the guide on apology tone in Arabic review replies. For the search-ranking context that makes reply quality matter beyond customer satisfaction, see local pack ranking for Arabic search.
Dialect-cue detection: reading the signals in a review
Detecting dialect from written Arabic review text is a pattern-recognition task. Reviewers do not write in academically pure dialects; they write the way they talk, which means vocabulary, morphology, and sentence rhythm all carry diagnostic information. You do not need a linguistics degree to use these patterns operationally. You need a short checklist.
Najdi cues are the most distinctive because Najdi Arabic retains several features absent from other Gulf dialects. The interrogative particle وش (what / what is) is a strong Najdi marker — you will rarely see it in Hijazi or Khaleeji text. يبغى (he wants) and أبغى (I want) rather than the Hijazi يريد or the Egyptian عايز mark Najdi strongly. Negation with ما plus verb (ما عجبني, ما كان زين) rather than مش or مو is common across Najdi. Geographic name patterns also help: reviewers mentioning Riyadh, Qassim, Ha'il, or Buraidah in passing are almost certainly Najdi speakers. Tribal references and certain family-name patterns reinforce this.
Hijazi cues centre on Western Saudi Arabia — Jeddah, Mecca, Medina. The pronoun انا is often dropped where other dialects retain it. يكسف (it is embarrassing / unfortunate) is a characteristically Hijazi mild negative expression; you will rarely see it in Najdi or Khaleeji writing. The particle بعدين (after that, then) is common. Hijazi Arabic is phonologically closer to Egyptian than Najdi, which means reviewers from Jeddah sometimes use Egyptian loanwords absorbed through decades of media exposure, creating a Hijazi-Egyptian blend.
Khaleeji cues span Kuwait, Bahrain, Qatar, and the UAE. The particle چذب / كذب used as an exclamation of disbelief, the verb يدري (to know), شلون (how, equivalent to كيف), and the question form وين (where) are Khaleeji markers. Emirati reviewers often include English code-switches mid-sentence. Kuwaiti text retains the q-phoneme قاف where many dialects substitute a glottal stop. Qatari reviews often carry the characteristic تشديد (gemination) patterns and the honorific يبارك.
Egyptian cues are highly recognisable because Egyptian Arabic is the prestige media dialect across the Arab world and its markers are widely known. إيوة (yes), عايز / عايزة (want), مش (not), زي (like / as), إيه (what), and بتاع (thing / belonging to) are core Egyptian markers. Reviews from Egyptian residents in the GCC — who form large expat communities in all five Gulf countries — will often include these markers alongside Gulf context (mall names, Saudi street names, UAE terminology).
MSA and formal markers appear in reviews written by people who default to standard Arabic when writing, often older reviewers, professionals, or people who learned written Arabic formally rather than through colloquial media. Markers include full إعراب diacritics (rare in colloquial writing), formal transitional phrases such as وتجدر الإشارة إلى or أود الإشارة, and consistent use of forms like ذلك rather than colloquial هذا variants.
Profile signals supplement text cues. A reviewer whose Google profile name is a Gulf tribal name in Arabic script is most likely writing in a Gulf dialect. A profile picture showing Gulf dress, or a review history concentrated on Riyadh locations, reinforces Najdi or Hijazi routing. These are secondary signals — never override clear text cues with profile signals, but use them to resolve ambiguity in short reviews.
Low-text reviews (three words or fewer, or emoji-only reviews with a rating) cannot be dialect-detected. For these, warm MSA is the correct default.
The five-dialect routing table
This table maps the primary reviewer cues to the recommended reply dialect and the fallback if a specialist is not available. The routing logic is: match the dominant dialect first; if ambiguous, match the broader regional register; if still ambiguous, warm MSA.
| Reviewer signal | Primary reply dialect | Dialect markers to include in reply | Fallback | |---|---|---|---| | وش / يبغى / ما عجبني / Riyadh or Najd geographic reference | Najdi Arabic | وش + verb constructions; يبغى for wants; ما + verb negation; warm informal address | Warm Gulf Arabic | | يكسف / بعدين / Jeddah or Mecca reference / Hijazi name pattern | Hijazi Arabic | يكسف where appropriate; بعدين for sequencing; warmer and slightly more expressive than Najdi | Warm Gulf Arabic | | شلون / يدري / وين / UAE or Kuwait or Qatar reference / English code-switch | Khaleeji Arabic | شلون; وين; يدري; avoid heavy Gulf formality; mirror code-switch level if reviewer code-switched | Warm Gulf Arabic | | إيوة / عايز / مش / زي / Egyptian name pattern or Cairo reference | Egyptian Arabic | إيوة; عايز/عايزة; مش for negation; زي for comparison; warm Cairo register | Warm MSA | | Full formal Arabic / consistent إعراب / academic vocabulary | Formal MSA | Maintain formal register; full sentences; avoid dialect markers entirely | Standard MSA | | Dialect blend (two or more dialects mixed) | Dominant-dialect-first + warm MSA bridge | Match emotionally charged words to dominant dialect; use MSA for structural sentences | Warm MSA | | Low-text or emoji-only | Warm MSA | No dialect markers; short, warm, genuine | Standard MSA |
The key principle in this table is that the routing decision is made at the cue level, not the rating level. A five-star review in Najdi Arabic gets a Najdi reply. A one-star review in Najdi Arabic also gets a Najdi reply. Dialect matching is not a reward for positive reviewers — it is the baseline of genuine communication.
Team implementation: building a dialect-capable reply operation
Knowing how to detect and route dialects is the analytical half of this playbook. The operational half is building a team structure that can execute it consistently, especially across multiple locations and high review volumes.
Per-dialect specialists. The ideal structure assigns at least one reviewer per primary dialect to your reply workflow. This does not mean five full-time employees; it typically means one or two people who are primary-dialect speakers for Najdi and Hijazi (covering the largest Saudi review volume), one person fluent in Khaleeji across its main variants, and one person for Egyptian. In practice, many multi-location operators in Saudi Arabia cover Najdi and Hijazi internally and contract a Khaleeji and Egyptian specialist for part-time review coverage.
Fallback rotation. When a specialist is unavailable — leave, high volume surge, off-hours — the fallback chain matters. The fallback should be documented: who covers which dialect when the primary is out, and what the maximum reply window is before the fallback triggers. A review waiting 18 hours for a dialect specialist is worse than a prompt warm MSA reply. Set a maximum waiting window — typically four hours for one- and two-star reviews — before the fallback automatically applies.
Training program. Native dialect competence is not enough for review reply work. Specialists need training on three additional dimensions: the brand voice guidelines (how the company expresses warmth, accountability, and resolution in its dialect); the escalation thresholds (which reviews go to management before any reply is sent); and the common complaint patterns for each location type (restaurant versus hotel versus clinic complaint patterns differ, and dialect-appropriate replies for each pattern should be pre-prepared as starting templates). A four-hour onboarding session plus monthly calibration review is sufficient for most teams.
Audit cadence. Dialect drift is real — specialists tend to revert toward MSA under time pressure, especially on high-volume days. A bi-weekly audit that pulls ten random replies per specialist, evaluates them against a dialect authenticity rubric, and provides written feedback keeps quality consistent. The rubric should score three things: dialect marker accuracy (are the right cues present?), warmth register (does it read like a local person, not a template?), and resolution completeness (does it address the specific complaint, or is it a generic acknowledgement?).
Multi-location consistency. A business with twelve locations in Riyadh, three in Jeddah, and two in Dubai needs dialect routing that reflects the location context as well as the reviewer dialect. A Khaleeji reviewer at the Dubai location should receive a Khaleeji reply regardless of which team member handles it. This means routing must be location-aware: the reply workflow should surface the location alongside the review so the specialist knows both the reviewer's likely dialect context and the local team's operational context.
Specialist brief cards. Each dialect specialist should have a one-page brief that covers: the ten most common vocabulary markers in their dialect for quick reference; five pre-approved opening phrases in dialect (warm, neutral, and apologetic registers); the escalation contact for that location; and the brand voice principle in two sentences. Brief cards reduce dependency on memory under pressure and keep replies consistent across specialists.
Pitfalls: the mistakes that undermine dialect routing
Knowing the strategy is not enough if common implementation failures undo it. These are the four pitfalls most likely to appear in the first three months of a dialect-routing program.
The MSA default that strips warmth from every reply. The most common failure is reverting to formal MSA under pressure — high volume, staff absence, or a particularly sensitive complaint that makes the reply writer reach for distance as protection. Formal MSA in an Arabic review reply reads as cold, bureaucratic, and impersonal. It signals that the company is not present locally and is operating through a filter. This effect is worse in Najdi and Egyptian contexts where the gap between formal MSA and the colloquial register is widest. Train your team to see formal MSA as a last resort rather than a safe default.
Over-confident dialect detection on ambiguous text. Automated dialect detection tools and even experienced human reviewers make errors on short text, blended dialects, and code-switched reviews. The worst outcome is confidently producing a Khaleeji reply for a reviewer who is clearly Egyptian — the mismatch is jarring and signals carelessness rather than warmth. Build in a confidence threshold: if the dialect signal is ambiguous, default to warm MSA rather than forcing a dialect assignment. Flag ambiguous reviews for a second human read before sending.
Ignoring Arabic-speaking expat communities in GCC. The GCC countries host enormous Arabic-speaking expat communities — Egyptian, Levantine, Sudanese, Moroccan, and Iraqi Arabic speakers who write reviews in their home dialects. A business in Dubai or Riyadh treating all Arabic reviews as Gulf Arabic misses a significant portion of its reviewer base. Egyptian Arabic alone accounts for a disproportionate share of Arabic-language digital content and review writing because Egyptian media has built the largest Arabic-language internet audience. If your customer base includes Egyptian, Levantine, or other non-Gulf Arabic speakers, your routing table and specialist roster should reflect that.
Missing the dialect-blend reviewer. Saudi Arabia's cities, particularly Jeddah and the Eastern Province, have decades of internal migration and Gulf expat mixing that produces reviewers who blend dialects natively — Hijazi-Egyptian blends from Egyptian families resident in Jeddah for generations, Najdi-Khaleeji blends from Eastern Province border communities. These reviewers do not fit cleanly into any routing category. Trying to force them into one by picking one dialect and ignoring the other often produces a reply that feels like it is talking to a different person. The correct approach is to use warm MSA as the structural base and insert two or three dialect markers from the dominant dialect in the review's emotional language, producing a reply that feels locally aware without over-committing to a single regional identity.
Measuring dialect routing performance
You cannot improve what you do not measure. Dialect-routing programs that run on intuition alone drift toward MSA within weeks. These three metrics give you the data to hold the program accountable.
Per-dialect response rate. Track the percentage of reviews in each dialect category that receive a dialect-matched reply within your target window. A program operating well should show response rates above 90% for each dialect segment during business hours, with a lower but still tracked rate for overnight and weekend reviews. If one dialect segment consistently underperforms, you have identified either a staffing gap or a routing failure.
Per-dialect reviewer update rate. Of all the reviewers who received a dialect-matched reply and whose issue was subsequently resolved, what percentage updated their star rating upward? This metric requires a 30-day measurement window from the date of reply. Benchmark across dialect segments: if Egyptian reviewers are updating at 35% but Najdi reviewers are only updating at 18%, investigate whether your Najdi replies are genuinely dialect-matched or reverting to Gulf-formal register. The update rate is the clearest signal of perceived authenticity.
Per-dialect satisfaction survey score. For businesses that run post-resolution customer surveys (via SMS or email follow-up), segment the results by reviewer dialect. Ask a single question: "Did our response feel personal and relevant to you?" Track scores per dialect segment monthly. This survey signal is more sensitive than review update rate because it captures the emotional response of customers who felt heard but chose not to update their review.
Review your metrics monthly for the first quarter of operation, then quarterly once the program is stable. Bring your dialect specialists into the review meeting: the people doing the work often see failure patterns in the queue before the metrics catch them.
What to do next
Dialect routing is not a one-time setup. It is an ongoing operational commitment that compounds in value as your review volume grows and your team builds genuine dialect competence. The businesses that do it well treat it as a core part of their local brand identity — the signal that they are genuinely part of the communities they serve, not a brand that happens to have a location there.
Start by auditing your last 30 replies for dialect matching. Count how many were sent in formal MSA when the reviewer wrote in colloquial Arabic. That number is your baseline. Then apply the routing table in this playbook to those same 30 reviews and see how many would have been routed differently. The gap between your current practice and the routing table output is your improvement opportunity.
For the apology language and accountability tone that dialect-matched replies need to carry, see the full guide on apology tone in Arabic review replies. For how reply quality affects your Google Maps ranking in Arabic searches, see local pack ranking for Arabic search. To connect your Google Business Profile and activate dialect-aware reply workflows, start at Taqymat onboarding.