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 them, says what each one needs in order to work and shows how they are asked for from the playbook.
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 on your business if you connect them. They are separate lists and do not mix.

​
Three things worth knowing first

1. Almost all of them come ready. They are available to every agent from day one. The rest depend on something you prepare: a catalog with products, a saved location, an active app, Slack connected or a switch in the funnel’s Configuración (Settings). 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 their technical name in a chapter, the Doctor asks you to delete it. 3. You can see every time one ran. In the chat thread, each action leaves a chip with a lightning bolt (⚡), the tool’s name and how it ended. In Resultados (Results) there is a number that sums it up: Éxito de herramientas (Tool success). More below, in How to know whether it worked.

​
Every tool at a glance

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. If an old playbook asks to «reply with a voice note», the agent replies with text. The audio files you upload to the Library are sent, like any other file.

​
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. You do not need to type it: in the Playbook editor, type @ and choose an entry from the Herramientas (Tools) group. There are ten: Recordatorio / seguimiento, Programar una acción, Registrar un referido, Avisar a un tercero, Consultar conocimiento (RAG), Leer un dato del cliente, Guardar un dato, Activar Modo Manual, Registrar una venta / conversión and Otra herramienta.
The playbook editor's @ menu with the search box and the Herramientas (Tools) group: in view, from Recordatorio / seguimiento (Reminder / follow-up) to Activar Modo Manual (Activate Manual Mode); the rest further down the list

In the @ menu, the Herramientas (Tools) group gathers the ones that are written into the playbook.

If the tool takes data, a short form opens to ask for it. Press Insertar (Insert) and the sentence is written correctly and tinted like a mention. A click on a tool already written lets you change it: if it takes data, its form opens with the data inside (change them and press Guardar — Save), and in every case you have ✕ Quitar mención (✕ Remove mention) to delete it. The sentence left in the text has this shape (in Spanish, as the editor writes it):
And two of them go without data, as they are:
Written in prose, it is not a tool. «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: the editor does not recognise them and the Doctor cannot check them. The same goes if someone wrote a tool’s technical name on its own: the Doctor flags it with «… está escrita sin formato de herramienta» (… is written without tool format) and, if there is an equivalent, offers to fix it with one click.
Three rules of the form that prevent broken sentences:
  • Reminder, Schedule an action, Register a referral and Notify a third party require the data. Without it, the Insertar button stays disabled: a sentence with an empty slot would be of no use. In Notify a third party, also fill in A quién (To whom): with no destination, the agent does not know whom to notify.
  • Activate Manual Mode and Consult knowledge take no data. The handoff notifies on Slack, if you connected it (more below, in Activate Manual Mode), and the agent decides on its own what to look up.
  • The data goes inside the sentence, not next to it. If the Doctor tells you that a tool «tiene sus parámetros sueltos» (has its parameters loose), someone typed the delay or the destination by hand outside the quotes; accept the fix it proposes.
Everything that happens around the script — the PASOS (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 conversation advance. In short: it is inserted with @ → Capítulos (Chapters) and the literal sentence is Llama a la herramienta advance_chapter con el capítulo 3. Writing «move on to the next one» in prose is not the way to do it: the advance lives in that line.

​
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 is not recorded without an amount. The agent takes it from the catalog (price per 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 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 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 funnel’s settings, under Informar de las ventas (Report sales), you chose whom to notify, every sale arrives instantly on WhatsApp with a 💰: the product, the total and the customer data the agent captured. It notifies sales and services; appointments and leads, no. If you connected Slack, it also goes to the channel you chose for Conversión (Conversion).
  • It does not count the same sale twice. If within the following 24 hours the agent records a sale again in the same chat, the system takes it as the same one: it does not add another sale or notify you again. If that chat’s order is still Por cobrar (Awaiting payment) or in Pago parcial (Partial payment), it rewrites it with the new lines; if it was already Pagado (Paid) or further along, a separate order is opened. After 24 hours, a sale in that chat does count as another purchase.
Put it once, in the closing chapter. It is the source of your sales numbers and of Resultados. If you repeat it in chapters that are reached days later (a follow-up, an after-sale), a conversation that comes back can add a second sale.

​
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 switched it off yourself from the inbox, as described in Taking over the conversation yourself. The agent uses it in these situations:
Switching it off leaves the customer without replies from the agent. From that moment on, that conversation waits for a person: autopilot is switched back on from the dashboard or, from the phone of that line, by repeating the first word of the message («ok ok…»), as described in Taking over the conversation yourself. That is why the agent is ordered not to switch 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.
Each handoff notifies on Slack, in the channel you chose for Te toca atender (Your turn to serve), if you have it connected, and stays in the thread as an Activar Modo Manual chip. Without Slack, the handoff does not notify your team at that moment: the conversation stays in your inbox with the Manual mark. If you want your team to find out on WhatsApp, write a Notify a third party in the same STEP, before the handoff (for example, to «Equipo de ventas»). While the conversation is in manual mode, reminders and scheduled actions that come due are cancelled instead of going out.

​
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» (Captured data), and is added to 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, in Clientes (Customers, Tabla view — Table). From the @ menu you can start it with ＋ Crear variable (＋ Create variable), but it stays as a draft until you create it in Clientes. And if it is an options variable (a closed list), the agent will only be able to 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 for it. 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 when and what. It is written in two ways, depending on who supplies the words. A note for the agent, which is the normal case. When the delay is up, the agent writes the message from that note, with the whole context of the chat, without telling the customer there was a reminder. If by then there is nothing useful left to say, it may send nothing:
An exact text for the customer. If after the delay you write «dile exactamente esto:» (tell them exactly this:) (or «dile esto:», or «dile al cliente:») followed by the text, when it comes due it is sent as is, word for word, without the AI rewriting it:
Three things worth knowing about the exact text:
  • It carries a colon. «dile al cliente que confirme la fecha» (tell the customer to confirm the date) is an instruction for the agent; «dile al cliente: ¿confirmamos la fecha?» (tell the customer: shall we confirm the date?) is an exact text.
  • It goes out with nothing added. No greeting is added to it: if you want a «hola», write it yourself.
  • If, when it comes due, there is a customer message still unanswered, the agent answers it normally instead of sending the text.
And for both cases:
  • The agent keeps a single reminder of its own per conversation. When it schedules another, the previous one it had scheduled is cancelled. That is why a follow-up cadence is chained — each follow-up schedules the next — rather than stacked. The reminders you schedule yourself from the chat’s record are not touched.
  • If you give no delay, it is scheduled for 24 hours by default.
  • It can be cancelled if the customer writes first. For a «re-engagement» of someone who does not answer, that makes sense; for a «call me on Monday», it does not. The agent decides from the meaning of the text.
  • It can carry files. In the form, type @ inside the text and choose a file from the Library: a marker is left at that point of the message and the file is attached when it comes due, not now. Up to 4 per reminder.
  • It respects your «No molestar» (Do not disturb) window. If it comes due inside the window you set in Configuración (from the factory, from midnight to 6 in the morning, in the funnel’s time), it waits for the window to end and goes out within the following hour.
  • If more than 8 hours have passed since the agent’s last message, it greets first (only in the note case). A reminder that comes due the next morning opens with a «good morning» and only then picks up where it left off.
  • If the conversation is in manual mode when it comes due, it is cancelled instead of going out: a person is serving and the agent does not cut across.
  • If your WhatsApp is disconnected when it comes due, it waits. It is retried and goes out if the line comes back in less than 6 hours; if not, it expires.
There is one reminder the agent schedules without the playbook asking for it: when the customer agrees on a day («I’ll pay you by Yape on Monday», «I’ll pay on the 15th», «I’ll confirm at 6»). It is set for that day, at the time the customer said or, if they did not say a time, at 10 in the morning, in the funnel’s time zone. A day of the week means the next one: if today is Monday and they say «on Monday», it is next week’s. That reminder replaces the follow-ups and actions the agent had scheduled in that chat, and the agent is ordered to leave it standing even if the customer writes first. If the agent later schedules another reminder, that one replaces it, as happens with any reminder of its own. Each chat’s reminders are seen in the conversation, on the Ficha (Record) tab, sections Recordatorios (Reminders) and Acciones programadas (Scheduled actions), each one with its time and a Cancelar (Cancel) button.

​
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. With no delay, it is also 24 hours. And like the reminder, it respects the «No molestar» window, it is cancelled if the conversation is in manual mode when it comes due, and the agent does not announce to the customer that it is scheduling something.

​
Register a referral

In the playbook it appears as «Registrar Referido Tool» and its data is whom the customer recommends to you: the name, their WhatsApp with its country code and whatever context the customer gives (where they live, what they do). The agent calls it once per person the customer shares, whether as a WhatsApp contact card or by typing the number:
What happens next is up to you, in Red de referidos → Programa (Referral network → Program), under «¿Quién escribe primero?» (Who writes first?):
  • El cliente lo presenta (The customer introduces them, the factory setting): the agent gives your customer, in that same chat and in a separate message, an introduction ready to forward, with your funnel’s WhatsApp number as text (if that number is not saved for your line, the introduction goes out without it and the agent asks your customer to pass it on to their acquaintance). The referred person writes to you themselves: your number does not write to the referred person first.
  • El agente le escribe primero (The agent writes first): your WhatsApp sends the referred person a single message, during the day (from 8:00 to 20:00 in the funnel’s time and outside your «No molestar» window), with a cap on referrals per day to look after your number.
The introduction text, the attachments, the chapter the referred person enters through, the rewards and the automatic notices are configured in The referral network. The referred person’s record gets Referido por (Referred by), with the name of whoever recommended them, and, if the customer said something about that person, Contexto del referido (Referral context). Rules the agent already knows:
  • Someone who already wrote to this funnel does not count. If that number already talked with your funnel, the agent tells the customer kindly and records nothing.
  • If the same customer passes you again someone they already recommended, that person still counts for them.
  • The first one wins. If another customer had already recommended that number, the new registration does not count. The exception: if in Programa you set «Un referido vale (días)» (A referral is valid for (days)), that period passed without a deposit and that person has not written to you yet, the recommendation passes to the new customer and Referidos marks it «Pasó a otro cliente» (Passed to another customer).
  • Nobody recommends themselves, and the agent does not invent or complete numbers: if one arrives without a country code, it asks the customer for it.
When registering a referral, the agent is ordered not to talk about rewards. What the customer is told about money is down to the notices in Red de referidos → Avisos (Notices), such as «Cuando su referido da el adelanto» (When their referral pays the deposit) or «Cuando le pagas» (When you pay them), which you switch on, switch off and write. In «El cliente lo presenta» mode, two more also come switched on from the factory: «Si su conocido no escribe» (If their acquaintance does not write: after 3 days it asks your customer whether they managed to forward the introduction) and «Cuando su conocido escribe» (When their acquaintance writes: it thanks them for the recommendation). And if the customer asks how their referrals are doing, the agent answers with their real figures: see Tell them how their referrals are doing.

​
Notify a third party

In the playbook it appears as «Enviar Mensaje A Tercero Tool». It sends a WhatsApp message from the funnel’s number to another person — your sales team, the warehouse manager — outside the conversation with the customer. The @ menu form asks you for two things:
  • A quién (To whom). Press ＋ or type @ in that field and choose from the list: Equipo de ventas (your Informar de las ventas list) or one of your Números frecuentes, which show up as «name · number». You can choose several. Writing a number with its country code also works.
  • Qué avisar (What to say). The notice itself: «the customer wants an appointment», «there is a new order to coordinate the delivery».
Avisar a un tercero (Notify a third party) form with the empty A quién (To whom) field and its ＋ button, the note Para avisar a otras personas por su nombre, guárdalas en Ajustes → Números frecuentes (To notify other people by name, save them in Settings → Frequent numbers), the notice el cliente quiere comprar al por mayor (the customer wants to buy wholesale) and the Volver (Back) and Insertar (Insert) buttons

The «Avisar a un tercero» (Notify a third party) form, with «A quién» (To whom) still empty: there you press ＋ or type @ to choose from the list, or write a number.

When you choose a contact, the sentence keeps their name in «» quotes, not their number:
You can mix several destinations («Dile a «Equipo de ventas» y «Almacén» que…»): nobody receives the same notice twice. And a bare number still works:
Better by name than by number. The number lives in the funnel’s settings, not in the playbook text: if you change salesperson, you change it there and the playbook is not touched. If in Números frecuentes you rename a contact that a notice names, without changing its number, the notice in the playbook renames itself (a new version is left in the Historial — History). And if you remove from the list a contact the playbook uses, when you press Guardar cambios (Save changes) the Configuración is not saved and it warns you: change it in the playbook first.
Configuración (Settings) screen with the Informar de las ventas (Report sales) and Números de prueba (Test numbers) sections, with no numbers set, each with the Elegir de mis números frecuentes… (Choose from my frequent numbers…) selector, and the start of Reportes (Reports)

In Configuración (Settings), «Informar de las ventas» (Report sales) is the list the notices call «Equipo de ventas» (Sales team); it is filled from «Elegir de mis números frecuentes…» (Choose from my frequent numbers…), here still empty.

What reaches that person: the notice, with the customer’s WhatsApp at the end so they can write to them. If the playbook asks for it, the agent can also attach the conversation with the customer.
A destination that cannot be found receives nothing. If the playbook names someone who is not in your Números frecuentes (or who has no number), the notice does not go out and the Doctor flags it as an error: «El aviso a «…» no sale: no está en tus Números frecuentes o le falta el número» (The notice to «…» does not go out: they are not in your Frequent numbers or their number is missing) (the Doctor and some dashboard notices call the Configuración «Ajustes»). If it names «Equipo de ventas» and your Informar de las ventas list is empty, the notice does not go out either, and there the Doctor does not warn you: check that list in the Configuración.A bare 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 ordered not to complete or correct it on its own. What has to be fixed is the playbook: the Doctor flags it too.

​
Consult knowledge

In the playbook it appears as «Memoria A Largo Plazo Tool» and is written without data. It searches what the agent studied:
  • the files that in the Library have the Memoria del agente permission (policies, warranties, shipping times, spec sheets; see The file Library), and
  • the Memoria a Largo Plazo (Long-Term Memory) document you write from the Playbook itself, if your funnel has that button (how it is written).
If that text uses a piece of business data (for example {{dato:yape}}), the agent receives the value you have saved under Configuración → Datos del negocio (Settings → Business details). You do not need to write it for it to work: the agent is ordered to use it on its own when 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 is ordered not to 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: Sending 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, and the default nickname is the file name without its extension. If the marker is missing a #, that text may reach the customer’s chat as is; if the nickname is not that of a file the agent can send, the marker disappears and the message goes out without the attachment.

​
The ones the agent uses on its own

These are not written into the playbook with the tool sentence. The agent has them at hand and decides when to call them depending on what the customer asks. The exception is the avatar video: the agent is ordered to send it only if the playbook asks for it in prose. If you write their technical name in a chapter, the Doctor asks you to delete 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 ordered not to invent prices or calculate totals on its own. If your business has no active products in the catalog, the agent does not receive this tool. 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 your premises as a WhatsApp map pin. The address and the point on the map come from what you saved under Librería → Ubicaciones for that funnel: the agent only chooses which premises to send if you have several («the Surco one», «the warehouse»), and if it does not recognise which one, it sends the first. One pin goes per reply.
The Library's Ubicaciones (Locations) tab, empty (Aún no hay ubicaciones — No locations yet), with the Nombre, Dirección, Cuándo enviarla, Coordenadas and Acciones (Name, Address, When to send it, Coordinates and Actions) columns and the Agregar ubicación (Add location) button

The premises the agent sends are saved on the Library's Ubicaciones (Locations) tab; here, still empty.

With no locations saved for that funnel, there is no pin to send.

​
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 to give prices: that is the catalog’s job. It needs three things: the Inventario app active in your business, the «Consultar stock (Inventario)» (Check stock (Inventory)) switch on in that funnel’s Configuración (Herramientas section — Tools — which only appears with Inventario active) and a catalog with products. If one fails, the agent does not receive it.

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

With the Calendario 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 ordered not to propose 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 payment receipt and your team confirms it. See The DarkFunnels apps. For it to really book, load into the Calendario, in that funnel’s calendar, your services and your opening hours: without them the agent does not offer appointments and tells the customer that someone in charge will coordinate the time.

​
Tell them how their referrals are doing

When a customer asks about their recommendations or their rewards («how are my referrals doing?», «have I been paid yet?»), the agent checks their real status and answers in its own words: whom they recommended and whether that person has already written to you or left their deposit, how many people there are in their network (in figures only, without names), how much they earned, how much they were paid and how much is still owed. It does not promise payment dates. If they have not recommended anyone yet, it tells them so and invites them to pass you a contact.

​
Note that they do not want to refer

If the agent asked the customer for referrals and they say no clearly («I don’t know anyone», «no, thanks»), the agent notes it down. From that moment on, the referral reminder and the automatic requests from Red de referidos → Avisos no longer reach them. An «I’ll think about it» or «I’ll pass it on later» does not count as a no.

​
Notify the team on Slack

If you connected Slack under Personalizar → Canales, the agent posts to the channel you chose for each notice: Conversión (Conversion: when it records a conversion), Te toca atender (Your turn to serve: when it hands over a chat or a piece of information from the playbook is missing) and Lead caliente (Hot lead). Without Slack connected, the agent does not notify there and everything else stays the same: the WhatsApp notices in Configuración (Informar de las ventas, Reportes, Alertas de error) go their own way.

​
Avatar video

If the agent’s persona has a face with 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. Each video spends balance, unless you use your own key for the video provider (see Credits and top-ups). The agent is ordered to do it only if the playbook asks for it expressly, and it is asked for in prose («in the greeting, send them a welcome video»). It does not repeat an identical video in the same conversation. 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: «Añadir servidor MCP» (Add MCP server), with a name, the server’s URL and, if it asks for one, its key.
Herramientas (Tools) tab of Personalizar (Customize), still with no servers (Aún no hay herramientas MCP — No MCP tools yet), with the Añadir servidor MCP (Add MCP server) button

Under Personalizar → Herramientas (Customize → Tools), «Añadir servidor MCP» (Add MCP server) opens the form to connect your server.

1

Connect the server

Personalizar → Herramientas → Añadir servidor MCP. Write the name, the URL and, if your server asks for it, the API key (opcional) (API key (optional)), and press Guardar. The card shows its status (Activo / Inactivo — Active / Inactive) 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 everything 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

Test it

The agent discovers the server’s tools on its own; a freshly added one can take a few minutes to show up for it. Test it with Probar (Test) in the Playbook: under each reply you see which tools it used. In a real chat, 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: someone else’s server does not bring the conversation down.
  • What your server returns reaches the agent unfiltered. The agent reads it like any other tool result: there is no filter that separates information from orders. The platform does not give the agent payment routes of its own (payments come in by receipt), but a tool on your server can do whatever your system allows: connect only servers you control and that return trustworthy data.
  • Use a public address that starts with https://. The dashboard also accepts http://, but the agent will not use it. Local or private-network addresses (localhost, 192.168…) are rejected.

​
How to know whether it worked

Every time the agent runs a tool, a chip appears in the chat thread with a lightning bolt, the tool’s name and a word that says how it ended (some tools show up with their name in English): If a turn uses several tools in a row, they fold into a single row — for example, «Conversión registrada · Acción programada ×2» (Conversion recorded · Scheduled action ×2). In that row success goes without a word and only what went off course is marked (falló, bloqueado, omitido, descartado). Press it to see the chips one by one. If a chip surprises you, press it: it unfolds with the data the agent passed to the tool and what the tool returned. It is the fastest way to understand why it did what it did. In the playbook’s Probar something similar happens: under each reply you see the tools it used, with «error», «bloqueada», «omitida» or «descartada» if something went off course. The summary of all this lives in Resultados, in the Operativo (Operational) group: Éxito de herramientas says what share of the tool calls went well. It is explained in Orders and metrics.

​
If something is not working

Look in the chat thread for the notice’s chip. If it says falló, unfold it: the most common cause is a number without a country code or a contact that is not in Números frecuentes. Also open the playbook’s Doctor, which flags those two cases as errors.If you named «Equipo de ventas», check that the Informar de las ventas list in the Configuración has at least one number.If the chip says ejecutado and the notice still did not arrive, unfold it: if some destination was not valid, it says so there («NO avisé a: …» — I did NOT notify: …), and if the same notice had already gone out a few minutes before, it is not repeated. If it is not that, that person may have gone more than 24 hours without writing to your funnel’s line: in that case the sending can be held back to look after your number. Ask them to send a message to that line.
The possible causes:
  1. The agent scheduled another one. The new one replaces its previous one; an agreed day also replaces its scheduled actions.
  2. It was set to be cancelled if the customer replied, and they replied.
  3. When it came due, the conversation was in manual mode.
  4. The turn that scheduled it did not reach the customer (the customer wrote over it): whatever was scheduled in that turn is cancelled with it.
  5. The customer unsubscribed and no longer receives messages from the agent.
You can see it all in the chat’s Ficha, sections Recordatorios and Acciones programadas.
That is expected when the reminder is a note: the agent writes the message. If you want it to go out word for word, write «dile exactamente esto:» after the delay, with the colon, and the text after it.
Check in the funnel’s Configuración that Informar de las ventas has numbers: without them, the notice does not reach your team. Remember that it notifies sales and services, not appointments or leads, and that a second sale in the same chat within 24 hours does not notify again. And check in the thread that the sale was recorded: unfold the Conversión registrada chip and read what it returned. That chip appears even if the sale did not go in (for example, if the amount was missing) or if it was the same sale repeated within 24 hours.
They are tools that depend on something of yours. Prices: active products in the catalog. Location: premises under Librería → Ubicaciones for that funnel. Stock: the Inventario app, the Consultar stock switch in that funnel’s Configuración, and the catalog.
Wait a few minutes after adding the server. Check that the card says Activo, that the URL starts with https:// and is public, and that you do not go over 5 servers or 20 tools in total.

​
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; that comes with the connection by default. If, when connecting it, you also asked for the operations and playbook-writing groups, it can also list, cancel and schedule a chat’s reminders, and write the tools into the playbook for you: ask it to use the exact sentence and to show you the chapter before saving. The link the dashboard gives you already asks for those groups; if you use a different one, see The connection URL. The tools your assistant has for that are in the Tool reference.
Last modified on October 19, 2026