Commands you can send from WhatsApp

If someone has added you to the Command Center roster, you can message your business’s own WhatsApp number — the same one customers use — and get straight answers back. This page is the reference for what you can ask.

The companion page, Command Center, is for whoever sets this up: the roster, roles, security flags and history. This one is for you, the person typing.

Two things are worth knowing before the list.

You never have to remember exact wording. Ask in your own words and your assistant works out which command you meant. The keywords below are a shortcut, not a syntax — today is faster to thumb-type than “how did we do today”, and both work.

Anything that changes data asks you first. Reads come straight back. Writes show you what they are about to do and wait for a yes. Nothing is written on the strength of one message.

Send help to see your own list

Your assistant replies with the commands you can use, which may be fewer than the ones on this page — see Why your list may be shorter below. The reply also carries up to three tappable buttons for the most common questions.

Tapping a button and typing its word do the same thing.

Asking for numbers

These seven never change anything, so they answer immediately.

Ask for	Shortcut	What comes back
Today’s activity	today	Calls, completed calls, minutes, new leads and spend, for today
A longer stretch	week	The same figures over a range, split by day and by assistant
The state of the board	pipeline	One line per stage — how many deals sit there and what they are worth
Where one customer stands	customer Ramesh	Their channels, how many deals, up to five of them with stage, and what your assistant remembers
What is overdue	overdue	Everything owed and not done across the business, soonest-overdue first
What is scheduled for someone	followup Ramesh	What your assistant has planned next for that customer’s open deal
A price or availability	price of deep clean	The catalogue answer, phrased for staff rather than customers

A few details that save a round trip:

• Names or numbers both work. customer Ramesh and customer 9876543210 find the same person. If more than one customer matches, your assistant lists them and asks which — it never guesses.
• overdue is the whole business, not only your own work. It is capped, and tells you when there is more.
• week accepts a period in words — today, yesterday, this week, last week, this month, last month. Ask for a period in words rather than dates; your assistant does not know today’s date and will not guess one.
• pipeline deliberately does not report what you won this week. Ask for week for that.

Making a change

Three commands change something. All of them show you the change and wait.

Dictate a note. Type or say it:

note Ramesh: wants delivery by Friday, seemed hot

Your assistant reads it back before saving anything:

Save a note on Ramesh: “wants delivery by Friday” and mark them hot — reply yes or no.

Reply yes and it saves. What it does, precisely:

• The note lands on that customer’s newest open deal. If they have no open deal, it saves against the customer instead and tells you so.
• Saying hot, warm or cold also marks the deal. Without an open deal there is nothing to mark, and your assistant says that rather than dropping it quietly.
• If the customer is new to your records, nothing is written — your assistant cannot save a note about someone it has never heard of.

⚠️ A note is for your team, not for your assistant. It is stored on the deal and shown in the dashboard, and it is not fed into what your assistant says to customers. To change how your assistant talks, use the instructions in your bot’s settings instead.

Log a call you just had — and turn what you promised into a reminder.

This is the one to use after you put the phone down. Say what happened and what you promised, and both are saved from one message:

logcall Priya: wants a quote for the balcony grill, I said I'd send it
Wednesday at 9. She's serious, mark her hot.

I will save this on Priya:

• “wants a quote for the balcony grill”*
• mark them hot*
• remind you Wed 20 Aug, 9:00 am — send the balcony grill quote* — reply yes or no.

Reply yes and three things happen together: the note is saved on Priya’s open deal, her deal is marked hot, and a reminder for you goes on the board for Wednesday morning. If Priya has no open deal, one is opened for her.

The reminder time you see is the real date and time, worked out in your own time zone, not the words you said — so you can catch a misunderstanding before anything is saved. Reply no and nothing at all is written.

What to expect:

What happens	Why
You promise something with no date — “I said I’d send a quote”	The note is saved and no reminder is set. Your assistant tells you so and asks for a time. Say “by Friday at 3pm” or “tomorrow at 11” and send it again. A reminder on a day you did not choose is worse than none.
You log a second promise for the same customer	The new reminder replaces the old one, and the reply names the date it replaced. You are never left with two.
You log a call with no promise at all	Just the note and the temperature. That is fine, and it is not an error.
Your assistant cannot tell which customer you mean	Nothing is written. It lists the matches and asks.

⚠️ A reminder only reaches your inbox if follow-up notifications are switched on. Otherwise it appears as a card on your pipeline board and nothing is emailed to anyone — which looks exactly like a reminder that never fired. Your assistant warns you about this on the confirmation, every time, so you find out before you rely on it. Whoever administers your account can turn notifications on under pipeline settings.

While your reminder is open, your assistant holds off following up with that customer itself. You told it you are handling this one personally, so it stops chasing until your reminder is dealt with.

Call off a planned follow-up.

cancel the task for Ramesh

Cancel the assistant’s planned actions for Ramesh — reply yes or no.

This cancels everything still pending on that customer’s open deal. Anything already under way cannot be pulled back, and your assistant tells you when that happened rather than pretending it stopped.

The shortcut word is canceltask, not cancel — on its own, cancel means “drop what we were just doing”.

Saying yes, saying no

While something is waiting on you:

You send	What happens
yes, or the Yes button	It runs, and you get the result
no, the No button, or cancel	Nothing is done — Cancelled — nothing was done.
Anything else	The pending change is dropped and your new message is treated as a fresh request

Three things follow from that, and they are all deliberate:

• A qualified reply is not a yes. yes runs it. “yes but make it Tuesday” does not — that is a new instruction, so your assistant starts again rather than saving the original wording and silently ignoring your correction.
• You have 15 minutes. After that: That confirmation has expired — nothing was done. Send the command again if you still want it. The wait is deliberately long enough to answer a customer mid-conversation and come back.
• Two people cannot both approve the same thing. If a second yes arrives after the first has run, it is told That was already handled — nothing more was done.

Sending a voice note

Every command works dictated. Record a voice note instead of typing and your assistant transcribes it, then treats it as though you had typed it — confirmation step included. Dictating a note after a customer meeting is what this was built for.

If the audio cannot be made out, you get no reply rather than a guess.

Why your list may be shorter

Two people on the same roster can see different commands.

Your role. Whoever set this up gave you a role, and roles carry different access. Out of the box there are two — Manager and Human Agent — and by default week and pipeline are manager-only, because business-wide revenue is not usually every agent’s to see.

Your business’s own settings. Roles are configurable, and custom ones can be added. If a command has been taken away from your role, it stops being offered rather than failing when you try it.

If you ask for something outside your access, your assistant says You do not have access to that one. — ask whoever manages your roster.

When something does not work

What you see	What it means
Too many commands at once — give it a minute and try again.	More than ten commands in a minute, counted per person. Wait a minute.
That is not something I can do. followed by your list	Your assistant could not match your message to any command. The list follows so you can pick one.
That option has expired. Here is what you can ask for now:	You tapped a button from an older message. Use the fresh list underneath.
There is nothing pending for that to answer.	A yes or no arrived with nothing waiting on it.
I could not pull that just now. Please try again in a minute.	A temporary fault. Nothing was changed.
which customer? give me a name or a phone number	The command needs to know who. Send it again with a name or number.
An ordinary customer-style reply	See below — this is the important one.

⚠️ If your assistant answers you like a customer, you are not on the roster. There is no error message for this, by design: your business number is a customer-facing number, and announcing “you are not authorised” to whoever messages it would tell an outsider that a staff entrance exists. The same thing happens if your number was removed, if your dashboard login was deactivated, or if Command Center was switched off. Ask whoever manages your roster to check.

Teaching your assistant something new

remember: adds something to your knowledge base — a price, a policy, an opening hour.

remember: delivery is free on orders above 2,000 rupees

Your assistant reads it back and waits for a yes, the same as any other command that writes something.

Then it waits again. What you add does not answer customers until a manager approves it. Your reply says so: it names a short reference and tells you the assistant will not use the fact yet. Nothing about this is a fault — a wrong fact in your knowledge base gets repeated confidently to every customer who asks, so a second person sees it first.

If a manager sends pending, they get the list of what is waiting, each entry tappable. Tapping one, or sending approve with its reference, releases it. discard throws it away. Both ask for a yes first, because approving is the moment your customers start hearing it.

Anyone on the roster can add a fact. Only a manager can approve one. A manager can approve their own, so a one-manager business is not stuck.

⚠️ If your team has added facts and your assistant still does not know them, they are waiting for approval. Send pending to see them. Nothing is lost, and nothing is live.

The queue can also be cleared from the dashboard, which is the answer when your manager is away.

Everything you send and everything that comes back is recorded in the History tab for whoever administers your account.

What is not here yet

Asking your assistant to call a customer back at a time you name is built but not yet switched on — outbound calling has not been verified on a live account. This page will cover it once it is. Until then, schedule callbacks from the dashboard.