Marketplaces and platforms
See every industryGood for signing sellers up. Not built for running a dispute desk.
Recruiting and onboarding sellers is a sales conversation, and it is one we handle well. Mediating between a buyer and a seller at volume needs role separation we do not have on the plan we sell — the section below is the one to read first.
- Seller recruitment as a pipeline with owners
- Onboarding steps as stages, not a spreadsheet
- Your last 90 days, imported
Is it right for you?
Not for buyer-seller dispute handling with separated roles
A dispute desk needs one thing we do not sell: role separation, so an agent sees the case they are handling and not everything else. Permissions by role sit on the Empresa tier, and the plan on sale gives three people one shared workspace where everyone sees every conversation. It also has no case management, no SLA per queue beyond a single workspace timer, and no way to keep two brands' inboxes apart except by connecting separate numbers. If disputes at volume are the job, we are not the tool.
What it does solve well
The commercial side of a marketplace: getting good sellers on, and keeping them active.
Seller recruitment becomes a pipeline
Interested, documents in, first listing, first sale. You can see how many stall between signing up and actually listing, which is where marketplaces lose most of their supply.
Onboarding stops depending on one person's memory
Snooze a seller to the day after you sent the guide. The follow-up that turns a signup into a live listing happens on a date rather than when somebody remembers.
You find out why a seller went quiet
A lost reason in their own words — commission, payout timing, a competitor. That is the supply-side report nobody has.
Three routines for the seller desk
All of it is on the plan we sell today.
Inbound seller enquiry
The question is always commission and payouts, in that order.
- Quick replies with commission, payout schedule and requirements
- Label by category straight from the row
- Assign to an owner without opening the thread
Signed up, not listed
The largest leak in any marketplace's supply funnel.
- A First listing stage moved from the row
- Snooze to two days after the guide went out
- Custom fields for category, catalogue size and payout method
Keeping sellers active
A seller who stops listing rarely announces it.
- A keep-in-touch cadence on their listing rhythm
- The report shows who has gone quiet this month
- One satisfaction question after their first sale
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.
One workspace, no roles, no case management
Everyone on the plan we sell sees every conversation. There is no per-role visibility, no case object, no queue-level SLA and no multi-brand separation beyond connecting a different number. For a marketplace's commercial desk that is fine; for an operations floor it is not.
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 marketplaces ask first
Can we restrict what each agent sees?
Not on the plan we sell. Role permissions sit on the Empresa tier and are not on sale today. Everyone in the workspace sees every conversation — say so to your team before you connect anything.
Can we run two brands from one account?
Only by connecting a separate number for each, and each number is a seat. Three seats is the ceiling today, so two brands leaves you one seat for a person.
Can it notify a seller that an order came in?
No. We cannot open a conversation — the API deliberately has no endpoint for it — and we do not know your order state. That belongs in your platform's own notifications.
So what is it good for here?
Signing sellers up and getting them live. That is a sales conversation with an owner, a stage and a follow-up date, and on most marketplaces it currently happens on somebody's phone.
If the job is recruiting sellers, connect the desk's WhatsApp and see the funnel
14 days, no card. If it does not suit you, you stop and you keep your data.