Policy-grade messaging
for insurers and InsurTech.

The template manager enforces a data-light pattern: the message carries a signed, expiring deep-link to your policyholder portal, and the sensitive data stays in your policy admin or claims system. Nothing beyond what a policyholder needs to recognise the message travels over the wire, which keeps you inside PDPL and GDPR data-minimisation expectations.

Yes. A single template manager covers your full renewal lifecycle across markets, with per-jurisdiction consent, quiet-hour and sender-ID rules applied automatically, and billing in AED, SAR, USD or EUR. Insurers typically consolidate several country-level SMS contracts onto one BroadNet agreement.

For most personal-lines servicing, yes — as an official Meta Business Solution Provider we run branded, two-way WhatsApp with agent handoff for complex cases. Because the data stays behind a portal deep-link, the conversational layer never becomes a data-protection liability.

For market conduct we align to UAE (CBUAE) and KSA (SAMA) insurance expectations around policyholder communication and treating customers fairly; for data protection we hold ISO 27001 and SOC 2 Type II and operate PDPL and GDPR consent ledgers. We do not claim PCI-DSS — payment-card handling stays with your payment provider behind the pay-now link.

Alerts go out on registered, sender-ID-protected routes on your brand, so impersonators cannot reuse your sender identity on direct operator routes. Combined with delivery receipts, that gives your fraud team a defensible record of exactly what was sent and when.

A TPA sending FNOL acknowledgements and status updates through our REST API is typically live in under four weeks, including sender-ID registration in each market. The claims webhook maps closely to common claims-platform event shapes, so the integration is usually a small piece of work.