Telecom and ISPs
See every industryFits the desk that sells connections. Not the floor that fixes them.
Selling a new connection is a short, competitive sales conversation — coverage, speed, price, install date — and it happens on WhatsApp. Everything after installation is a support operation, and that is not what we are.
- New-connection enquiries as a pipeline
- Coverage and install questions get an owner
- Your last 90 days, imported
Is it right for you?
Not a support platform, and it cannot send an outage notice
Two things make us the wrong tool for an ISP's support operation. First, we cannot message anyone who has not messaged us — the API deliberately has no endpoint that opens a conversation — so an outage notice to affected customers is impossible here and always will be. Second, the plan on sale is three people in one shared workspace with no role separation and no per-queue SLA, which is not a support floor. If either of those is the job, stop here.
What it does solve well
The sale of a connection, which is short, competitive and lost on response time.
Coverage questions get answered before the competitor's do
Whoever is free picks it up, and each conversation has an owner. On a new connection the provider that replies first usually wins.
The quote that stalls has a follow-up date
Snooze to two days after the quote went out. In a market where three providers quoted the same street, that single nudge is the difference.
You find out which street you keep losing
Label by neighbourhood and record a lost reason. Price, speed, install date — that is a coverage-investment report nobody currently produces.
Three routines for the sales desk
All of it is on the plan we sell today.
Coverage enquiry
The first question, always, and the one that decides speed of reply.
- Quick replies with plans, speeds and what you need to check coverage
- Label by neighbourhood straight from the row
- Business hours answer in the evening, when people ask
Quoted, waiting on install
The window where a competitor books the Saturday first.
- A Quoted stage with the monthly value on the card
- Snooze to two days after the quote
- Custom fields for address, plan and install preference
After the install
The first month decides whether they stay a year.
- One satisfaction question after installation
- A keep-in-touch cadence before the contract anniversary
- A lost reason when somebody cancels, in their words
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 account data, no tickets, no broadcasts
Unibox does not know a customer's plan, balance or connection status, has no ticketing, and cannot start a conversation. Everything it shows about an account is what somebody typed into a custom field. Your OSS or billing system remains the source of truth and we do not connect to it.
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 providers ask first
Can we notify customers about an outage?
No, and this will not change. We have no endpoint that opens a conversation and no bulk sending. An outage notice is a broadcast, which is exactly the behaviour that gets a number banned — so we do not build it.
Can it pull the customer's plan or balance?
No. There is no integration with billing or provisioning. What you see is what somebody typed into a custom field.
Our support team is twelve people. Does that fit?
No. Three people, one number each, one shared workspace, no roles. For a support floor that is the wrong shape and we would rather say so than sell you a trial.
So who is this actually for?
A small regional provider whose sales desk is two or three people quoting new connections on WhatsApp. That specific job it does well.
If it is the sales desk you want fixed, connect it and see the open quotes
14 days, no card. If it does not suit you, you stop and you keep your data.