Your number runs on the WhatsApp Business API, Meta’s official platform, and the agent answers there: it checks price and stock in your management system, builds the quote, sends the payment link and leaves the order and the customer record filed. All of it inside the rules Meta sets for the channel, and with a person one click away.
Official WhatsApp Business API · Victoria AI is a Meta Tech Provider.
Illustrative example with fictional data: it does not correspond to any client.
An AI agent on WhatsApp is a system connected to the official WhatsApp Business API that handles the messages arriving at a company’s number. It does not reply with text written in advance: it queries the systems where the data lives — catalog, prices, stock, customer record, calendar — and executes whatever the case calls for: quoting, charging, booking, filing the order or handing over to a person.
WhatsApp is not an open channel. Meta keeps the conversation open for 24 hours counted from the customer’s last message; outside that window the only thing that goes out is a template approved by Meta. The agent works inside that rule: within the window it writes freely, outside it sends a template, and either way everything is logged in the same customer thread.
Three things that set it apart from a WhatsApp answered by hand
The number runs on the WhatsApp Business API, which is what allows it to be wired to your systems. Multiple numbers and multiple accounts are handled from the same place.
Whatever comes in through WhatsApp lands on the same timeline as Instagram, email or a phone call. The rep sees the whole story, not just the slice from their own channel.
Every action of the agent and every approval is audited next to the conversation: what it checked, what it sent and what is still waiting on a person.
These are not canned replies: each one is an operation against a real system, executed while the conversation is still open.
Price, stock and availability are read from your management system at the moment of replying, not from a list uploaded last week.
It creates, moves and cancels appointments on the team calendar, or sends the link so the customer picks a slot without any back and forth.
Quick reply buttons, lists of up to ten options, products from the Meta Commerce catalog, a location on the map and voice notes.
The agent also picks up voice calls inside WhatsApp, and the call stays in the thread with its duration, its summary and its transcript.
When the request goes beyond its scope or a piece of data is missing, it does not improvise: it alerts the lead owner and leaves them the full conversation.
Which functions stay active in your account depends on the plan, the industry and the integrations you contract.
See the omnichannel inboxIt is the rule that surprises people the most when automating WhatsApp, and the one that decides what can be sent at any given moment. The system tracks it and shows it on screen, instead of letting someone find out through a rejected message.
The agent and the rep reply with free text, files, audio, buttons and lists. The indicator shows how much time is left and refreshes as soon as a new message from the customer arrives.
Free text is blocked before anyone can send it and the approved-template picker opens: it is the only format Meta accepts outside the window. This is not a CRM restriction.
The reply opens the window again and the conversation picks up where it was, in the same thread and with the history in view. Nothing starts from scratch.
It is the message Meta authorises you to send outside the window. Meta does not write it: you write it and Meta approves it.
You write it, Meta approves it — It is created in the CRM and submitted for approval from there. Until Meta approves it, it cannot be used.
The variables come from the CRM — Each placeholder is mapped to a lead field: the name, the quote number, the date. The message goes out with the data that belongs to that person.
The same template, across several numbers — It is created on several WhatsApp numbers at once, or copied from one number to another without rewriting it.
Source
The 24-hour window and template approval are Meta’s rules, not Victoria’s.
Official WhatsApp Business Platform documentationTen moves between the message coming in and the order being filed. None of them is a canned reply: each one touches the channel, the CRM or your management system, and the label on every step says which.
ChannelAgentCRMManagement systemAction
The customer writes to the company number the way they talk: a long text, a photo of the product or a voice note, which is transcribed before the agent reads it.
Before replying it identifies the intent and picks the tool that resolves it. If a piece of data is missing to run that tool, it asks instead of guessing.
The number is matched against your customer base. If it is already there, the conversation is tied to that record; if it is the first time, the lead is created on the spot with the chat inside.
It sees what happened before: past purchases, open opportunities, the custom fields your company defined and where that customer came from.
It searches your catalog with the words the customer used and, when there are similar variants, it asks which one instead of picking for them.
It reads them at the moment of replying and checks availability again before confirming a purchase. If the query does not return the data, it says so.
It calculates the order total and issues the quote as a PDF —customer details, discounts, tax broken out— inside the same conversation.
If the customer asks for time, a follow-up is scheduled for the date they asked for, quoting their exact words. It does not depend on anyone remembering.
When the customer confirms, the sale is closed and the manager is notified to prepare it. After that the agent answers about its status, modifies it or cancels it.
When someone on the team opens the chat there are no messages to read and re-enter by hand: the work is done, and every move is signed by whoever made it.
The full circuit only runs when the functions behind it are enabled: with no catalog connected there is no step 5, and with no quoting there is no step 7.
See how your management system connectsFive steps of an ordinary conversation at a building supplies store. Each one is something the agent does today: the only fictional parts are the names and the numbers.
"Can you quote me 20 bags of hydrated lime?" The agent recognises the number, opens the customer record and sees they have bought twice before.
It reads price and stock from the management system, sends the quote as a PDF and leaves the opportunity filed in the pipeline with its owner.
"I’ll check with my partner and let you know." The agent schedules the follow-up quoting that exact sentence, and the conversation ends there.
More than 24 hours have passed since the customer’s last message: free text is blocked and the send is resolved with an approved template.
The message goes out with the customer name and the quote number taken from the CRM. If they reply, the window opens again and the agent picks up where it left off.
Illustrative example with fictional data: it does not correspond to any client.
See the agent’s scheduled tasksBoth are sold with the same words and they do not do the same thing. Here they are side by side, category by category, so the difference shows without adjectives.
| The category | Fixed-flow chatbot | Connected agent |
|---|---|---|
| How it understands the message | Keywords and numbered options. If the customer words it differently, the flow loses track and goes back to the menu. | Natural language, and the voice note is transcribed before it replies. The customer writes the way they talk. |
| Where price and stock come from | From a list loaded by hand, which someone on the team has to keep up to date. | From the management system, read at the moment of replying and checked again before confirming the purchase. |
| How far it goes | It collects the details and leaves the message for a person to pick up. | It quotes, sends the payment link, books and files the order without leaving the conversation. |
| Outside the 24 hours | Meta's rule is the same for everyone. With no window tracking, the send is discovered rejected after it went out. | The system tracks the window, blocks free text before the send and opens the approved templates. |
| When a person is needed | It hands the chat over and the person rebuilds the context by reading the conversation. | It alerts the lead owner with the whole case and stays muted in that chat until it is enabled again. |
| Several numbers and accounts | One flow per number, maintained separately from the rest. | The same agent across several numbers and accounts, each with its own window and its own templates. |
The table compares categories of technology, not named products: both approaches exist and can be bought today.
See what an AI agent isWhat is left is not a message log for someone to read and type up: it is the transaction filed in the CRM, with every move signed by whoever made it.
The name, the contact details, the tags from your CRM catalog and the custom fields your company defined —text, number, date, list, yes/no— filled in with what the customer said.
If the sale closed, the order is filed and the manager is notified to prepare it. If the customer asks later, the agent answers about that order.
Scheduled for the date the customer asked for and quoting their exact words, so whoever picks it up knows why they are writing that day.
Every move in the history says whether it was the AI, an automated workflow, a broadcast or a person by name. There are no anonymous events.
None of this is a summary written at the end: they are the same records the rest of the CRM uses, created while the conversation was happening.
Victoria CRM, where all of this ends up filedThe full autonomy table is the same on every channel and lives on the AI agents page. What changes on WhatsApp is the TIMING: replying inside the window is not the same as starting a conversation outside it.
Inside the window it replies with free text; outside it, the only thing it can start is an approved template.
A rep can take over the chat at any time: the AI stays muted in that conversation until it is enabled again.
Every agent action and every approval is audited inside the platform.
See the full autonomy tableSome of these are Meta rules and some are Victoria limits. Both are better known before signing than after the first campaign.
Once 24 hours have passed since the customer’s last message, the only thing Meta accepts is an approved template. There is no way around it, and the system does not pretend otherwise: it blocks the send first.
They are written and submitted from the CRM, but the decision and the timing are Meta’s. A rejected template is corrected and submitted again.
Recipients of a broadcast must have agreed to receive it. That is what protects your company’s WhatsApp account, and the system reminds you of it on every send.
What can be sent, in which formats and from which number is defined by your WhatsApp Business account settings. It is reviewed during discovery, before anything is promised.
The integrated providers are Mercado Pago, Payway and Rebill. If your company charges through a different one, that is custom development, with its own timeline and validation.
Before it handles a single customer there is discovery, a connection to your systems and training: seven stages, between one and three weeks. There is no instant activation.
If your management system is not connected yet, the connector is developed within the onboarding fee.
See the available integrationsIn a 30-minute meeting we review which systems you have, connect a test number and you watch a real WhatsApp message land in the customer thread.
Official WhatsApp Business API · Victoria AI is a Meta Tech Provider.
