A Gulf border-crossing authority
Transportation / Border Operations · Gulf
The shape of this problem
The answer exists and nobody can find it
The problem
Travelers needed immediate answers on crossing times, vehicle-insurance validity, and digital services, while service teams needed a scalable alternative to repetitive contacts. These questions are time-sensitive and usually asked when the traveller is already en route, so an answer that arrives at the end of a contact-center queue has little value. Insurance validity in particular cannot be answered correctly from a static FAQ - it requires a live check against the source system.
What we built
We implemented an Arabic-English virtual assistant across WhatsApp, web, and mobile-ready channels, connected to vehicle-insurance and customer-experience services through secured APIs, with human escalation and administrator access to conversation logs, dashboards, content controls, and service reports.
What moved
| Measure | Before | After |
|---|---|---|
| Response time for common traveller questions | † | down 55% |
| Routine demand handled without entering the contact-center queue | not measured | 35% |
| Digital self-service completion | † | up 28% |
† Measured against the prior level of the same measure. The source publishes the size of the movement, not the figure it moved from.
Response time for common traveller questions
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.
Routine demand handled without entering the contact-center queue
35%
Routine demand handled without entering the contact-center queue
The ring is the whole of that measure. The grey arc is the other 65%.
Digital self-service completion
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
Freshness checks and explicit fallbacks were central to the result - the assistant reduced workload only where the source system could support a dependable answer, rather than containing conversations behind stale or speculative responses. Relevant to any service where the customer is mid-journey and a confidently wrong answer costs more than no answer.
- Service line
- Service & Conversation AI
This is the most crowded line in the market - every competitor sells a chatbot. Lead with the traceability and the QA coverage, which most of them cannot do, rather than with the assistant itself.
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.