Skip to content

Insurance and fintech

See every industry

An independent broker's renewal desk, yes. A regulated operations floor, no.

Renewals are a dated, repeatable sales conversation and they happen on WhatsApp. But if your compliance checklist asks for audit trails and role separation, we fail it today — read the next section before anything else on this page.

  • Renewals as dated follow-ups, not a spreadsheet
  • Every conversation has an owner
  • Your last 90 days, imported

Is it right for you?

Not for a firm whose compliance checklist asks for audit trails

On the plan we sell there is no audit log, no permissions by role and no choice of data region — logging and role permissions sit on the Empresa tier, which is not on sale, and the database runs in the United States. Message bodies get no separate encryption layer from us. If you have to demonstrate who read what, keep an immutable record of advice given, or hold data in a particular jurisdiction, we would fail your review and you should not start a trial. That is a description of today, not a promise about later.

What it does solve well

The broker's own book: renewals that arrive on a date, and quotes that need chasing.

Renewals stop being a spreadsheet nobody opens

A keep-in-touch cadence on the policy date brings the client's own thread back before expiry, with the whole history attached.

The quote that goes quiet gets chased

Snooze to the day after you sent the comparison. In broking, the second follow-up is where most of the conversion actually is.

Two brokers stop working the same client

Every conversation has an owner, and an unanswered one comes back to the pile marked rather than sitting with whoever forgot it.

Three routines for a broker's desk

All of it is on the plan we sell today.

New enquiry in

Three brokers quoted the same person this week.

  • Quick replies listing exactly what you need to quote
  • Label by line of business straight from the row
  • Custom fields for policy type, insurer and renewal date

Quoted, deciding

The gap where price alone wins if nobody calls.

  • A Quoted stage with the premium on the card
  • Snooze to the day after the comparison went out
  • A lost reason when they go direct — that is the report that matters

The renewal calendar

Predictable revenue that depends entirely on timing.

  • A keep-in-touch cadence set to each policy's own date
  • The report shows which renewals were not worked
  • One satisfaction question after a claim is settled

What Unibox does not do

Said here rather than discovered after you subscribe. It is the reason to believe the rest of this page.

No bulk sending

There is no blast, and there is a cap on how much leaves each number. That is a decision rather than a gap: blasting is the fastest way to lose your business's number.

It cannot message someone first

Our API replies inside a conversation that already exists and deliberately has no endpoint to open one. Every automation here starts after the person has messaged you.

No audit log, no roles, no data residency choice

Everyone in the workspace sees every conversation, nothing records who read what, and the data lives in one United States region. There is no policy administration, no claims handling and no integration with an insurer. This is a conversation tool being honest about being one.

Roadmap — not live yet

Caio, our chief AI officer

He reads the conversation and writes the draft. You are the one who sends it.

Caio is being built, and this section exists to say what he will do rather than to imply he already does it. Nothing above on this page depends on him.

  • Drafts the reply with the customer's history to hand — you review and send
  • Reads “call me Tuesday” as a snooze and sets the return
  • Summarises a three-week thread for whoever just picked it up

The badge comes off the day he ships. Until then he is not a feature and he is not in the price.

Before you connect your number, read this

We connect by QR code, the way WhatsApp Web does — no Business API, no Meta verification, no waiting. The cost of that is real: WhatsApp's terms do not permit unofficial clients, and it may warn, restrict or ban a number that uses one. The risk is yours, it rises with volume, and it is why we cap sending and do not blast. The advice we would give a friend: connect the business's number, not the owner's personal phone.

Read section 5 of the terms →

One plan, one price

14 days free, no card. No free plan.

US$ 10

Up to 3 people · 1 WhatsApp number each

Start free for 14 days

What brokers and fintechs ask first

Do you have an audit log?

Not on the plan we sell. Audit logging sits on the Empresa tier, which is not on sale today. If your regulator or your own policy requires it, we are not compliant with your requirement and we will not imply otherwise.

Can we keep data in our own country?

No. The application and database run in the United States, and that is not configurable. Our privacy page states it plainly.

Can we restrict which broker sees which client?

No. Role permissions are on the Empresa tier. On the plan we sell, everyone in the workspace sees every conversation.

So who is this genuinely for?

A small independent brokerage of two or three people whose renewals and quotes live on WhatsApp and currently on one phone. For that, it works well and honestly.

If you are a small brokerage and the renewals live on a phone, connect it

14 days, no card. If it does not suit you, you stop and you keep your data.

WhatsApp for insurance brokers — and why a regulated desk should not use it — Unibox