Your business number,
answered by someone who works.
Not an FAQ bot. An agent with its own working space on our infrastructure — your SOPs, access to the systems you already run, and a human handover whenever it matters. Onboarded in days, not months.
A chatbot answers.
You need one that works.
Almost every WhatsApp bot stops at a sentence. The actual job goes back to the same person it always did.
It replies from a FAQ list written three months ago. The price moved, the hours changed, the item ran out — and nothing told the bot.
A question outside the flow ends the conversation with "please wait for an admin". The customer is already waiting, and your team still does the work.
Orders, complaints and booking requests all arrive as notifications someone then has to retype into another system by hand.
An operator, not
an auto-reply
Every number we handle gets its own working space: your SOPs, your notes, and access to the systems your business runs on. The agent reads and works there before it answers.
Replies are assembled from a static FAQ that somebody has to remember to update.
The agent reads the real source first — catalogue, schedule, order status — and answers from that.
Every request becomes a manual task queued for your team.
The agent performs the steps it is allowed to perform — logging the order, preparing the recap, drafting the document — and reports the result back.
The conversation is passed on and the customer repeats their story.
You step into the same conversation whenever you want, read everything that happened, and the agent stands down while you are there.
One number,
many roles
Routing is exact, per person and per group — so the vendor group never sees what the internal group sees.
A specific conversation goes to a specific working space. Customer service, vendors, and internal ops can each have their own, on one number.
Answer everything, answer only when mentioned, or stay silent and simply keep the record — set differently for each conversation.
In a group the agent replies only when it is addressed. It does not interrupt a room full of people talking to each other.
Telegram and Slack run through the same routing model, so a second channel is configuration rather than a rebuild.
Send manually from the same number any time, and switch the agent off in one conversation without touching the others.
Pair your own business number, or begin on our shared line while you decide whether this fits.
The limits, before
you have to ask
These three usually surface after signature. We would rather you knew now, and walked away now if they do not suit you.
Your number connects as a linked device, the way WhatsApp Web does. That is what makes setup fast and removes per-template message fees — but it is not a Meta-official integration, and we do not promise immunity from account restrictions. If your business needs the official route, that is a different path and we will say so rather than sell you this one.
Each client gets its own working space: separate routes, separate SOPs, separate data of work. All of it runs on our managed infrastructure rather than in a per-customer isolated environment. For data that requires formal isolation or certification, we will tell you this is not the right home for it.
We onboard a small number of businesses at a time, because each working space is built by hand and tuned after real use. There is no sign-up button, and that is deliberate.
Where most
engagements start
Scope is agreed after a short discovery, and cost is quoted against that scope — there is no fixed price list and no padded package.
One number, one working space
- One WhatsApp number, paired or shared
- Working space with your SOPs and catalogue
- Auto-reply with group rules
- Human handover from the same number
- Tuning after go-live
Several roles behind one number
- Everything in Starter
- Separate routes per person and per group
- Access to the systems you already run
- Scheduled recaps and reports
- Regular tuning sessions
Many brands, or many clients
- Several working spaces side by side
- A separate number per brand
- Same model for Telegram and Slack
- Built for agencies and business groups
From first chat
to live
No procurement theatre. The person who scopes it is part of the team that operates it.
What arrives on your number today, who answers it, and which part of that is worth handing over. If a simpler tool solves it, we say so.
Your SOPs, catalogue, tone and rules become the space the agent works in — plus the routes that decide who reaches which one.
The number is paired, routes are switched on, and real messages start becoming real turns. You watch the first ones with us.
The first weeks change the SOPs more than the software. We read what actually came in and adjust against it.
Typical time from first chat to live: days, not months. What takes the time is agreeing how your business answers, not the setup.
Asked before
reaching out
Tell us what arrives onyour number all day.
A short, no-pressure conversation about what your number handles today and which part of it is worth handing over. If this is not the right fit, we will say so.