Each carries its own rules on consent, recording and data residency. The platform is configured to them per market rather than shipped with one global default.
Every control on this page exists so an agent can answer a call without checking which rules apply, and a supervisor can prove afterwards that they were followed.
Meet the team behind itRecording a call, storing a transcript and messaging a customer are all regulated acts. These are the frameworks the platform is designed to operate under.
Compliance is shared: the platform provides the controls, and your organisation remains the data controller for how they are configured and used. Current certificates, sub-processor lists, the DPA and the security questionnaire are available under NDA — ask your specialist during activation.
Configured per queue and per market, not set once globally.
Retention, routing and AI scope change by industry — the console does not.
The floor view a supervisor keeps open all day. Every channel sits in the same queue model, so WhatsApp traffic is measured exactly like the phone lines.
Every deployment is led by named people on our side and yours — not a ticket queue.
Every connection can come from you or from us — and you can mix per country. Switch later without changing platforms.
Most customers mix: their own trunk in one country, our numbers in another.
Send us your sector and markets. We will come back with the residency, retention and consent configuration that applies, and the evidence pack your compliance team will ask for.
