— Capabilities
Three capabilities. One WhatsApp number per client.
Each tenant you run gets an agent that takes orders against a catalog, answers from that client's own documents, and books appointments — on the number their customers already write to.
How the agent is actually used
1. A message arrives
A customer writes — or sends a voice note — to the client's WhatsApp number, the same way they always have.
2. It resolves against the tenant's data
Catalog, price lists, documents, availability — the agent answers from that tenant's own records, never from a generic script.
3. You see it in the console
Every resolution lands in the operator console. When the agent is not sure, it escalates — and a person steps in.
- Crema de leche 200ml x12 · 2 u.$18.400
- Yerba mate 1kg · 1 u.$14.550
- “la crema chica” — 2 candidate matchesClarify
→ Crema de leche 200ml x12 · or · Crema de leche 500ml x6
— Orders
The message is the order form.
Text or voice note, the agent captures the order line by line and resolves each line against that client's catalog and price list — per client, per zone. Clean lines confirm themselves; ambiguous ones are clarified back inside the chat or handed to a person. The finished order exports to your own systems.
Before: 2 hours · After: 2 minutes
See the order engineCustomer asked
“¿Hacen envíos a zona Sur los sábados?”
Agent answered
Sí — los sábados se despacha a zona Sur con pedido confirmado antes de las 11:00.
Source: logistica-y-envios.pdf · p. 2
No match in the document base
“No tengo ese dato en los documentos cargados. Te derivo con una persona.”
Refusal — nothing invented
— Knowledge
Answers from their documents. Or an honest “I don't know”.
Each tenant uploads its own documents — price sheets, policies, catalogues, FAQs. The agent answers strictly from that base and cites the source of every answer. When nothing matches, it says so and hands off, instead of inventing. That refusal is the feature: a wrong answer costs your client a customer.
Before: a forwarded PDF and a phone call · After: the answer in the chat, with its source
Read the knowledge docs— Scheduling
Bookings taken inside the conversation.
Each tenant sets its own availability. The agent offers open slots, books the one the customer picks, confirms it in the chat and sends the reminder — no link, no form, no app to install.
Before: three messages to agree a time · After: booked in one exchange
Read the scheduling docsAround the three, the machinery that makes them operable
Provider-agnostic transport
Meta Cloud API, 360dialog or Twilio — the agent behaves the same whichever provider carries the messages.
Per-organization credentials
Each tenant's WhatsApp and model credentials are held per organization, encrypted — never one shared config.
Human-handoff queue
Ambiguous order lines and unresolved questions land in one review queue, with the conversation attached.
Audit of agent actions
Every resolution, refusal and handoff is logged — you can reconstruct what the agent did and why.