Insurance
Renewal, premium status and first-notice-of-loss answered in Bangla, with policy facts read from your policy admin system.
Insurance in Bangladesh runs on a long tail of small policies and a distribution network of agents who cannot personally chase every renewal. The result is predictable: policies lapse not because the policyholder decided against them but because nobody reached them in the window, in their language, with the exact figure. At the same time, the inbound line carries premium-due questions, policy status, nominee and address changes, and the first report of a claim, which is the single moment where a clumsy experience does lasting damage. We put the same Bangla voice brain across both directions, grounded in your policy administration system so that the premium figure, the due date and the policy status it reads are the real ones.
The problem before the product.
Lapses that were reachability failures
A renewal that lapses after no contact, or one SMS, is not a pricing problem. It is an outreach capacity problem, and it compounds quietly across a book of small policies.
Agent-dependent service
When policy questions can only be answered by the agent who sold the policy, service quality tracks that one person's availability, and it collapses when they leave.
First notice of loss arrives unstructured
The first claim call is emotional and unstructured. What the claims team needs is a complete, consistent intake. What it usually gets is a callback note.
Policy language does not survive translation on the fly
Coverage, exclusions and waiting periods stated loosely in Bangla by an improvising system create expectations the policy does not honour.
Built against your
systems of record.
Renewal outreach at book scale
The whole renewal list, not the top slice. Each call states the real premium and due date from policy admin, honours consent and quiet hours, and writes the outcome and any promise-to-pay back to your system.
Policy and premium status on the inbound line
Premium due, paid-to date, policy status, nominee details and maturity dates, read from the policy record after identity verification rather than generated.
Structured first notice of loss
A consistent intake that captures what happened, when, where, the policy involved and the contact path, then creates the claim record and routes it. The caller gets a reference number before the call ends.
Coverage answers that stay inside the wording
Coverage, exclusion and waiting-period questions answer from your approved policy wording and product documents. Anything outside that set is handed to a human instead of improvised.
Agent and branch support
The same engine can answer the agent-facing line so your distribution network gets status and premium answers without occupying the customer queue.
Your systems stay yours.
Nothing here is a replacement platform. The engine reads from and writes to what you already run.
- Policy administration systems
- Claims management systems
- Agency and distribution management platforms
- Existing PBX, contact centre and SIP trunks
- CRM and campaign tooling
- bKash, Nagad and SSLCommerz for premium payment links
What it will not do.
The constraints are the product. A system that cannot be audited cannot be approved.
- Deployable on-premise or in your own cloud tenancy for insurers with data residency requirements.
- Policyholder PII masked before any prompt leaves your boundary.
- Coverage and exclusion answers are drawn from your approved wording set, so what is said on a recorded line matches the contract.
- Consent state, quiet hours and retry caps enforced on every outbound renewal campaign.
- Append-only recording and transcripts, retention set by you, which matters when a claim is later disputed.
Why this sector
works differently here.
The regulators, the systems and the operating reality that decide whether a deployment in this sector actually survives contact with your environment.
IDRA is the regulator to design around
The Insurance Development and Regulatory Authority governs insurers here, and its concerns centre on policyholder protection and what is represented to a policyholder. That is the reason coverage answers are served from your approved wording set rather than generated: a loose statement on a recorded line is a regulatory exposure, not just a service lapse.
Penetration is low, which makes retention everything
Insurance penetration in Bangladesh is very low by regional standards, so the book is built from a long tail of small policies. When acquisition is this hard, a lapse that happened only because nobody made contact is the most expensive failure in the business.
Distribution is agent-led and personal
Most policies here are sold by an individual agent, and service tends to follow that relationship rather than an institution. When the agent moves on, the policyholder effectively loses their service channel, which is where a central Bangla line changes the economics.
Premiums move over MFS
bKash and Nagad are now ordinary ways to pay a premium, which makes a confirm-the-amount-and-send-a-link flow genuinely complete rather than a partial one that ends in a branch visit.
The first build, in about 30 days.
Renewal outreach on one product line, plus premium and policy status on the inbound line, both read from policy administration.
- Renewal calls across the full list for one product line
- Real premium and due date from policy admin, not a template
- Consent state, quiet hours and retry caps
- Promise-to-pay and outcome written back to your system
- Premium payment links over bKash or Nagad
Scoping everything at once is how these projects fail. These come after the first build is answering real calls.
- First notice of loss, which needs claims integration
- Coverage and exclusion answering, which needs the wording set loaded
- The agent-facing line
- Maturity and surrender flows
If three of these are true, book the diagnostic.
Your lapse rate is driven by policies nobody managed to contact in the window.
Renewal outreach depends on individual agents rather than a system.
First notice of loss arrives as free-text callback notes.
Policyholders cannot get a premium figure without reaching a specific person.
Your agent-facing queries compete with customers for the same phone lines.
Will it quote coverage it should not?
It answers from your approved wording and product documents only. Questions outside that set are escalated rather than improvised, because a loose coverage statement on a recorded line is a liability.
Can it take a payment?
It confirms the amount due and sends a payment link through bKash, Nagad or SSLCommerz. Card and account details are never spoken to or captured by the engine.
Does it work for both life and general?
Yes, though the flows differ substantially. Life skews toward renewal, lapse recovery and maturity. General skews toward policy status and first notice of loss. The diagnostic decides which to build first.
A diagnostic, then a written scope.
Forty-five minutes on your call mix and your systems. You get the findings in writing inside 72 hours, and they are yours whether or not we work together.