Bilingual Service Desk answers in two languages
A front door in two languages, English and French in Canada or English and Arabic in the GCC, answering from approved bilingual sources that a fluent person at the client reviews.
The problem it answers
Customers write in more than one language while staff answer in one, and iSystematic's Bilingual Service Desk answers them in both, from the same approved sources.
What it does
It is a front door in two languages: English and French in Canada, English and Arabic in the GCC. Answers are drawn from approved bilingual sources, and each answer exists in both languages, linked, with the translation's lineage and its fluent reviewer.
A fluent person at the client reviews the bilingual knowledge base, and the action policy is agreed, before go-live.
It builds on the Front Door Agent and runs on ARIA by Simplification.io, which the client subscribes to directly with Simplification. Per Simplification's published corpus (checked 9 October 2026), ARIA works in English, French and Arabic.
Where answer quality differs by language, the model tier is chosen per language. Where data may sit is chosen from the residency rules of each jurisdiction.
Built from
It is built from the Front Door Agent, ARIA's languages and one catalogue pattern.
| Id | Name | What it brings |
|---|---|---|
| S3 | Front Door Agent | The front door, its action policy and its records |
| ARIA | ARIA by Simplification.io, its languages | English, French and Arabic, per Simplification's published corpus (checked 9 October 2026) |
| P01 | Retrieve, Ground, Draft, Review | Answers only from approved sources, in either language |
What it is built on
Five parts of the framework corpus decide how two languages stay one service, and each leaves a record the client keeps.
| Framework | In this solution | Client keeps |
|---|---|---|
| The Front Door Agent set (S3) | PARA, Tiered Human-in-the-Loop (AP-4), Capability Contract (AP-5), the AI Vendor Risk Framework (AVRF)™ and event identity, as in S3 | As in S3: agent registry entry, approval records, a contract per tool, vendor records, conversation trail |
| AI Data Governance Framework™ | Each answer exists in both languages, linked, with the translation's lineage and its fluent reviewer | Bilingual source register |
| Tiered Model Pool (IP-2) | Model tier chosen per language where quality differs | Routing evidence |
| Cross-Border AI Architecture Patterns™ | Sovereign Silo, Federated or Regional Hub, chosen from the residency rules (Canada; each GCC jurisdiction) | Boundary set; chosen pattern |
| Sharia AI Compliance Framework (SACF)™, for Islamic financial institutions | Dual validation and vendor screening where a Sharia board binds | Dual-validation records |
Five parts apply to every build and are not repeated here: decision rights, the five gate records, a BOE Declaration per control, a vendor assessment for every vendor, and incident response. How we build sets out all of them.
About the Sharia AI Compliance Framework (SACF)™: No Sharia Supervisory Board has reviewed or endorsed this framework. It is an engineering proposal offered for scholarly and institutional review.
The evidence it leaves behind
Every conversation leaves records the client keeps.
- Language-tagged receipts
- A bilingual source register
- Routing evidence
- The boundary set and the chosen residency pattern
- The Front Door Agent's records: registry entry, approvals, tool contracts, vendor records, conversation trail
- Dual-validation records, where a Sharia board binds
Typical buyer
The typical buyer is a customer-service team in Canada or the GCC.
Status
Proposed, as of 9 October 2026. A solution becomes Piloting or Released only after a documented pilot, and no result is shown for it before then.
How to start
Most organisations start with a six-week Pilot of the Bilingual Service Desk on one queue. The baseline is taken first, in the service team's own measures: first-contact resolution, handle time, escalation rate and quality sampling of replies.
Organisations still choosing their first task start with the Automation Assessment.
Where to go next
Customer service
Customer-service leaders: iSystematic pilots a bilingual front door on one queue for six weeks, measured in your own terms against a baseline taken first.
Front Door Agent
The Front Door Agent gives an organisation one front door across email, web chat, WhatsApp and forms, built on ARIA by Simplification.io, with people approving.
Knowledge Desk
The Knowledge Desk answers staff questions only from approved, versioned documents, cites the section, and refuses when the source is missing or retired.
Pilot
iSystematic's Pilot puts one solution live for one team for six weeks, measured against a baseline from day one: the only route to a published result.
How we build
How iSystematic builds: every solution uses the same deposited frameworks. See what each part decides, what the client keeps, and each specification's DOI.
Conformance is self-declared; no regulator endorses this work.
Start with a Pilot
Six weeks, one solution live for one team, measured against a baseline taken before it starts.