Public sector
See every industryFor most public bodies the answer is no, and it is better said here.
A public body's messaging usually has to be auditable, role-separated, retained under a schedule and held in a named jurisdiction. On the plan we sell, Unibox is none of those things. This page exists so you can establish that in two minutes instead of two weeks.
- No audit log and no role separation on the plan we sell
- One shared workspace, three people, one US region
- An unofficial WhatsApp connection, with the ban risk that carries
Is it right for you?
Not for official correspondence, casework, or anything with a retention schedule
Everything a public body normally needs, we do not have on the plan we sell. There is no audit log, so nothing records who read what. There is no role separation, so every person in the workspace sees every conversation. There is no choice of data region — the application and database run in the United States. There is no self-hosted option. There are no retention or disposal controls, and no accessibility audit. And the WhatsApp connection is an unofficial client, which a public body almost certainly cannot accept as a channel of record. If any of that is on your checklist, we fail it. Please do not start a trial to confirm what this paragraph already tells you.
The one case where it does work
A very small arms-length organisation — a community trust, a sports association, a venue — whose public enquiries already arrive on one WhatsApp number and get lost there.
Nobody's enquiry goes unanswered
The “Never answered” tab shows exactly who wrote and got nothing back, which for a body accountable to the public is the measure that matters.
Two staff stop answering the same person
Every conversation has an owner, and an unanswered one comes back to the pile marked rather than sitting with whoever forgot it.
A handover does not lose the history
When someone leaves, the conversations stay in the workspace. That is the one records-continuity property we genuinely offer.
If you are that small body, three routines
All of it is on the plan we sell today. None of it makes us an official channel.
The repeating enquiry
Opening times, fees, who to contact — most of the volume.
- Quick replies for the questions that arrive every week
- Label by enquiry type straight from the row
- Business hours answer outside opening times
Bookings and hires
The part that has a date and can be missed.
- A Booking stage moved from the row
- Custom fields for the date, the space and the rate applied
- Snooze to the day the form is due back
Nobody left waiting
The accountability measure, not a growth metric.
- A reply timer returns anything nobody picked up to the pile
- The report shows average time to first reply
- One satisfaction question after an enquiry is closed
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.
We are not a system of record, and should not become one
Nothing here should be treated as an official record. There is no retention schedule, no export designed for a records request, no audit trail and no guarantee about jurisdiction. If a conversation would need to survive a freedom-of-information request or an audit, it does not belong in Unibox.
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 daysWhat public bodies ask, and the honest answers
Do you offer self-hosting?
No. There is no self-hosted or on-premise option, and none is planned for the tier we sell. The application and database run on managed infrastructure in the United States.
Do you have audit logging and role-based access?
Not on the plan we sell. Both sit on the Empresa tier, which is not on sale today. On the plan you can actually buy, everyone sees everything and nothing logs who read what.
Can you meet our data residency requirement?
No. One region, in the United States, not configurable. If your requirement names a jurisdiction, we do not meet it.
Is this an approved WhatsApp channel?
No. We connect through an unofficial client, which WhatsApp's own terms do not permit and which can result in the number being banned. For a public body that alone is usually disqualifying, and we would rather lead with it than let procurement discover it.
If the checklist above rules us out, it was meant to. Thank you for reading it.
14 days, no card. If it does not suit you, you stop and you keep your data.