A Gulf tax authority - Arabic NLP, agent assistance
Government / Tax and Customs · Gulf
The shape of this problem
The answer exists and nobody can find it
The problem
Employees and service agents needed precise answers from extensive Arabic tax guidance, without slow manual searches and without relying on unsupported general-model knowledge. An agent on a live contact has minutes, and tax guidance is long, written in formal Arabic, and unforgiving of approximation. Both available options were bad: search several guides while the taxpayer waits, or defer the question and generate a follow-up contact that would not have existed otherwise.
What we built
We implemented a retrieval-augmented question-answering pipeline over the Gulf tax authority's documents - extracting and chunking source content, retrieving relevant passages with multilingual embeddings, and prompting JAIS and other Arabic-capable models to produce grounded responses inside an agent-assist interface.
What moved
| Measure | Before | After |
|---|---|---|
| Agent search time for tax guidance | † | down 65% |
| First-contact resolution | † | up 30% |
| Unsupported or off-context answers | † | down 38% |
† Measured against the prior level of the same measure. The source publishes the size of the movement, not the figure it moved from.
Agent search time for tax guidance
Measured against the client's own prior process, indexed to 100. The source publishes the size of the movement, not the absolute figure it moved from.
First-contact resolution
Measured against the client's own prior process, indexed to 100. The source publishes the size of the movement, not the absolute figure it moved from.
Unsupported or off-context answers
Measured against the client's own prior process, indexed to 100. The source publishes the size of the movement, not the absolute figure it moved from.
Figures are drawn from the practice's own delivery records for the engagement named, measured against the process that preceded it. They have not been through third-party audit, and none is presented as an average across clients.
What it turned on
The service became faster not by trusting the model more, but by reducing the evidence an agent had to inspect and making the boundary between sourced guidance and model generation explicit - retrieval relevance, factual support, Arabic language quality, and output format were evaluated separately, and weak-evidence cases withheld a definitive draft rather than producing one.
- Service line
- Workflow Copilots & Agents
The platform story is the strong one, and it is the argument for doing the foundations once. Lead with the structure, not the assistant.
Start here
Which of the four is yours?
Tell us the documents and the monthly volume and we will send the two closest records, with the proof behind each and the honest note where the match is partial.
You get a reply within one working day, from the engineer who would do the work - not a sales sequence.