Will it explain what is covered under a policy?

It answers from the documents you connect, with sources shown. Anything that amounts to a cover decision goes to a person.

Can we automate renewal reminders?

Store the renewal date as a field, segment on it, and send with consent screening and frequency caps. Campaign-scale sends queue for approval.

Do you hold a compliance certification?

No. Everything described here is a capability of the software, and you can check each one against the product.

Can we prove what a customer was told?

Every send is logged with the approver and the exact message that went out, and you can read that record inside the product at any time.

Can customers send claim documents by message?

Yes on WhatsApp and Messenger. Attachments are stored against the contact, under the same access limits as the rest of the record.

Can agents be limited to their own policyholders?

Yes. A member can be restricted to assigned contacts, with personal details masked at the point they are read.

Can we send claim status updates automatically?

Status changes can go out as an update on the same thread. The underlying records have to be pushed in from your systems for the answer to be real.

Can we restrict who sees policy documents?

Yes. Contact visibility is limited per person, personal details can be masked, and export and deletion can be blocked individually.

Renewals chased, claims handled by people.

Your own policy wording answers the question instead of a hold queue. Claim decisions wait for a person.

Insurers, brokers, and agents use business messaging for the servicing half of the policy lifecycle: renewal reminders, document collection, claim status updates, and process explanations. Because a wrong statement about cover carries real consequences, the useful setup answers what is written down and refuses to decide anything that requires judgment.

What usually goes wrong.

Renewals lapse quietly: A renewal that needed one reminder and got none is lost revenue that never announced itself.
Claim status questions arrive constantly: The customer wants to know where their claim is, which is a status lookup, and it is answered by someone whose time should go to the claim itself.
Documents arrive as photographs in a personal inbox: Policy documents and claim evidence sent to a personal number are outside any record of who received them and when.

What Otobiz does about it.

Renewal reminders from a segment

Store renewal dates as a field on the contact, segment on the month or the days remaining, and send a reminder with consent screening, pacing, and frequency caps applied.

Date fields on the contact with month and range conditions
Sequences with steps that exit on reply
Quiet hours in the customer's own timezone

A hard refusal on anything that decides something

Cover decisions, claim outcomes, and payment actions do not send themselves. They wait for someone to approve the exact message that goes out.

Approvals restricted to owners and admins
The message you approved is the message that sends
Approvals expire on their own

A record of every message

Every send and every decision is logged, and nothing in that record can be edited or deleted afterwards.

One unbroken record per workspace
Insert-only for the application
Nightly verification that escalates on a break

Documents collected on the thread

Customers send documents on WhatsApp, they attach to the conversation and the contact record, and access to them follows the same per-person restrictions as everything else.

Attachments stored against the contact
Per-person visibility limits and data masking
Deletion of a contact removes its messages and attachments

Claim status without a phone call

Status questions are answered from the records you push in, and a status change can go out as an update on the same thread, which removes the call that produces no new information.

Status answered from your own records
Updates sent on the thread the customer already has
No matching record means a handoff rather than a guess

What matters most here.

Common questions

Will it explain what is covered under a policy?: It answers from the documents you connect, with sources shown. Anything that amounts to a cover decision goes to a person.
Can we automate renewal reminders?: Store the renewal date as a field, segment on it, and send with consent screening and frequency caps. Campaign-scale sends queue for approval.
Do you hold a compliance certification?: No. Everything described here is a capability of the software, and you can check each one against the product.
Can we prove what a customer was told?: Every send is logged with the approver and the exact message that went out, and you can read that record inside the product at any time.
Can customers send claim documents by message?: Yes on WhatsApp and Messenger. Attachments are stored against the contact, under the same access limits as the rest of the record.
Can agents be limited to their own policyholders?: Yes. A member can be restricted to assigned contacts, with personal details masked at the point they are read.
Can we send claim status updates automatically?: Status changes can go out as an update on the same thread. The underlying records have to be pushed in from your systems for the answer to be real.
Can we restrict who sees policy documents?: Yes. Contact visibility is limited per person, personal details can be masked, and export and deletion can be blocked individually.