Language scope
Record whether the workflow needs Modern Standard Arabic, relaxed Gulf phrasing, Arabizi input comprehension, code-switching, Arabic tone, or Arabic escalation wording.
Loading AI Team page
A language evidence pack for workflows that need Arabic or bilingual handling, including approved terminology, Gulf phrasing rules, tone rules, test cases, ambiguity behavior, and human reviewer signoff.
Buyer question
Arabic quality is treated as a risk-control feature, not a checkbox. Arabic in UAE business can include Modern Standard Arabic, Gulf phrasing, Arabizi inputs, bilingual phrases, and sector terms. Weak handling can damage trust even when the workflow is technically correct.
Package outcome
Arabic quality is treated as a risk-control feature, not a checkbox.
What buyers should see
Each section should be short enough for an SME owner, manager, or procurement reviewer to understand before approving access or go-live.
Record whether the workflow needs Modern Standard Arabic, relaxed Gulf phrasing, Arabizi input comprehension, code-switching, Arabic tone, or Arabic escalation wording.
Lock approved terms, product names, support phrases, greeting style, Gulf phrasing preference, complaint tone, and never-say phrases.
Test normal, angry, confused, urgent, Arabizi-input, missing-data, policy-sensitive, and unsupported-claim cases before go-live.
Artifact template
Treat Arabic and bilingual handling as scoped quality evidence, with glossary, Gulf phrasing, tone, examples, uncertainty behavior, and reviewer signoff.
Specify Modern Standard Arabic, Gulf phrasing, Arabizi input handling, code-switching, channel, and whether voice is in scope.
channel_language_scope
When Gulf or Khaleeji Arabic is scoped, record the approved relaxed Gulf phrasing instruction. Treat Arabizi as input comprehension and reply in Arabic script unless Arabizi output is explicitly approved.
arabic_gulf_phrasing_instruction
Lock approved Arabic product terms, policy terms, greetings, complaint language, and never-say phrases.
business_rule_consistency
Link approved Arabic FAQs, policy sources, brand tone sources, and unsupported or stale sources.
company_brain_source_scope
Include normal, angry, confused, urgent, missing-data, policy-sensitive, and unsupported-claim cases.
qa_evidence_pack
Define when dialect uncertainty, mixed-language ambiguity, or sensitive topics require human review.
refusal_escalation
Record accepted, blocked, scoped, or review-required with reviewer name and date.
arabic_readiness_decision
Before Arabic go-live and whenever policy, offer, channel, customer segment, or Arabic source material changes.
Risk handling
A package only builds trust when it also explains when AI Team should pause, escalate, re-scope, or decline instead of pushing the Agent live.
Source records
These are the implementation records and public surfaces that should remain aligned as the package becomes a dashboard, PDF, or sales handoff.
Related paths
Use these links when a buyer needs supporting context before setup review.
FAQ
These answers are intentionally practical so owner-operators can decide whether the package is ready, needs review, or should pause setup.
Arabic quality is treated as a risk-control feature, not a checkbox.
The Agent detects dialect uncertainty or mixed-language ambiguity. The Agent drifts into another language or unsupported dialect. The message includes pricing, legal, finance, HR, medical, or policy-sensitive content. Approved Arabic source material is missing or stale. Voice Arabic is requested without a Complex review.
Use AI_TEAM_ONE_PAGER.md, AI_TEAM_AGENT_CATALOG.md, config/agent-evidence-pack.json, src/data/agentic-teams.ts as the starting source records for this package.