Text it from the car park.
Octo on WhatsApp is the same assistant you use in the dashboard, reachable by message. You describe what you want done in a sentence, it does the work and reports back in the thread, and anything that spends money or messages a lot of people stops first and asks you to reply with a short code.
Delegated work draws on your plan’s included credits, and both a monthly model budget and a daily voice-minute cap apply — so a vague instruction sent one-handed cannot become an open-ended bill.
The same assistant, three doors
WhatsApp is one way in. Here are the other two.
Same confirmations, same work, wherever your hands are.
InboxConfirm: text 183 contacts — YES 9127
Text the March lapsed list about the autumn offer.
Reply YES 9127. One use, expires in 24 hours, and the recipient list is frozen as of now — the same code and the same wording you would get on WhatsApp or in Slack.
@Octo how did last night’s text go?
On it 🔧(runningget_sms_delivery_summary…)
183 sent, 179 delivered, 9 replies. Two of the replies want a person. (edited)
✅ 3🎉 12 replies · last reply 18m ago
nice — do the same for the april list
Email octo@agent.omniocto.com · WhatsApp 1-MAN-ASK-OCTO · Slack #omniocto
The whole interface
A message thread, and a code when it matters.
There is nothing to open and nothing to learn. You send a sentence, and the only ceremony is a short confirmation on the things that would cost you something.
You ask in plain words
Describe the outcome. Octo works out which of its tools that needs and asks about the parts you left out rather than guessing.
It asks before it spends
Money, mass messages and destructive actions stop with a plain description and a one-use code. Everything harmless just happens.
It reports back in the thread
What was done, and what was skipped and why — where you asked, so the decision and the record are the same conversation.
From wherever you are
The point of WhatsApp is the car park, the van, the ten seconds between two jobs. The message is one-handed.
The same assistant answers on email, Slack and the dashboard, with the same confirmations. This is a door, not a different building.
How you'd hand it over
Message, approve, read.
Send it a sentence
The way you would text a colleague.
No commands, no syntax, no field names. If something is missing it asks you rather than inventing an answer.
Reply with the code
If it costs, it waits.
You get what it is about to do, how many people it affects and what it will cost, plus a short code. Send the code and it goes; ignore it and nothing happens.
Get the result back
Including what did not work.
Sent, skipped and why — in the same thread. Anyone who was on a do-not-contact list is reported rather than silently dropped.
Why a message thread is a safe control surface
The confirmations are the product, not the friction.
The same assistant, not a cut-down one
WhatsApp is a channel into the assistant that builds agents, runs campaigns, looks things up and reports back. Nothing is withheld because you happened to arrive by message.
one assistant · email · WhatsApp · Slack · dashboardA code, once, with an expiry
Risky actions stop with a plain-language description and a short code. It is good for one use and expires after a day, so an old message in your history cannot be replayed into an action.
one-use code · 24h expiryEvery tool carries a risk class
Tools are classified as safe, spends money, mass message, destructive, or changes a live deployment — and the classification is enforced in the build, so a new tool cannot arrive unclassified. Only the harmless class runs without asking.
five risk classes · enforced in CIA budget it cannot argue past
A monthly model budget and a daily voice-minute cap sit under everything, with alerts at 50%, 80% and 100%. The cap stops the work rather than telling you afterwards.
monthly budget · daily voice cap · 50/80/100% alertsWhat it did is visible afterwards
Work started from a message lands in the same shared inbox as everything else, so the thread is a convenience rather than a place where things happen unrecorded.
one inbox across every channelQuestions
The things people actually ask.
- Is this a different, smaller assistant?
- No, it is the same one. WhatsApp is another way in to the assistant that is in the dashboard and on email — same capabilities, same confirmations, same memory of what you asked yesterday.
- What stops a mistyped message doing something expensive?
- Anything that spends money, messages a lot of people, or destroys something stops and asks. You get a plain description of what it is about to do and a short code to send back. Nothing happens until you do, the request expires after a day, and a code works once.
- Why would I use this instead of email?
- Because of where you are. Email suits a sentence typed at eleven at night at a desk; WhatsApp suits the one you send standing in a car park between two jobs. Most owners use both.
- Can I see what it did afterwards?
- Yes. Work started from a message shows up in the same shared inbox as everything else — the messages that went out, the replies that came back, the calls that connected.
- Is this the same as putting an agent on my WhatsApp for customers?
- No, and it is worth keeping them separate. That is a customer-facing agent on your business number. This is you talking to Octo. Both exist; they are different jobs.
- What else can I reach it on?
- Email, Slack and the dashboard, with the same confirmations everywhere. Which one you use is a matter of where your hands are.
Keep reading
Related jobs you can hand over.
Delegated work draws on your plan’s included credits, and both a monthly model budget and a daily voice-minute cap apply — so a vague instruction sent one-handed cannot become an open-ended bill.