Skip to main content
Your agent does not only write. In the middle of a conversation it does things: it looks up the price in your catalog, sends a photo, saves the customer’s district, schedules a follow-up for tomorrow, records the sale and, when the time comes, hands the chat to a person. Each of those actions is a tool. This guide lists all of them, says what each one needs in order to work, and shows how they are asked for from the script.
Two different things are called «tool» in this documentation. The ones on this page are the agent’s: the actions it carries out while talking to a customer on WhatsApp. The ones in the Tool reference are the bridge’s: what Claude, ChatGPT or Codex can do to your business if you connect them. They are separate lists and do not mix.

​
Three things worth knowing first

1. There is nothing to «switch on». The tools are available to every agent from day one. The exceptions are the ones that depend on something you have to prepare: a catalog with products, a location with an address, an active app. The table below says so, tool by tool. 2. There are two families, and they are asked for differently. Some are written into the playbook, at the exact point of the script where they must happen («record the sale here», «if they do not reply, remind them tomorrow»). Others the agent uses on its own when the conversation calls for it — looking up a price, sending the location, checking the calendar — and are not named in the playbook: if you write them, the Doctor will flag it. 3. You can see every time one ran. In the chat thread, every action leaves a ⚡ chip with its name and its result, and in Resultados (Results) there is a number that sums them up: Éxito de herramientas (Tool success). More below, in How to know whether it worked.

​
Every tool at a glance

The first column shows the name as it appears in the dashboard.
The voice note is switched off. There is a tool that turns text into audio with the agent’s voice, but today it is disabled for every business. If an old playbook asks to «reply with a voice note», the agent replies with text.

​
How they are written into the playbook

A playbook tool is asked for with one exact sentence, on the line of the script where it must happen. Do not type it: in the playbook editor, type @, choose the Herramientas (Tools) group and click the one you want. If the tool takes data, a one-line form opens to ask for it, and the sentence is written correctly and tinted as a mention: a click changes it, ⌫ deletes it. The sentence left in the text always has this shape (it is in Spanish, because it is what the agent reads):
And two of them go without data, as they are:
Writing it in prose executes nothing. «Record the sale», «schedule a reminder for tomorrow» or «hand it to a human», written without the sentence, are text the agent reads as a suggestion, not an order the system recognises. The same goes for a bare technical name (reminder, register_conversion): the Doctor flags it as «escrita sin formato de herramienta» (written without tool format) and offers to fix it with one click.
Three rules of the form that prevent broken sentences:
  • Reminder, Schedule an action and Notify a third party require the data. Without it, the Insertar (Insert) button stays disabled: a sentence with an empty slot would be of no use.
  • Activate Manual Mode and Consult knowledge take no data. They are not told whom to notify or what: the handoff notifies your team on Slack, if you have it connected, and the agent knows on its own what to look up.
  • The data goes inside the sentence, not next to it. If the Doctor tells you «los argumentos están escritos como prosa al lado de la herramienta» (the arguments are written as prose next to the tool), someone typed the delay or the number by hand outside the quotes; accept the fix it proposes.
Everything that happens around the script — the STEPS, the § sections, the Doctor — is in The sales playbook. Here goes only what concerns each tool.

​
The ones written into the playbook

​
Advance chapter

It is the most important tool in the product, which is why it has its own section in the playbook guide: Making the sales funnel advance. In short: it is inserted with @ → Capítulos, the literal sentence is Llama a la herramienta advance_chapter con el capítulo 3, and writing «move on to the next one» in prose moves nothing.

​
Record a sale / conversion

In the playbook it appears as «Registrar Conversion Tool», and its data is what gets recorded: venta (sale), cita (appointment), lead calificado (qualified lead) or servicio (service).
What it does when it runs:
  • A sale always carries an amount. The agent takes it from the catalog (price times quantity, plus shipping if you charge it). It is what the order is worth, not what has already been collected: a cash-on-delivery sale with no advance is recorded all the same, at the product’s price.
  • On a product sale, it opens the order. With the Órdenes (Orders) app active, that same call creates the conversation’s order with its lines, the agreed payment plan (all upfront, cash on delivery, or advance plus balance), the shipping cost and the address. If the chat already had an open order, it replaces it entirely with the final lines.
  • It does not charge anything. Payment is confirmed when your team verifies the receipt. See Orders and metrics.
  • It notifies you. If in the agent’s Ajustes (Settings) you chose numbers for Ventas (Sales), every recorded sale arrives instantly on WhatsApp with a 💰, with the product, the total and the customer data captured.
Put it in the closing chapter, and only once. It is the source of your sales numbers and of Resultados: if you write it in two chapters, you will count the same sale twice.

​
Activate Manual Mode

In the playbook it appears as «Activar Modo Manual Tool» and is written without data. When it runs, it switches off autopilot for that conversation: the agent stops replying and the conversation waits for a person — just as if you had flipped the switch yourself from the inbox, as described in Taking over the conversation yourself. The agent runs it in three situations:
It is irreversible from the chat. Once off, the agent does not reply again until a person comes in and turns autopilot back on. That is why the agent is forbidden from switching it off «by inertia»: because the history mentions an earlier handoff, because it offered one itself before, or because the customer asks about their data. If the customer says they would rather carry on with the agent, it carries on with the agent.
Every handoff notifies your team through the handoff channel, if you have Slack connected, and stays in the thread as an ⚡ Activar Modo Manual chip.

​
Save a piece of data · Read a customer’s data

In the playbook they appear as «Actualizar Datos Tool» and «Leer Datos Tool»; the data is what to save or what to read:
What it saves goes to the customer’s record, the one you see under «Datos capturados», and merges with what was already there.
It only saves variables that exist. The tool does not create new fields: if the playbook asks it to save «talla» (size) and the record has no «talla» variable, it saves nothing. Create the variable first; and if it is an options variable (a closed list), the agent can only save one of those values.
Read a piece of data exists so as not to repeat questions: if the customer already gave their name in chapter 1, chapter 4 can re-read it instead of asking. Since the agent already receives the customer’s record with every message, you will need it rarely; it is useful when you want to make it explicit in the script that it must use that piece of data.

​
Reminder / follow-up

In the playbook it appears as «Recordatorio Tool» and its data is the delay and what to pick up:
How it works inside, which is what explains its surprises:
  • The text is a note for the agent, not a message for the customer. When the delay is up, the agent writes the message from that note, with the whole context of the chat. And it never tells the customer that it is «creating a reminder».
  • Only one lives per conversation. If the agent schedules another, the previous one is cancelled. That is why a follow-up cadence is chained — each follow-up schedules the next — rather than stacked.
  • If you give no delay, it is 24 hours.
  • It can expire if the customer writes first. For a «re-engagement» of someone who does not answer, it makes sense for it to cancel itself if the customer replies; for a «call me on Monday», it does not. The agent decides from the meaning of the text.
  • It can carry files. If the text contains a ###SEND_FILES: promo### marker, that file is attached on its own when the delay is up, not now.
  • If the conversation switches to manual mode, whatever was scheduled is cancelled when it comes due instead of going out: a person is serving and the agent does not cut across.
Each chat’s reminders are seen and cancelled from the thread, in the reminders panel. And there is one the agent schedules without the playbook asking: when the customer agrees on a day («I’ll let you know on Friday», «I’ll pay on the 15th»), the agent arranges to pick it up that day at 10 in the morning, without insisting before.

​
Schedule an action

In the playbook it appears as «Programar Accion Tool» and its data is the delay and the task:
It resembles the reminder, but it is not the same thing: If the task changes chapter, it can also say from which STEP of that chapter to continue. And just like the reminder, the agent never announces to the customer that it is scheduling something.

​
Notify a third party

In the playbook it appears as «Enviar Mensaje A Tercero Tool». The @ menu form asks you which number and what to tell them, and builds the sentence:
It sends a WhatsApp message from the agent’s number to that other person — the salesperson on duty, the warehouse manager — outside the conversation with the customer. It can attach the chat history.
The number goes with its country code, joined up and without +. 51987654321, not 987654321 or +51 987 654 321. If the playbook carries the number in local format, the tool rejects it and the notice does not go out; and the agent is forbidden from completing or correcting it on its own. What has to be fixed is the number in the playbook. If you keep your numbers under Números frecuentes (Frequent numbers, in Settings), the @ menu offers them to you already well written.

​
Consult knowledge

In the playbook it appears as «Memoria A Largo Plazo Tool» and is written without data. It searches the files the agent studied: the ones that in the Library have the Memoria del agente (Agent memory) permission (policies, warranties, shipping times, spec sheets). See The file Library. You do not need to write it for it to work: the agent uses it on its own whenever the customer asks something that is neither in the chapter nor in its data. And if what it finds does not answer the question, it does not use it: it tells the customer it will confirm and follows the script. Writing it into a chapter serves to force it at a specific point («before answering about warranties, look it up»).

​
Send a file

It is not a sentence but a marker with the file’s nickname, and it has its own section: Send a file from the script.
The essentials: the file has to be in the Library with the «Enviar por WhatsApp» permission before you name it, the default nickname is the file name without its extension, and a badly written marker comes out as it is in the chat.

​
The ones the agent uses on its own

These are not written into the playbook. The agent has them at hand and decides when to call them depending on what the customer asks. If you name them in a chapter, the Doctor flags it; what you can do is prepare what they need.

​
Search the catalog

Every time the customer asks about a product or a price, the agent searches your catalog and answers with the exact price; if the customer said how many units they want, it receives the total already calculated, with quantity pricing and promotions. It is forbidden from inventing prices and from calculating totals on its own. It only exists if your business has active products in the catalog: with no catalog, the agent does not even see it. The same search gives it each variant’s identifier, which is what Record a sale uses to tie the sale to the right product.

​
Send the location

When the customer asks where you are or how to get there, the agent sends the location as a WhatsApp map pin. The addresses and coordinates come from what you saved under Librería → Ubicaciones (Library → Locations); the agent never writes an address of its own, it only chooses which location to send if you have several («the Surco one», «the warehouse»). With no saved locations, it does not have it.

​
Check stock

Before promising units, large quantities or delivery times, the agent checks how much there really is in the inventory, per variant, and does not offer what there is not. It does not use it for prices: that is the catalog’s job. It is the only one with three conditions: the Inventario (Inventory) app active in your business, the «Consultar stock» switch on in that agent’s Ajustes (Settings, under Herramientas, which only appears with Inventory active) and a catalog with products. If one fails, the agent does not see it.

​
Appointments: see the calendar, book, move and cancel

With the Calendario (Calendar) app active, the agent receives four tools at once: check availability (the bookable services and the real free slots), book, reschedule and cancel the customer’s appointment. It is forbidden from proposing a slot without checking first, and the price, the duration and the deposit come from your services, not from its head. If the service carries a deposit, it collects it by receipt and your team confirms it. See The DarkFunnels apps.

​
Notify the team on Slack

If you connected Slack under Personalizar → Canales (Customize → Channels), the agent posts to the channel you chose when it records a sale, detects a hot lead or hands a chat to a person. Without Slack, the tool does not exist and nothing else changes: the WhatsApp notices in Ajustes (Ventas, Alertas, Reportes) are independent.

​
Avatar video

If the agent’s persona has a face and a voice set up, the agent can generate a short video of the avatar saying a text and send it when it is ready; it takes a few minutes and the conversation carries on meanwhile. It is the only one asked for in prose («in the greeting, send them a welcome video») and only if your business warrants it. See The agent’s persona.

​
Your own tools (MCP)

If your business has a system of its own — an ERP, a booking system, a CRM — that exposes an MCP server, you can connect it and your agent will use it as one more tool. It is under Personalizar → Herramientas (Customize → Tools): «Añadir servidor MCP» (Add MCP server), with a name, the server’s URL and, if it asks for one, its key.
1

Connect the server

Personalizar → Herramientas → Añadir servidor MCP. The card shows its status (Activo / Inactivo) and a Con credencial (With credential) label if you saved the key.
2

Write it into the playbook

In the @ menu → Herramientas, the «Otra herramienta» (Other tool) entry is the generic one for anything that comes from an MCP server. Its data is the instruction: what it has to do, naming your system if you have several.
The agent picks, among the tools your server publishes, the one that fulfils that instruction.
3

Try it in a chat

The agent discovers the server’s tools on its own; a freshly added server can take a few minutes to show up for it. Open a test chat from the inbox and look at the ⚡ chip to see whether it ran and what it returned.
What to keep in mind:
  • Limits: up to 5 servers per business and 20 tools in total. Anything beyond that is not loaded.
  • If the server is down, it is skipped. The agent keeps serving without that tool; a conversation never falls over because of someone else’s server.
  • What your server returns is third-party text. The agent treats it as information, not as orders; and no MCP tool can charge or move money, because the agent has no way of doing so.
  • The URL has to be public (https://…). Servers on private networks are not accepted.

​
How to know whether it worked

Every time the agent runs a tool, an ⚡ chip appears in the chat thread with its name — Recordatorio, Conversión registrada, Aviso a tercero… — and, if something went off course, a word next to it: If a chip surprises you, click it: it unfolds with the data the agent passed and what the tool returned. It is the fastest way to understand why it did what it did. The summary of all this lives under Resultados, on the Éxito de herramientas (Tool success) line: of all the actions the agent attempted, how many went well. It is explained in Orders and metrics.

​
From your assistant (optional)

If you connected Claude, ChatGPT or Codex through the bridge, your assistant can read a conversation and see which tools ran in each turn, list and cancel a chat’s reminders, and schedule a new one. It can also write the tools into the playbook for you: ask it to use the exact sentence and to show you the chapter before saving. The tools your assistant has for that are in the Tool reference.
Last modified on September 4, 2026