The same engine, five different compliance shapes
What changes between industries is not the routing engine — it is which systems must be written to during the call, what may be recorded, and who has to approve the flow before it goes live.
Where Ittisal is deployed
Fintech and banking
Identity verification before any account data is read back, transaction disputes filed into the core system, and recordings encrypted in your own object store for regulator access.
Government services
In-country deployment with zero audio egress, Arabic-first flows with English fallback, and appointment booking against national scheduling systems.
Logistics and last mile
Tracking lookups inside the voice turn, delivery rescheduling on WhatsApp, and driver callbacks placed from the same queue.
E-commerce and retail
Order status, returns intake and payment links on WhatsApp, with peak-season capacity absorbed by AI minutes rather than seasonal hiring.
Healthcare
Appointment scheduling and reminders with clinical data kept out of the transcript, and consent captured on the recorded leg before any detail is discussed.
What we ask your compliance team
Before a flow is published we need four answers, and they are usually the whole integration conversation.
- Which data may appear in a transcript, and which must be redacted before storage
- Where recordings live, for how long, and who may retrieve them
- Whether inference may run on a managed tier or must stay in-boundary
- Who signs off a flow revision before it reaches production traffic
Tell us your sector and its constraints
We will come back with the flow shape, the residency model and the systems that need connectors.