Dashboard manual · Intelligence

Advanced base: company memory, queries to your system, inbound webhooks and AI flows

The Advanced base is the module that makes the AI learn from conversations (with your approval), query your system during service, keep the catalog up to date on its own, act when your system sends a notice, and follow flows designed node by node.

When it appears: The item appears in the menu only when the "Base de conhecimento avançada" (Advanced knowledge base) module is active on the account. Without the module turned on, opening any of its screens takes you to the module page, in "Módulos" (Modules), where it is activated.

Who can use it

RoleWhat you see and do
OwnerSees and uses everything. Only the Owner (the account manager) turns on a sync, publishes actions and flows (even with a failing evaluation), goes back to an old version, takes a flow offline, decides "Aplicar mesmo assim" (Apply anyway) on the safety brake, switches or keeps the spreadsheet, restores the spreadsheet, tests an action that writes, changes the webhook secret, invalidates the old secret, creates a new endpoint, deletes rules and archives anything that already has history.
AdminSees the item and all screens. Approves, edits, rejects and archives facts; creates and edits actions, syncs, flows, events and rules; tests actions that only read; pauses, resumes and runs the sync on the spot; ignores a halted round; shows the webhook secret; sees the masked input in "Execuções" (Runs) (it is logged) and permanently deletes what never ran. Does not publish: the dialog warns that only the account manager publishes.
AgentDoes not see the Advanced base item in the menu. If the address of one of the screens is opened, the user is sent back to the start of the dashboard.

Screens

"Visão geral" (Overview)

The Advanced base Overview screen lets you see at a glance what the module has learned and done: approved facts, queries to your system, success rate, what needs your attention and the health of the connections.

Address in the dashboard: /app/base-avancada

The "Visão geral" (Overview) screen in the demo account, with sample data and blurred values.

How to get there: "Base avançada" (Advanced base) menu → "Visão geral" (Overview), or the "Abrir" (Open) button on the module card in "Módulos" (Modules).

Module header (on every Advanced base screen)

The module name, its status and the tabs that lead to each part.

Buttons and actions

"Plano e preço" (Plan and price)
Opens the module page in "Módulos" (Modules), with the plan, what is included and the turn-off button.
"Nova ação" (New action)
Opens the choice of action type: "Consultar na hora" (Query on the spot) or "Sincronizar com a base" (Sync with the base).
"Visão geral" (Overview)
Tab with the numbers and what the module did over the last few hours.
"Memória da empresa" (Company memory)
Tab for the queue of proposed facts; shows how many are waiting for review.
"Ações" (Actions)
Tab with the queries and syncs; shows how many exist.
"Fluxos" (Flows)
Tab with the AI flows; shows how many exist.
Webhooks
Tab for the notices your system sends; shows how many events exist.
"Execuções" (Runs)
Tab with every call the AI made to your system and the notices received.
  • "Ativo" (Active) badge or, during the trial period, the days remaining.
  • Account name and its "Segmento" (Industry) next to the title.
  • On mobile, the tab strip scrolls sideways and brings the open tab into view.

Plan notices

They appear at the top when something about the module's plan needs action.

Buttons and actions

"Recarregar" (Top up)
Takes you to "Carteira" (Wallet) to top up your balance when there is not enough balance for the module's subscription.
"Assinar agora" (Subscribe now)Owner
During the trial period, when the included queries run out, it confirms the subscription and the syncs start running again.
  • "Saldo insuficiente para a mensalidade" (Insufficient balance for the subscription): the module stays on until the date shown.
  • Notice that the trial reached the total of included queries and the syncs paused.

Module numbers

Five indicators at the top of the screen.

  • Approved facts: total, how many this month and how many expired.
  • The AI started answering: questions that used to go to the team.
  • Published actions: with the count of drafts and flows.
  • Queries this month: the queries used and, when the plan has an allowance, the bar showing how much of the included amount has been used.
  • Success rate: failures and your system's average response time.

Replies based on what the AI learned

Weekly chart: what the AI answered with an approved fact or a query and what went to the team.

Buttons and actions

"Ir para a Memória" (Go to Memory)
On the empty chart, opens "Memória da empresa" (Company memory) so you can approve the first facts.
"Nova ação" (New action)
On the empty chart, opens the creation of an action.
  • Legend: Answered by the AI and Went to the team.
  • The date the module was turned on appears in the corner of the legend.

"Agora" (Now)

What the module did over the last few hours, from newest to oldest.

Buttons and actions

"Revisar" (Review)
When the Curator proposed new facts, opens the "Memória da empresa" (Company memory) queue.
  • Sync rounds: synced, failed, paused by the safety brake, refused due to the plan limit or syncing; the time leads to the sync.
  • Queries to your system during the conversation; when the system did not respond, the line says the conversation was passed to the team. The time leads to "Execuções" (Runs).
  • Notices received from your system, with how many leads were notified; the time leads to Webhooks.
  • Curator readings: how many new facts it proposed and from how many conversations.

To do

Shortcuts to what needs your attention.

Buttons and actions

"Revisar ‹n› fatos propostos" (Review ‹n› proposed facts)
Opens the Memory queue; says how many contradict facts that already exist.
"Ver “‹sincronização›”" (View “‹sync›”)
Opens the sync that failed or is paused (brake, spending cap, trial or module turned off).
"Terminar “‹rascunho›”" (Finish “‹draft›”)
Opens the draft of a sync or an action so you can finish the steps.
"Publicar alterações do fluxo" (Publish flow changes)
Opens the editor of the flow that has changes not yet published.
"‹n› fatos chegaram à data de revisão" (‹n› facts reached their review date)
Opens "Aprovados" (Approved): the AI keeps using them, so confirm they are still valid.
"‹n› fatos venceram" (‹n› facts expired)
Opens "Vencidos" (Expired) so you can renew or archive them.
  • With nothing pending, the card says "Tudo em dia." (All caught up.)

Connection health

Each connection to your system, with the rate of successful calls and the average time.

Buttons and actions

"Mais ações de ‹conexão›" (More actions for ‹connection›)
Opens the connection menu.
"Excluir conexão" (Delete connection)
Opens the delete dialog; a connection used by an action or a sync cannot be removed until you delete or archive whatever uses it.
  • Inbound webhook: a lit dot when it is receiving and the time of the last notice.
  • With no connections: "Nenhuma conexão ainda." (No connections yet.)

Screen states

Loading
Skeletons for the five numbers and the chart.
Nothing here yet
Chart with "Os números aparecem com o uso" (The numbers appear with use) and the shortcuts "Ir para a Memória" (Go to Memory) and "Nova ação" (New action); "Agora" (Now) says nothing happened in the last few hours.
If something goes wrong
"Não foi possível carregar a Visão geral" (Could not load the Overview), with the assurance that facts, syncs and queries keep working and the try-again button.
Failure to open the module
"Não foi possível abrir a Base avançada" (Could not open the Advanced base), saying nothing changed on the account, with the try-again button.

"Memória da empresa" (Company memory)

The "Memória da empresa" (Company memory) screen is for approving, editing or rejecting the facts the Knowledge Curator learned from conversations, and for taking care of approved and expired facts.

Address in the dashboard: /app/base-avancada/memoria

The "Memória da empresa" (Company memory) screen in the demo account, with sample data and blurred values.

How to get there: "Base avançada" (Advanced base) menu → "Memória da empresa" (Company memory) (the number next to it counts the facts to review).

Memory tabs

Buttons and actions

"Para revisar" (To review)
Shows the queue of proposed facts, with the count.
"Aprovados" (Approved)
Shows the table of facts the AI uses, with the count.
"Vencidos" (Expired)
Shows the facts whose validity has passed, so you can renew them.
  • Keyboard shortcuts in the queue: A to approve, E to edit, R to reject, J and K to move between cards (they do not apply inside a field).

Proposed fact card

Each proposed fact, with its source, the Curator's confidence and the actions.

Fields and filters

"Categoria" (Category)
Those for your "Segmento" (Industry), plus Others. The Curator chooses; you change it here (it appears on the focused card).
"Validade" (Validity)
No expiry, Until a date or Review in 90 days.
"Vale até" (Valid until)
The date the fact goes out of use, when the validity is Until a date.

Buttons and actions

"Aprovar" (Approve)
The AI and the Auditor start using the fact from the next message.
"Aprovar e substituir" (Approve and replace)
Appears when the fact contradicts an approved one: approves this one and archives the old one.
"Editar" (Edit)
Makes the fact text editable on the card itself.
"Pronto" (Done)
Ends editing and saves the adjusted text; after that you only need to approve.
"Recusar" (Reject)
Removes the fact from the queue; the Curator does not propose the same sentence again.
"A mesma pergunta em mais ‹n› conversas" (The same question in ‹n› more conversations)
Opens the fact drawer with all the source conversations.
  • Source badge: unanswered question, agent reply, blocked by the Auditor or spreadsheet.
  • The source conversation: what the lead asked, what the AI was going to say and what the team answered.
  • Notice "Contradiz um fato aprovado" (Contradicts an approved fact) with the old text, or "Vence sozinho em" (Expires on its own on) when the Curator found the date in the sentence.
  • The Curator's confidence meter, as a percentage.

How the memory works and Where they came from

The side panel of the queue.

  • The rules: the Curator proposes and only you or a manager approves; the Auditor checks every reply; a fact with an expiry goes out of use the day after it expires; the lead's personal data never becomes a fact.
  • Where the facts proposed in the last 30 days came from, by source, and the proportion approved and rejected.

"Aprovados" (Approved)

The table of facts the AI uses.

Fields and filters

"Buscar fato" (Search fact)
Search within the text of approved facts.
"Fato" (Fact)
The text and the source (conversations and who approved it).
"Categoria" (Category)
The category of the fact.
"Validade" (Validity)
No expiry, Expires on or Review on, with the date.
"Usado" (Used)
How many times the AI used the fact.
"Aprovado" (Approved)
The approval date.

Buttons and actions

"Todas" (All)
Shows facts from all categories; next to it, one button per category filters the table.
"Ver mais" (See more)
Loads more approved facts.
  • Clicking a row (or Enter) opens the fact drawer.

"Vencidos" (Expired)

Facts whose validity has passed and which the AI stopped using.

Fields and filters

"Validade" (Validity)
The new validity of the renewed fact.
"Vale até" (Valid until)
Required when the validity is Until a date.

Buttons and actions

"Renovar" (Renew)
Opens the Renew the fact box, with the new validity; confirming makes the AI use it again from the next message.
"Cancelar" (Cancel)
Closes the box without renewing.

Fact drawer

Opens from the table or from the conversations link; shows everything about a fact.

Fields and filters

"Texto do fato" (Fact text)required
The text the AI uses.
"Categoria" (Category)
The category of the fact.
"Validade" (Validity)
No expiry, Until a date or Review in 90 days.
"Vale até" (Valid until)
The end date, when the validity is Until a date.

Buttons and actions

"Editar" (Edit)
Opens the fact form; the new text takes effect immediately and goes into the history.
"Arquivar" (Archive)
Asks "Arquivar o fato?" (Archive the fact?); once confirmed, the AI stops using it and the fact leaves the table but stays in the audit trail.
"Abrir" (Open)
Opens the source conversation in the Inbox.
"Salvar" (Save)
Saves the edited text, category and validity.
"Cancelar" (Cancel)
Leaves editing without saving.
  • Validity, Approved by, Proposed by the Knowledge Curator (with its confidence) and "Usado" (Used) (AI replies and Auditor checks).
  • Source conversations and the fact's History, from newest to oldest.

Screen states

Loading
Skeletons of the fact cards.
Nothing here yet
In the queue: "Tudo revisado" (All reviewed), with the button to see the approved ones. In "Aprovados" (Approved): "Nenhum fato aprovado ainda" (No approved facts yet) or "Nenhum fato com essa busca" (No facts match this search). In Vencidos: "Nenhum fato vencido" (No expired facts).
If something goes wrong
"Não foi possível carregar os fatos para revisar" (Could not load the facts to review) (the approved ones remain in effect), with the try-again button.

"Ações no seu sistema" (Actions in your system)

The "Ações" (Actions) screen is for viewing and creating what the AI queries in your system during the conversation or syncs with the base, starting from scratch or from a ready-made template for your "Segmento" (Industry).

Address in the dashboard: /app/base-avancada/acoes

The "Ações no seu sistema" (Actions in your system) screen in the demo account, with sample data and blurred values.

How to get there: "Base avançada" (Advanced base) menu → "Ações" (Actions).

Your actions

Buttons and actions

"Nova ação" (New action)
Opens the choice of action type.
"Criar consulta" (Create query)
"Consultar na hora" (Query on the spot) card: opens the type choice with the query already selected.
"Criar sincronização" (Create sync)
"Sincronizar com a base" (Sync with the base) card: opens the sync creation directly.
"Excluir ação" (Delete action)
In the query card's menu, opens the delete or archive dialog.
  • Card for each sync: status (Draft, Syncing every so many hours, Paused, Last round failed), how many items it pulled and to where, and when it last ran. A draft opens editing; one that is on opens the sync.
  • Card for each query: Published with the version or Draft, whether it only reads or writes (the lead confirms) and the month's calls with the success rate. Clicking opens the editor.

Start from a template

Ready-made actions by industry: you only point to your system's address.

Buttons and actions

"Todos" (All)
Shows the templates for all industries; next to it, one button per industry filters them.
"Usar" (Use)
Creates the action draft filled in by the template and opens the editor.
"Criar" (Create)
On the "Criar do zero" (Start from scratch) card, creates an empty action (any API that responds in JSON) and opens the editor.
  • Each template shows who it is for and whether it only reads or also writes.

Screen states

Loading
Skeletons of the cards.
Nothing here yet
"Nenhuma ação ainda" (No actions yet), suggesting you start from a template or sync a list from your system.
If something goes wrong
"Não foi possível carregar as suas ações" (Could not load your actions) (queries and syncs keep working). If only the templates fail: "Não foi possível carregar os modelos" (Could not load the templates), and you can still create from scratch.

"Nova ação" (New action)

The "Nova ação" (New action) screen is for deciding the type of action: query your system on the spot, during the conversation, or sync an entire list with the base from time to time.

Address in the dashboard: /app/base-avancada/acoes/nova

The "Nova ação" (New action) screen in the demo account, with sample data and blurred values.

How to get there: "Nova ação" (New action) button in the module header, in "Visão geral" (Overview) or in "Ações" (Actions); or "Trocar o tipo" (Change type), inside an editor.

What will this action do?

Buttons and actions

"Consultar na hora" (Query on the spot)
Chooses the query: the AI asks your system while talking to the lead (runs on every question, counts 1 query per call).
"Sincronizar com a base" (Sync with the base)
Chooses the sync: the whole list is pulled every 1, 6 or 12 hours, or 1 time a day, and replaces the spreadsheet you upload by hand.
"Cancelar" (Cancel)
Goes back to "Ações" (Actions).
"Continuar com “‹tipo›”" (Continue with “‹type›”)
For the query, creates the draft and opens the editor; for the sync, opens the sync creation.
  • Fixed tip: you can use both together, syncing the catalog and querying only the store's stock on the spot.

"Nova sincronização" (New sync)

The "Nova sincronização" (New sync) screen is for connecting a list from your system (catalog, prices, service table) to the base, in six steps, with a list test and a preview of how the AI will read each item.

Address in the dashboard: /app/base-avancada/sincronizacoes/nova

The "Nova sincronização" (New sync) screen in the demo account, with sample data and blurred values.

How to get there: "Ações" (Actions) → "Criar sincronização" (Create sync), or "Nova ação" (New action) → "Sincronizar com a base" (Sync with the base) → "Continuar" (Continue). The spreadsheet notice in the "Base de conhecimento" (Knowledge base) also opens this screen, with the comparison.

"Cabeçalho" (Header)

Fields and filters

"Nome da sincronização" (Sync name)required
The editable title at the top; it cannot be left empty.

Buttons and actions

"Trocar o tipo" (Change type)
Goes back to the action type choice.
"Ligar e sincronizar agora" (Turn on and sync now)Owner
Saves, turns on the sync and runs the first round; with a spreadsheet to replace, it takes you to the comparison first. It is blocked if the list exceeds the plan limit.
  • Badges "Sincronizar com a base" (Sync with the base) and Draft, and the "saved ago" of the autosave (or the reason it did not save).
  • For anyone who is not the Owner, in place of the button: "Só o responsável pela conta liga a sincronização." (Only the account manager turns on the sync.)

Spreadsheet notice

Appears when you have imported a spreadsheet into the "Base de conhecimento" (Knowledge base).

Buttons and actions

"Ver a comparação" (See comparison)
Tests the list and opens the "Trocar a planilha" (Change the spreadsheet) screen with the column-by-column comparison.

Steps

The strip with the six steps; a completed one gets a mark and clicking scrolls to it.

Buttons and actions

"Conexão" (Connection)
Goes to step 1.
"Lista" (List)
Goes to step 2.
"Campos" (Fields)
Goes to step 3.
"Destino" (Destination)
Goes to step 4.
"Frequência" (Frequency)
Goes to step 5.
"Itens que somem" (Items that disappear)
Goes to step 6.

1 · Connection

The same vault as the other actions; the token never appears again.

Fields and filters

"Nome da conexão" (Connection name)
Appears in notices, such as "Sistema da loja não respondeu" (Store system did not respond).
"Cabeçalho do token" (Token header)
The header the token goes in (it already comes as Authorization).
Token
Goes to the vault and never appears again.

Buttons and actions

"Guardar no cofre" (Store in vault)
Stores the token encrypted; the step badge becomes Connected.
"Trocar" (Change)
With a token already stored, opens the fields to store another one.
"Cancelar" (Cancel)
Gives up on changing the token.
"Usar “‹conexão›”" (Use “‹connection›”)
When the address already has a connection on the account, it starts using that same one, without creating an identical one.

2 · List address

Where the entire list comes from; if it arrives in pages, reading continues to the last one.

Fields and filters

"Método" (Method)
Always GET: the sync only reads.
"Endereço" (Endpoint)required
The list's address in your system.
"Paginação" (Pagination)
Automatic (shows what the test detected), Cursor (next field) or No pagination.
"Onde está a lista na resposta" (Where the list is in the response)
The path to the list within the response, such as dados.produtos.

Buttons and actions

"Testar a lista" (Test the list)
Reads all pages, shows progress page by page and, at the end, how many pages and items came back and how long it took. Testing does not count as a query.
  • If the list has more items than the plan syncs, the notice "A lista passou do limite do plano" (The list exceeded the plan limit) suggests filtering the address.

3 · Fields · what the AI reads

The columns of your system, with a suggested name in Portuguese.

Fields and filters

"Coluna no seu sistema" (Column in your system)
The column name as it comes from the system.
"Exemplo" (Example)
An example value read during the test.
"Nome que a IA lê" (Name the AI reads)
The name in Portuguese of that column; the Key column appears as an internal code.
"Papel" (Role)
Name, Price, Stock, Key or Other. One column must be the Key of each item and another the Name.
"Usar" (Use)
Switch: whatever is hidden does not reach the AI or show up for the lead.

4 · Destination

Fields and filters

"Coleção" (Collection)
In the catalog, the collection the items go into.

Buttons and actions

"Catálogo de produtos" (Product catalog)
One item per product, with price and stock; the AI builds the order from it.
"Base de conhecimento" (Knowledge base)
One snippet per row, as in the spreadsheet import.

5 · Frequency

Buttons and actions

"A cada ‹n› h" (Every ‹n› h)
Fetches the list every 1, 6 or 12 hours.
"1 vez por dia" (1x per day)
Fetches the list once a day.
  • The upcoming rounds, the queries per day and the forecast of queries for the month (no charge when the module is included in the plan).

6 · Item that disappeared from your system

Buttons and actions

"Marcar como indisponível" (Mark as unavailable)
The AI says it is out of stock and offers to notify when it comes back.
"Tirar da base" (Remove from the base)
The item disappears for good and the AI starts saying it does not carry it.
"Freio de segurança" (Safety brake)
Switch: if more than 20% of the items disappear in one round, the sync pauses and warns you before changing the base.

How the AI will read it

The fixed side panel, with the preview of the first items and the summary.

  • The first items with the chosen names; it warns when the names come in capital letters and the AI reads them in normal case.
  • Items (out of the total the plan allows), Per round (pages and queries) and Agent: Actions Operator (on your company's model, when the account uses its own AI).

Screen states

Loading
Skeletons of the title and steps, when a draft that was already saved is opened.
If something goes wrong
"Não foi possível abrir a sincronização" (Could not open the sync), saying nothing changed in it. A save failure appears next to the title, and what you wrote stays on screen.
Before the test
Step 3 tells you to test the list in step 2, and the preview asks for the test.
The Key column is missing
"Escolha a coluna que é a chave de cada item (o papel “Chave”)." (Choose the column that is the key of each item (the “Key” role).)

"Sincronização" (Sync)

The "Sincronização" (Sync) screen is for following a sync that is on: the last and next round, what changed item by item, the round history and the decisions when something goes wrong.

Address in the dashboard: /app/base-avancada/sincronizacoes/‹…›

How to get there: Click the card of a sync that is on in "Ações" (Actions), or the time of a round in "Visão geral" (Overview).

"Cabeçalho" (Header)

Buttons and actions

"Editar" (Edit)
Opens the sync editing in six steps.
"Pausar" (Pause)
Stops the rounds; the AI keeps using the last good version.
"Retomar" (Resume)
Goes back to running on schedule.
"Sincronizar agora" (Sync now)
Runs a round outside the schedule; the button shows "Sincronizando… página ‹n› de ‹total›" (Syncing… page ‹n› of ‹total›). It is blocked while the sync is paused or halted.
  • Status badge and the "system → destination" path (Knowledge base or Catalog with the collection).

Round notices

Buttons and actions

"Aplicar mesmo assim" (Apply anyway)Owner
On the safety brake, applies the round that removed many items at once.
"Ignorar esta rodada" (Skip this round)
On the safety brake, discards the round; nothing changes in the base and the next one runs on schedule.
"Tentar agora" (Try now)
After a failure, runs again right away.
"Ajustar o teto" (Adjust the limit)
With the sync paused by the spending cap, opens "Configurações" (Settings) at the billing section.
  • Round paused by the brake: says what percentage of the items disappeared at once and that nothing changed in the base.
  • Round refused: the list exceeded the plan limit; nothing changed.
  • Round that failed: the AI keeps the last good version, the platform tries again in 15 minutes and, on the third failure, you receive an email.
  • The plan notices (balance for the subscription, trial queries) also appear here.

Last round numbers

  • Last sync (time, day, duration, pages), Next (or "paused"), "Novos" (New), Changed (prices and stock set to zero) and "Indisponíveis" (Unavailable) (disappeared from the system).

What changed in the last round

Fields and filters

"Produto" (Product)
The item name (Item, when the destination is the "Base de conhecimento" (Knowledge base)).
"Mudança" (Change)
The type: new, price, stock, changed, stock zeroed, unavailable or removed.
"Antes" (Before)
The previous value.
"Agora" (Now)
The new value; for unavailable, that the AI offers to notify.

Buttons and actions

"Tudo" (All)
Shows all changes.
"Preço" (Price)
Only the items whose price changed.
"Novos" (New)
Only the items that came in.
"Indisponíveis" (Unavailable)
Only the items that did not come in the list.

Rounds

Buttons and actions

"Ver" (View)
On a round paused by the brake, scrolls to the notice with the decision.
  • Each round with day and time, whether it was manual, applied anyway, ignored, failed or was refused, and the duration.

Summary

Buttons and actions

"Voltar a planilha" (Back to the spreadsheet)Owner
Asks "Voltar a planilha?" (Restore the spreadsheet?); once confirmed, the spreadsheet goes back to the base and the sync pauses.
"Cancelar" (Cancel)
Closes the confirmation without restoring the spreadsheet.
  • In the catalog (or In the base): items and unavailable ones, and how many items are awaiting text review.
  • This month: rounds and queries.
  • Spreadsheet: when it left and until when it is kept.

Screen states

Loading
Skeletons of the title and cards.
Nothing here yet
"A primeira rodada mostra aqui cada item que entrou, mudou de preço ou sumiu." (The first round shows here each item that came in, changed price or disappeared.) and "A primeira rodada aparece aqui assim que terminar." (The first round appears here as soon as it finishes.)
If something goes wrong
"Não foi possível abrir a sincronização" (Could not open the sync) (it keeps running on schedule), with the try-again button.

"Editar sincronização" (Edit sync)

The "Editar sincronização" (Edit sync) screen is for changing the connection, the list, the fields, the destination, the frequency or what to do with items that disappear, or for finishing a draft.

Address in the dashboard: /app/base-avancada/sincronizacoes/‹…›/editar

How to get there: "Editar" (Edit) button on the sync, the card of a draft in "Ações" (Actions), or Finish in "Visão geral" (Overview).

The six steps

The same steps and fields as the New sync, already filled in and saved automatically.

Buttons and actions

"Ver a sincronização" (View the sync)
With the sync already on, goes back to its screen.
"Ligar e sincronizar agora" (Turn on and sync now)Owner
On a draft, turns it on and runs the first round.
"Trocar o tipo" (Change type)
Goes back to the action type choice.
"Testar a lista" (Test the list)
Reads the list again and updates the columns and the preview.
  • The badge shows On or Draft; the path at the top says Edit sync or New sync.

Screen states

Loading
Skeletons of the title and steps.
If something goes wrong
"Não foi possível abrir a sincronização" (Could not open the sync), saying nothing changed in it.

"Trocar a planilha" (Change the spreadsheet)

The "Trocar a planilha" (Change the spreadsheet) screen is for comparing the spreadsheet you imported into the "Base de conhecimento" (Knowledge base) with your system's list and deciding to switch to the sync or keep the spreadsheet for now.

Address in the dashboard: /app/base-avancada/sincronizacoes/‹…›/trocar-planilha

How to get there: "Ver a comparação" (See comparison), in the spreadsheet notice; or "Ligar e sincronizar agora" (Turn on and sync now) on a sync that came from a spreadsheet.

The switch

  • The spreadsheet (when and by whom it was imported, rows and how many days old the prices are) next to the sync (items now and frequency).
  • The spreadsheet stays in effect until the first sync finishes successfully; only then does it go out and get kept for 30 days.

Column comparison

Fields and filters

"Na planilha" (In the spreadsheet)
The spreadsheet column (or "não tinha" (it had none), for a new column).
"No sistema" (In the system)
The matching column in the system, or "não existe no sistema" (does not exist in the system).
"Nome que a IA lê" (Name the AI reads)
The field's name in Portuguese.
"Situação" (Status)
matches, matches with prices that changed, becomes a fact, empty or new.
  • A column with text that does not exist in the system becomes facts in "Memória da empresa" (Company memory), for you to approve.

How the switch happens

Buttons and actions

"Trocar pela sincronização" (Switch to sync)Owner
Turns on the sync and waits for the first round: if it finished well, it opens the sync; if it errored, nothing changes and the notice appears.
"Manter a planilha por enquanto" (Keep the spreadsheet for now)Owner
Leaves the sync as a draft and goes back to "Ações" (Actions).
"Nova sincronização" (New sync)
In the path at the top, goes back to the sync creation.
  • For anyone who is not the Owner: "Só o responsável pela conta troca a planilha pela sincronização ou decide manter." (Only the account manager switches the spreadsheet to the sync or decides to keep it.)

Screen states

Loading
Skeletons; during the test, "Comparando as colunas da planilha com a lista do sistema…" (Comparing the spreadsheet columns with the system list…).
If something goes wrong
"Não foi possível carregar a comparação" (Could not load the comparison) (the spreadsheet stays in effect).
The first round failed
"A primeira sincronização não terminou bem" (The first sync did not finish well): nothing changed and the spreadsheet stays in effect.
No list test
Asks you to test the list when creating the sync.

"Editar ação" (Edit action)

The "Editar ação" (Edit action) screen is for setting up a query to your system in steps: the connection, what the AI collects from the lead, what it can use from the response and when to call, with autosave and versions.

Address in the dashboard: /app/base-avancada/acoes/consultas/‹…›

How to get there: Click the card of a query in "Ações" (Actions), use a template, "Criar do zero" (Start from scratch), or "Abrir a ação" (Open the action) in a flow's inspector.

"Cabeçalho" (Header)

Fields and filters

"Nome da ação" (Action name)required
The editable title; it cannot be left empty.

Buttons and actions

"v‹n› publicada" (v‹n› published)
Badge of the live version; clicking opens the Versions drawer.
"Testar" (Test)
Saves and opens the action test.
"Publicar v‹n›" (Publish v‹n›)
Saves and opens the publish dialog; it is disabled when nothing has changed since the published version.
  • Badges Draft and Unpublished changes, and the "saved ago" of the autosave.

Action steps

Buttons and actions

"Conexão" (Connection)
Goes to step 1.
"Entrada" (Input)
Goes to step 2.
"Resposta" (Response)
Goes to step 3.
"Quando usar" (When to use)
Goes to step 4 and, if the intents are empty, asks the Actions Operator for a suggestion.
"Testar" (Test)
Opens the test.
"Publicar" (Publish)
Opens the publish dialog.

Connection to your system

Fields and filters

"Método" (Method)
GET to query, POST to write (POST marks the action as "writes").
"Endereço" (Endpoint)
Your system's address, with the fields between braces, such as {cep}. Below, "Vai chamar" (Will call) shows the address with example values.
"Corpo da chamada (JSON)" (Request body (JSON))
POST only; it must be a JSON object and accepts {campo} for what the AI collects.
"Cabeçalho" (Header)
The token header.
Token
It goes encrypted to the vault; nobody on the team sees it again, nor does the AI.
"Tempo limite" (Timeout)
5 seconds, 8 seconds or 15 seconds; beyond that, the AI says it will confirm and calls the team.

Buttons and actions

"Trocar o tipo" (Change type)
Goes back to the action type choice.
"Guardar token" (Store token)
Opens the token fields when there is not one yet.
"Trocar" (Change)
Opens the fields to change the stored token.
"Guardar no cofre" (Store in vault)
Stores the token.
"Cancelar" (Cancel)
Gives up on storing the token.
"Só consulta" (Read-only)
The action only reads from your system.
"Grava no meu sistema" (Writes to my system)
The action writes; the AI asks the lead for confirmation before each call.
  • When the address already has a connection on the account, the notice says this action uses that same one, with its token.

Input · what the AI collects from the lead

Fields and filters

"Campo" (Field)
The field's technical name and, below it, the label in Portuguese.
"Formato" (Format)
CEP, number, CPF, CNPJ, date, email, phone or text.
"Como a IA pede" (How the AI asks)
The sentence the AI uses to ask for the data; if empty, it does not ask and uses it if the lead says it.
"Obrigatório" (Required)
Switch: the AI never calls with an empty required field; it asks first.

Buttons and actions

"Campo" (Field)
Adds an input field.
"Tirar o campo ‹campo›" (Remove the ‹field› field)
Removes the field from the input.
  • Red warning when the action looks up by CPF without sending the lead's phone: anyone who typed a CPF would see the data of its owner.

"Resposta" (Response) · what the AI can use

Buttons and actions

"usa" (uses)
Clicking hides the response field: the AI never sees what is hidden.
"oculto" (hidden)
Clicking makes the field available for the AI to use.
"Editar o rótulo de ‹campo›" (Edit the label of ‹field›)
Opens the field's name in Portuguese for editing.
"Testar" (Test)
With the response still empty, opens the test so you can read the real response.
  • Shows the day the response was read in a real test.

"Quando usar" (When to use)

Fields and filters

"Descrição" (Description)
How you would explain to a new agent when to call the action.
"A IA consulta quando o lead…" (The AI queries when the lead…)
The intents: question about a product or service, asks the price, wants to buy or hire, wants to book a time, is already a customer and asks for help. Outside these, the AI does not even consider the action.
"Frases de exemplo · deve chamar" (Example phrases · should call)
Phrases that should trigger the action.
"Frases de exemplo · não deve chamar" (Example phrases · should not call)
Phrases that should not trigger it.

Buttons and actions

"Frase" (Phrase)
Adds an example phrase (Enter saves, Esc cancels).

How the AI will use it and "Avaliações" (Evaluations)

The side panel with a summary of what is configured.

  • "Chama" (Calls), "Pede ao lead" (Asks the lead), "Pode dizer" (Can say), "Nunca vê" (Never sees) (the hidden fields and the token), "Antes de chamar" (Before calling) (in the action that writes), "Se falhar" (If it fails) and "Modelo" (Model) (on Enterprise, set in "Roteamento" (Routing) → "Operador de ações na conversa" (In-conversation Action Operator)).
  • "Avaliações" (Evaluations): the sample conversations, each one marked "passou" (passed), "revisar" (review), "falhou" (failed) or "a rodar" (to run).

End of the page and the "Versões" (Versions) drawer

Buttons and actions

"Excluir ação" (Delete action)
Opens the delete or archive dialog; then returns to "Ações" (Actions).
"Ver" (View)
In the "Versões" (Versions) drawer, shows that version's configuration.
"Voltar para esta" (Go back to this one)Owner
Asks whether you want to go back; the old version becomes the next one and the AI starts using it on the next message. An action that writes asks for the two-step code.
  • Each version with who published it and when, the in-use badge and the notice for a version published with a failure.

"Publicar a versão" (Publish the version) dialog

Runs the evaluations against your system (read-only) and shows what changes since the previous version.

Fields and filters

"Código de verificação" (Verification code)
In the action that writes, the code from the Owner's two-step verification app.

Buttons and actions

"Corrigir antes" (Fix first)
Closes the dialog without publishing.
"Publicar" (Publish)Owner
Publishes the new version; the AI uses it starting with the next message.
"Publicar assim mesmo" (Publish anyway)Owner
With a failing evaluation, publishes anyway and it is logged.
  • "Rodando as avaliações no seu sistema… ‹n› de ‹total›" (Running the evaluations on your system… ‹n› of ‹total›) while they run.
  • Without two-step verification turned on, the notice tells you to turn it on in "Configurações" (Settings) → "Segurança" (Security) to publish an action that writes.
  • For anyone who is not the Owner: "Só o responsável pela conta publica. Você pode testar e deixar tudo pronto." (Only the account manager publishes. You can test and get everything ready.)

Screen states

Loading
Skeleton placeholders for the title and the editor.
If something goes wrong
"Não foi possível abrir esta ação" (Could not open this action) (it may have been deleted or the connection dropped). A failure to save appears next to the title, and what you wrote stays on the screen.

"Testar ação" (Test action)

The "Testar ação" (Test action) screen is for calling your system for real with sample data and seeing the request, the response and what the AI would say in a simulated conversation, without sending anything to any lead.

Address in the dashboard: /app/base-avancada/acoes/consultas/‹…›/testar

How to get there: The "Testar" (Test) button in the action editor, step 5, or "Testar só este nó" (Test only this node) in a flow's inspector.

"Cabeçalho" (Header)

Buttons and actions

"Voltar a editar" (Back to editing)
Returns to the action editor.
"Publicar v‹n›" (Publish v‹n›)
Opens the publish dialog (the same one as in the editor).

"Entrada do teste" (Test input)

Fields and filters

"‹campo›" (‹field›)
One field for each input value, with sample values.
"‹variável› (teste)" (‹variable› (test))
The lead's phone or name used in the test; in the conversation, they come from the real lead.
"Fala do lead" (Lead's message)
What the lead would say; changing the message or a field switches the scenario to "Entrada digitada" (Typed input).

Buttons and actions

"Entrada digitada" (Typed input)
Uses the typed values.
"‹avaliação›" (‹evaluation›)
Under "Cenário de exemplo" (Sample scenario), loads the input and the message from a saved evaluation.
"Executar teste" (Run test)
Calls your system and builds the simulated conversation.
"Entendo que este teste grava de verdade no meu sistema" (I understand this test really writes to my system)Owner
In the action that writes, the mandatory confirmation, together with the two-step code.
  • In the action that writes, anyone who is not the Owner sees: "só o responsável pela conta testa, com o código de 2 etapas." (only the account manager tests, with the 2-step code.)

"Requisição" (Request), "Resposta" (Response) and "O que a IA diria" (What the AI would say)

Fields and filters

"Código de verificação" (Verification code)
In the action that writes, the code from the verification app.

Buttons and actions

"Conferir também os valores que voltaram" (Also check the values that came back)
Makes the saved evaluation also check the response values, not just the decision.
"Salvar como avaliação" (Save as evaluation)
Saves the conversation as an example; it runs again with every publication.
  • Request with the token hidden.
  • Response with the code and the time; a timeout or an error says the call does not count against the allowance.
  • Simulated conversation with the AI's name, the action line and the note on how the AI decided.

Screen states

Loading
Skeleton placeholders for the title and the panels.
Nothing here yet
Before the test: "A requisição aparece aqui" (The request appears here) and "A conversa aparece aqui depois do teste." (The conversation appears here after the test.)
If something goes wrong
"Não foi possível abrir o teste desta ação" (Could not open this action's test), with the try-again button.

"Execuções" (Runs)

The "Execuções" (Runs) screen is for seeing each call the AI made to your system in conversations, with the action, the masked input, the result and the time, and the notices your system sent.

Address in the dashboard: /app/base-avancada/execucoes

The "Execuções" (Runs) screen in the demo account, with sample data and blurred values.

How to get there: The "Execuções" (Runs) tab in the header of "Base avançada" (Advanced base), or the time of a lookup in "Visão geral" (Overview).

Filters

Buttons and actions

"Todas" (All)
Shows all the calls, with the count.
"Com falha" (Failed)
Only the calls that failed.
"Avisos recebidos" (Notices received)
Swaps the table for the list of notices from your system, with how many messages went out. The number shows "100+" when there are more notices than the list holds.
"‹ação›" (‹action›)
One button per action filters that action's calls.
"Exportar" (Export)
Downloads the runs spreadsheet with the chosen filter.

Table of "Execuções" (Runs)

Fields and filters

"Quando" (When)
Date and time of the call.
"Ação" (Action)
The name and version of the action.
"Conversa" (Conversation)
The conversation's lead; "Primeira mensagem do lead" (Lead's first message) when the lookup ran before the conversation existed; "conversa excluída" (conversation deleted) when it was deleted afterward.
"Entrada" (Input)
What was sent, with personal data masked; the manager clicks to view it, and that is logged.
"Resultado" (Result)
The code and a summary of the response, or the reason it did not run.
"Tempo" (Time)
In milliseconds.
"Custo" (Cost)
What the call consumed from the plan.

Buttons and actions

"Ver a entrada de ‹ação› (fica registrado)" (View the input of ‹action› (it gets logged))Owner, Admin
Shows the unmasked input while the mouse is over it.
"Mostrar mais" (Show more)
Loads more runs.
  • Fixed note: failures do not count against the allowance.

Screen states

Loading
Skeleton rows.
Nothing here yet
"Nenhuma execução ainda" (No runs yet) (each call appears live), "Nenhuma falha" (No failures) in the failures filter and "Nenhum aviso recebido" (No notice received) in the notices.
If something goes wrong
"Não foi possível carregar as execuções" (Could not load the runs) (lookups keep running in the conversations).

"Fluxos" (Flows)

The "Fluxos" (Flows) screen is for viewing and creating the paths the AI follows when something happens: a message from the lead, a notice from your system, a time of day or a service event.

Address in the dashboard: /app/base-avancada/fluxos

The "Fluxos" (Flows) screen in the demo account, with sample data and blurred values.

How to get there: Menu "Base avançada" (Advanced base) → "Fluxos" (Flows).

"Seus fluxos" (Your flows)

Buttons and actions

"Novo fluxo" (New flow)
Opens the dialog to name the flow and choose the trigger.
"Mais ações de ‹fluxo›" (More actions for ‹flow›)
Opens the card menu.
"Excluir fluxo" (Delete flow)
Opens the dialog to delete or archive the flow.
  • Each flow's card: "Publicado" (Published) with the version, "Alterações não publicadas" (Unpublished changes), "Rascunho" (Draft) or "Fora do ar" (Offline); the trigger (in a published flow, the live version's trigger); the summary and the conversations (and errors) from the last 24 hours, or when it was last edited. Clicking opens the editor.

"Novo fluxo" (New flow) dialog

Fields and filters

"Nome" (Name)
The flow's name; if left empty, it is created as "Novo fluxo" (New flow).

Buttons and actions

"Mensagem do lead" (Lead's message)
Trigger that runs before the AI's normal service.
"Aviso do seu sistema" (Notice from your system)
Trigger that runs once per webhook from your system, after the event rules notify the leads.
"Agenda" (Calendar)
Trigger at a recurring time.
"Evento no atendimento" (Event in the conversation)
Trigger when the lead changes stage or becomes hot.
"Cancelar" (Cancel)
Closes without creating.
"Criar e abrir o editor" (Create and open the editor)
Creates the flow and opens the editor.
  • If the trigger already has a published flow, the notice says which one: only one counts at a time.

Screen states

Loading
Block skeletons.
Nothing here yet
"Nenhum fluxo ainda" (No flows yet), with the "Novo fluxo" (New flow) button.
If something goes wrong
"Não foi possível carregar os fluxos" (Could not load the flows), with the try-again button.

"Editor de fluxo" (Flow editor)

The "Editor de fluxo" (Flow editor) screen is for drawing, node by node, what the AI does, in full screen: the node list on the left, the canvas in the middle and the inspector for the selected node on the right, with test, evaluations, runs and versions.

Address in the dashboard: /app/base-avancada/fluxos/‹…›

How to get there: Click a card in "Fluxos" (Flows), "Criar e abrir o editor" (Create and open the editor) in "Novo fluxo" (New flow), or "Publicar alterações do fluxo" (Publish flow changes) in "Visão geral" (Overview).

Top bar

Fields and filters

"Nome do fluxo" (Flow name)
Editable; saves when you leave the field or with Enter.

Buttons and actions

"Voltar" (Back)
Returns to the list of flows.
Editor
Edit mode on the canvas.
"Execuções" (Runs)
Mode with the conversations that went through the flow in the last 24 hours.
"Avaliações" (Evaluations)
Mode with the sample conversations that run with every publication.
"Versão" (Version)
Version selector: choosing an old version asks whether you want to go back to it; choosing the live one offers to take it offline.
"Central de ajuda" (Help center)
Opens the guide for the "Base de conhecimento avançada" (Advanced knowledge base).
"Publicar" (Publish)Owner
Opens the publish dialog.
"Mais ações do fluxo" (More flow actions)
Opens the flow menu.
"Excluir fluxo" (Delete flow)
Opens the delete or archive dialog; then returns to "Fluxos" (Flows).
  • Path with the version (or "Rascunho" (Draft) and the number) and the selected node.
  • Badge "Alterações não publicadas" (Unpublished changes) or "Publicado" (Published) with the version.

Node list

Fields and filters

"Buscar nó" (Search node)
Search by name or description; opens all the groups.

Buttons and actions

"Favoritar" (Favorite)
Star on each node: adds it to or removes it from the "Favoritos" (Favorites) group.
"Favoritos" (Favorites)
Group with the favorited nodes (only appears when there are any).
"Gatilhos" (Triggers)
Group: "Mensagem do lead" (Lead's message), "Aviso do seu sistema" (Notice from your system), "Agenda" (Calendar) and "Evento no atendimento" (Event in the conversation). The flow's trigger is already on the canvas.
"IA" (AI)
Group: "Classificar intenção" (Classify intent), "Extrair campos" (Extract fields), "Gerar resposta" (Generate response) and "Resumir" (Summarize).
"Lógica" (Logic)
Group: "Condição" (Condition), "Esperar" (Wait) and "Dividir" (Split).
"Ações" (Actions)
Group: "Chamar ação" (Call action) and "Marcar no CRM" (Mark in CRM).
"Equipe" (Team)
Group: "Passar para a equipe" (Hand off to the team) and "Avisar a equipe" (Notify the team).
  • Drag a node onto the canvas, double-click it or press Enter to add it.

Canvas

  • The draggable nodes and the curved wires with an output label (yes, no, error, A, B) and the counts for the last 24 hours.
  • Connect an output to another node by pulling the wire; each output has only one wire.
  • Delete or Backspace removes the selected node (the "Início" (Start) node and the trigger cannot be removed).
  • At the foot of the canvas: how many nodes, who edited and when, and the "salvo há" (saved ... ago) of the autosave.

Canvas bar and test

Fields and filters

"Mensagem do lead para o teste" (Lead message for the test)
What the lead would say; Enter runs it. The last message is remembered.

Buttons and actions

"Enquadrar" (Fit to screen)
Adjusts the zoom to fit the whole flow.
"Aproximar" (Zoom in)
Zooms in.
"Afastar" (Zoom out)
Zooms out.
"Desfazer" (Undo)
Undoes the last change on the canvas.
"Testar com uma conversa" (Test with a conversation)
Opens the test box; during the test, it becomes "Rodando a conversa de teste…" (Running the test conversation…).
"Rodar o teste" (Run the test)
Runs the draft as a simulation: each node lights up along the path it went through and, at the end, a notice summarizes nodes, time and response. Nothing is sent, saved or billed.
"Cancelar" (Cancel)
Closes the test box.

Node inspector

Opens when you select a node; the fields change with the type.

Fields and filters

"Título do nó" (Node title)
The node's name on the canvas.
"Linha do canvas" (Canvas line)
The short description shown on the node.
"Intenções" (Intents)
"Classificar intenção" (Classify intent): the possible intents (Enter adds one); below the confidence threshold, it becomes "outro" (other).
"Confiança mínima" (Minimum confidence)
"Classificar intenção" (Classify intent) and "Extrair campos" (Extract fields): the AI's confidence threshold.
"Campos" (Fields)
"Extrair campos" (Extract fields): each field, its format and whether it is required.
"Se faltar, a IA pergunta" (If missing, the AI asks)
"Extrair campos" (Extract fields): the question for the lead when a piece of data is missing; the flow waits for the answer.
"Instrução" (Instruction)
"Gerar resposta" (Generate response): what the response should say; it uses the persona and the approved facts.
"Para quem" (For whom)
"Resumir" (Summarize): the team (goes with the handoff) or the CRM (note on the record).
"Condição" (Condition)
The rules about intent, confidence, extracted fields, action response, system notice and lead; yes and no outputs.
"Combinar" (Combine)
With more than one rule: all must hold (and) or any one must hold (or).
"Esperar por" (Wait for)
A time or only the lead's reply.
"ou a resposta do lead, o que vier primeiro" (or the lead's reply, whichever comes first)
"Esperar" (Wait): continues when the lead replies, even before the time is up.
"Caminho A recebe" (Path A receives)
"Dividir" (Split): the percentage for path A; the same lead always lands on the same side.
"Ação" (Action)
"Chamar ação" (Call action): a published action; if the system does not respond or the lookup cannot run (the same limits as actions in the conversation), it follows the "erro" (error) wire.
"O que fazer" (What to do)
"Marcar no CRM" (Mark in CRM): "Pôr a etiqueta" (Add the tag), "Tirar a etiqueta" (Remove the tag) or "Mover para a etapa" (Move to stage).
"Etiqueta" (Tag)
"Marcar no CRM" (Mark in CRM): the tag (or the "Etapa do Funil" (Pipeline stage), when moving).
"Fila" (Queue)
"Passar para a equipe" (Hand off to the team): the queue; it carries the summary and the fields, and the lead sees the agent's name.
"Aviso no sino" (Bell notification)
"Avisar a equipe" (Notify the team): the message in the bell, without taking the conversation away from the AI.
"Evento do seu sistema" (Event from your system)
"Aviso do seu sistema" (Notice from your system) trigger: the event from the "Webhooks" tab.
"Dias" (Days)
"Agenda" (Calendar) trigger: the days of the week.
"Hora (no fuso da conta)" (Time (in the account time zone))
"Agenda" (Calendar) trigger: the time.
"Para os leads da etiqueta" (For leads with the tag)
"Agenda" (Calendar) trigger: who receives it.
"Quando" (When)
"Evento no atendimento" (Event in the conversation) trigger: "O lead mudou de etapa no Funil" (The lead changed stage in the pipeline) or "O lead ficou quente" (The lead became hot).
"Trocar gatilho" (Change trigger)
On the trigger: changes the type in place; the output wire stays connected. In a published flow, the new trigger only takes effect on publishing.

Buttons and actions

"Fechar" (Close)
Closes the inspector.
"Regra" (Rule)
In "Condição" (Condition), adds a rule.
"Tirar esta regra" (Remove this rule)
In "Condição" (Condition), removes the rule.
"Abrir a ação" (Open the action)
In "Chamar ação" (Call action), opens the editor of the chosen action.
"Testar só este nó" (Test only this node)
In "Chamar ação" (Call action), opens the action's test.
"Excluir nó" (Delete node)
Removes the node and its wires (does not appear on the "Início" (Start) node or the trigger).
  • "Modelo" (Model): in AI nodes, the account's AI or, on Enterprise, the company's model set in "Roteamento" (Routing) → "Construtor de fluxo" (Flow Builder).
  • Last 24 hours: the entries into the node and, in the condition, how many went to yes and how many to no.
  • Notice with what is missing before you can publish.

"Execuções" (Runs) mode

Buttons and actions

"Todas" (All)
Shows all the conversations from the last 24 hours.
"Com erro" (With error)
Only those that ended with an error.
  • Each conversation with the lead, the outcome, the node-by-node path and the duration; clicking returns to the editor with the path lit up on the canvas.

"Avaliações" (Evaluations) mode

Fields and filters

"Nome curto" (Short name)required
The name of the sample conversation.
"Conversa de exemplo" (Sample conversation)required
What the lead says.
"Esperado (na ordem)" (Expected (in order))required
The steps the flow must perform, in this order; it may perform others in between. "Extrair campos" (Extract fields) only counts when the flow asks the lead for what was missing.

Buttons and actions

"Conversa de exemplo" (Sample conversation)
Opens the dialog for a new sample conversation.
"Rodar de novo" (Run again)
Runs all the evaluations; each result appears when it finishes.
"Editar" (Edit)
Edits the sample conversation.
"Excluir ‹nome›" (Delete ‹name›)
Asks, then permanently deletes the sample conversation.
"Salvar" (Save)
Saves the sample conversation.
"Excluir" (Delete)
Confirms the deletion of the sample conversation.
  • Table: "Conversa de exemplo" (Sample conversation), "Esperado" (Expected), "Obtido" (Obtained) and "Resultado" (Result) (passed, failed or not run yet). A failure blocks the "Publicar" (Publish) button.

Publish and version dialogs

Fields and filters

"Código de verificação" (Verification code)
When the flow calls an action that writes.

Buttons and actions

"Publicar" (Publish)Owner
Publishes the version; the AI uses it starting with the next message.
"Publicar assim mesmo" (Publish anyway)Owner
With a failing evaluation, publishes anyway and it is logged.
"Corrigir antes" (Fix first)
Closes so you can fix it (with a failing evaluation).
"Tirar do ar" (Take offline)Owner
On the version in use, takes the flow offline and frees the trigger for another flow.
"Voltar para esta" (Go back to this one)Owner
The old version becomes the next one, published now, and replaces the draft.
  • The dialog runs the evaluations when it opens ("Rodando as avaliações: ‹n› de ‹total›…" (Running the evaluations: ‹n› of ‹total›…)) and shows what changed.
  • If the trigger already has another published flow, the dialog says which one: take that one offline to publish this one.

Screen states

Loading
Skeleton placeholders for the top bar and the canvas.
Nothing here yet
Runs: "Nenhuma conversa passou por aqui ainda" (No conversation has gone through here yet). Evaluations: "Nenhuma conversa de exemplo" (No sample conversation).
If something goes wrong
"Não foi possível abrir este fluxo" (Could not open this flow) (it may have been deleted or the connection dropped). A failure to save appears in the canvas footer, which tries again.
On mobile
"Para editar, use o computador." (To edit, use a computer.) You can view the flow, the runs and test with a conversation.

"Webhooks de entrada" (Inbound webhooks)

The "Webhooks de entrada" (Inbound webhooks) screen is for giving your system a signed endpoint to notify the platform, naming each event that arrives and building rules like "when X arrives, for the right leads, do Y".

Address in the dashboard: /app/base-avancada/webhooks

The "Webhooks de entrada" (Inbound webhooks) screen in the demo account, with sample data and blurred values.

How to get there: Menu "Base avançada" (Advanced base) → Webhooks, or the shortcut "Webhooks de entrada · na Base avançada" (Inbound webhooks · in Advanced base) on the "Integrações" (Integrations) screen.

Endpoint for your system to send notices

Buttons and actions

"Copiar o endereço" (Copy the address)
Copies the endpoint to register in your system.
"Mostrar" (Show)
Reveals the signing secret so you can copy it (it is logged).
"Ocultar" (Hide)
Masks the secret again.
"Copiar o segredo" (Copy the secret)
Copies the revealed secret.
"Trocar" (Change)Owner
Asks "Trocar o segredo?" (Replace the secret?): the new one is valid right away and the current one keeps working for 24 hours.
"Trocar agora" (Replace now)
Confirms the change and shows the new secret.
"Invalidar o antigo agora" (Invalidate the old one now)Owner
With the previous secret still valid, asks and cuts it off immediately (use it if it leaked).
"Invalidar agora" (Invalidate now)
Confirms: notices signed with the old secret start being rejected.
"Mais ações do endereço" (More address actions)
Opens the endpoint menu.
"Arquivar endereço" (Archive address)
In the card menu, when there are already deliveries in the history: opens the dialog and the endpoint goes to the archive.
"Excluir endereço" (Delete address)
In the card menu, when no notice has ever arrived: opens the dialog and deletes it permanently.
"Criar endereço novo" (Create new address)Owner
With the endpoint archived, generates another endpoint and another secret. The named events and the rules (turned off) remain; turn back on the ones you want.
  • "Situação" (Status): "Recebendo" (Receiving), "Último há tanto tempo" (Last one X ago), "Sem avisos ainda" (No notices yet) or "Arquivado" (Archived).
  • Tip with the signature headers: X-Webhook-Assinatura (HMAC SHA-256 of "timestamp.id.corpo" (timestamp.id.body)), X-Webhook-Timestamp and X-Webhook-Id.
  • In an account with its own brand and no configured domain, the endpoint only appears after the dashboard domain is ready.

Events

What your system has already sent, each one with a name in Portuguese.

Fields and filters

"Chave do evento" (Event key)required
What goes in the "evento" (event) field of the body (letters, numbers, dot, dash or underscore).
"Nome em português" (Name in Portuguese)required
How the event appears on the screen.
"Ícone" (Icon)
"Cobertura" (Coverage), "Agenda" (Calendar), "Pagamento" (Payment), "Informação" (Information), "Pedido" (Order), "Cliente" (Customer), "Aviso" (Notice), "Etiqueta" (Tag) or "Documento" (Document).

Buttons and actions

"Regra" (Rule)
Opens a new rule (it needs at least one event).
"Evento" (Event)
Opens "Cadastrar um evento" (Register an event), to register the key before the system sends it.
"nomear" (name)
On the event "Sem nome ainda" (No name yet), opens "Nomear o evento" (Name the event).
"Salvar" (Save)
Saves the event.
"Cancelar" (Cancel)
Closes without saving.
  • Clicking an event shows its rule on the right; each one shows how many arrived this month.

Latest deliveries

  • Each call to the endpoint: "aceita" (accepted) (with what the rule did), "recusada" (rejected) (invalid signature, outside the window, burst) or "repetida" (duplicate), with the time.
  • A notice that did not reach some lead shows as an alert ("alguns leads não receberam" (some leads did not receive it)) or in red ("não entregue" (not delivered), none received), with the reason and how many: no WhatsApp connection, text blocked by the check, send failure, no balance, missing template data. Anyone who did not receive it is not tried again in the same delivery; if a whole batch fails to go out, the rest of the list stays as not attempted.

Event rule

"Quando o evento chegar" (When the event arrives), "Para os leads de uma etiqueta" (For the leads with a tag), "Faça os passos" (Do the steps).

Fields and filters

"Etiqueta do CRM" (CRM tag)
Leads with this tag in the "Base de contatos" (Contact base) receive the notice.
"Campo do lead" (Lead field)
The lead field used in the filter.
"Comparação" (Comparison)
is one of, equals or exists.
"Campo do aviso" (Notice field)
The field in the body of the notice, with suggestions from the last one received; a list ends with "[]".
"Frase do fato" (Fact phrase)
In the "Propor fato para aprovar" (Propose a fact for approval) step, the phrase with the notice fields in braces; it goes into the "Memória" (Memory) queue.
"Modelo aprovado da Meta" (Meta-approved template)
Outside the 24 hours, the template used; without a template, the notice is not sent outside the window. The template's cost appears on the option and comes out of the balance.
"De onde vem a variável ‹n›" (Where variable ‹n› comes from)
The lead's first name or a field from the notice; if the notice does not bring the data, the template is not sent to that lead.
"No máximo 1 aviso por lead a cada" (At most 1 notice per lead every)
7, 14 or 30 days.
"Só das" (Only from)
The start time from which notices go out.
"às" (to)
The end time; a notice that arrives outside the hours waits for the next opening.

Buttons and actions

"Editar" (Edit)
Opens the rule for editing.
"Excluir regra" (Delete rule)Owner
Asks "Excluir esta regra?" (Delete this rule?); notices already sent stay on record.
"Regra ativa" (Active rule)
Switch that turns the rule on or off; the rule is created turned off.
"Escolha o evento" (Choose the event)
Under "Quando" (When), chooses the event that triggers the rule.
"Escolha a lista" (Choose the list)
Under "Para" (For), opens the "Base de contatos" (Contact base) tag that receives the notice.
"sem filtro" (no filter)
Opens the optional filter by "Campo do lead" (Lead field).
"Usar o filtro" (Use the filter)
Applies the filter.
"Tirar o filtro" (Remove the filter)
Removes the filter.
"Adicione o que fazer" (Add what to do)
Opens the steps: "Propor fato para aprovar" (Propose a fact for approval), "Mandar mensagem ao lead" (Send a message to the lead), "Tirar da lista" (Remove from the list), "Marcar campo do lead" (Mark a lead field).
"Tirar este passo" (Remove this step)
Removes the step.
"Editar limites" (Edit limits)
Opens the rule's frequency and time-of-day limits.
"Pronto" (Done)
Closes the open box.
"Salvar" (Save)
Saves the rule; the new rule is created turned off.
"Cancelar" (Cancel)
Discards the edit.
  • Within the 24 hours, the AI writes with the account's persona; outside, it uses the approved template.
  • "Quem já recebeu" (Who already received it) (‹n›): opens the list of notified leads, with the date and whether it was an AI message or a template.

Test the rule

Fields and filters

"Corpo de exemplo" (Sample body)
The JSON of the simulated notice, filled in with the last notice received.

Buttons and actions

"Enviar evento de teste" (Send test event)
Simulates the notice: shows whether the signature is valid, how many leads would receive it inside and outside the 24 hours, how many were skipped by the limit and the proposed fact. Nothing is sent.

Screen states

Loading
Skeleton placeholders for the endpoint, the events and the rule.
Nothing here yet
"Nenhum evento recebido" (No event received) (register the endpoint in your system, or the key first), "Nenhuma entrega ainda." (No deliveries yet.) and "Nenhuma regra ainda" (No rules yet).
If something goes wrong
"Não foi possível abrir os webhooks" (Could not open the webhooks), saying nothing changed, with the try-again button.
Archived endpoint
The system can no longer send notices. The rules stay turned off and come back when you create a new endpoint; the old deliveries stay in the list.
New endpoint, no notice yet
"Aguardando o primeiro aviso" (Waiting for the first notice) in place of "Recebendo" (Receiving).

Step by step

How to approve the facts the AI learned from conversations

  1. Open "Base avançada" (Advanced base) → "Memória da empresa" (Company memory); the "Para revisar" (To review) tab brings the facts proposed by the Curator.
  2. Read the fact's source on the card (the lead's question and the team's answer) and check the confidence.
  3. Adjust the "Categoria" (Category) and the "Validade" (Validity) if needed; to correct the text, use "Editar" (Edit) and then "Pronto" (Done).
  4. Click "Aprovar" (Approve) (or press A). If the fact contradicts another one, the button becomes "Aprovar e substituir" (Approve and replace).
  5. To discard it, use "Recusar" (Reject) (or press R). Move between the cards with J and K.

How to sync your system's catalog with the base

  1. In "Base avançada" (Advanced base) → "Ações" (Actions), click "Criar sincronização" (Create sync).
  2. In step 1, give the "Nome da conexão" (Connection name), enter the Token and click "Guardar no cofre" (Store in vault).
  3. In step 2, paste the list's "Endereço" (Endpoint) and click "Testar a lista" (Test the list).
  4. In step 3, give each column the "Nome que a IA lê" (Name the AI reads) and the "Papel" (Role) (at least one "Chave" (Key) and one "Nome" (Name)).
  5. Choose the destination ("Catálogo de produtos" (Product catalog) or "Base de conhecimento" (Knowledge base)), the frequency and what to do with an item that disappeared.
  6. The Owner clicks "Ligar e sincronizar agora" (Turn on and sync now) and follows the first run on the sync screen.

How to create an action that queries your system during the conversation

  1. In "Ações" (Actions), use "Usar" (Use) on a template for your industry or "Criar" (Create) on the "Do zero" (From scratch) card.
  2. In "Conexão com o seu sistema" (Connection to your system), choose the "Método" (Method), fill in the "Endereço" (Endpoint) with the fields in braces and store the token.
  3. In "Entrada" (Input), use "Campo" (Field) for each piece of data the system needs and mark what is "Obrigatório" (Required).
  4. Click "Testar" (Test) to read the real response and mark, under "Resposta" (Response), what the AI "usa" (uses) and what stays "oculto" (hidden).
  5. Under "Quando usar" (When to use), write the "Descrição" (Description), choose the intents and add phrases that should and should not trigger the call.

How to test and publish an action

  1. In the action editor, click "Testar" (Test).
  2. Fill in the fields and the "Fala do lead" (Lead's message) and click "Executar teste" (Run test).
  3. Check the request, the response and "O que a IA diria" (What the AI would say); if it is right, click "Salvar como avaliação" (Save as evaluation).
  4. The Owner clicks Publicar v‹n›: the evaluations run and the dialog shows what changes.
  5. Click "Publicar" (Publish) (or "Publicar assim mesmo" (Publish anyway), if an evaluation failed). An action that writes asks for the "Código de verificação" (Verification code).

How to notify leads when your system sends a webhook

  1. In "Base avançada" (Advanced base) → Webhooks, click "Copiar o endereço" (Copy the address) and register it in your system; use "Mostrar" (Show) to copy the signing secret.
  2. When the first notice arrives, click "nomear" (name) on the event and give the "Nome em português" (Name in Portuguese).
  3. Click "Regra" (Rule), choose the event, the list under "Escolha a lista" (Choose the list) and, under "Adicione o que fazer" (Add what to do), the steps.
  4. Choose the "Modelo aprovado da Meta" (Meta-approved template) for those outside the 24 hours and adjust it under "Editar limites" (Edit limits).
  5. Click "Salvar" (Save), test with "Enviar evento de teste" (Send test event) and turn on the "Regra ativa" (Active rule) switch.

How to build an AI flow and test it with a conversation

  1. In "Base avançada" (Advanced base) → "Fluxos" (Flows), click "Novo fluxo" (New flow), give it a "Nome" (Name), choose the trigger and click "Criar e abrir o editor" (Create and open the editor).
  2. Drag the nodes from the list onto the canvas and connect the outputs to the next nodes.
  3. Select each node and fill in the inspector (intents, fields, instruction, action, condition).
  4. Click "Testar com uma conversa" (Test with a conversation), write the message and click "Rodar o teste" (Run the test); watch the nodes light up.
  5. In "Avaliações" (Evaluations), create sample conversations; then the Owner clicks "Publicar" (Publish).

How to replace the spreadsheet with sync

  1. In the spreadsheet notice (in the "Base de conhecimento" (Knowledge base) or when creating the sync), click "Ver a comparação" (See comparison).
  2. Check the "Comparação das colunas" (Column comparison): what matches, the prices that changed and the columns that become facts.
  3. The Owner clicks "Trocar pela sincronização" (Switch to sync); the spreadsheet is only removed if the first run finishes well.
  4. To postpone, use "Manter a planilha por enquanto" (Keep the spreadsheet for now): the sync stays as a draft.
  5. If you need to undo it later, use "Voltar a planilha" (Back to the spreadsheet) in the sync summary, while it is still kept.

How to delete or archive an action, a flow or a connection

  1. Open the card menu ("Mais ações" (More actions)) and choose "Excluir ação" (Delete action), "Excluir fluxo" (Delete flow) or "Excluir conexão" (Delete connection); in the editor, the button is at the end of the page or in the top menu.
  2. Read the dialog: what never ran is deleted permanently; what has history goes to the archive.
  3. If something still uses the item (a published flow, an action), take it offline or delete it first.
  4. Confirm with "Excluir" (Delete) or "Arquivar" (Archive). Archiving what has already run is for the Owner only.

Frequently asked questions

Who can publish an action or a flow?

Only the account Owner (the person responsible). The Admin creates, edits and tests everything and gets it ready; in the publish dialog, they see that only the account manager publishes.

Does editing a published action change what the AI is using?

No. The changes stay as "Alterações não publicadas" (Unpublished changes) and the AI keeps using the published version until the next publication.

Why is the Publish button disabled?

Because nothing has changed since the published version, something is still missing, the evaluations are running, another flow already uses the same trigger or, for an action that writes, two-step verification is not turned on.

Does testing an action or a flow send a message to the lead?

No. The action test calls your system for real, but nothing goes to any lead. The flow test runs as a simulation: nothing is sent, saved or billed.

Can sync change data in my system?

No. Sync only reads the list (always GET); the token stays in the vault and never appears again.

Can I have two published flows with the same trigger?

No. Only one flow per trigger is live. To publish another one, take the current one offline through the version selector, under "Tirar do ar" (Take offline).

Can I edit a flow from my phone?

No. On a phone you can see the flow, the runs and test with a conversation; to edit, use a computer.

Where can I see each time the AI queried my system?

In the "Execuções" (Runs) tab: each call with the action, the version, the conversation, the masked input, the result and the time. Use "Exportar" (Export) to download the spreadsheet.

Who can see the masked personal data in "Execuções" (Runs)?

The Owner and the Admin click the input to see the full value, and each view is logged.

Help center guide

"Base de conhecimento avançada" (Advanced knowledge base)

The module that learns from conversations ("Memória da empresa" (Company memory), with your approval), keeps the base up to date by pulling the list from your system on its own, queries your system on the spot, receives its notices through webhook, and follows flows that you design node by node.

The "Base de conhecimento" (Knowledge base) you already have answers with what you wrote. The "Base de conhecimento avançada" (Advanced knowledge base) goes further: it learns from your team's day-to-day work and looks up in your system the list that changes all the time (catalog, prices, service table). It is a module: you turn it on in "Módulos" (Modules), in the menu, and turn it off whenever you want. What you taught it is kept.

"Ativar" (Activate)

  1. Open "Módulos" (Modules): In the menu, under "Conta" (Account). The highlighted card is the "Base de conhecimento avançada" (Advanced knowledge base).
  2. Activate: On the module page, "Ativar" (Activate). The "Base avançada" (Advanced base) is included in your plan: there is no trial or monthly fee. Only the account owner can activate it; the manager sees the explanation in place of the button.
  3. Start with "Memória" (Memory): The "Curador de conhecimento" (Knowledge Curator) already starts reading the conversations. Within an hour, the first facts appear for you to approve.

What is included

"Mensalidade" (Subscription)
There is none. The "Base avançada" (Advanced base) is included in your plan.
Queries
No charge and no allowance per cycle. The safety limits on actions still apply (see "Consultar na hora" (Query on the spot)).
Items per sync
Up to 100 thousand.
Messages outside the 24 h window
The notice uses a Meta-approved template and carries Meta's cost, as it does today, charged to the balance.
"Desligar" (Turn off)
Turns off immediately. Nothing is charged and what you taught it is kept.

"Memória da empresa" (Company memory)

The "Curador de conhecimento" (Knowledge Curator) agent reads the conversations every hour and proposes facts with their source: the question the AI could not answer that went to the team, the service agent's reply, and what the Auditor blocked for lack of a source. Nothing goes in without you or a manager approving it. An approved fact applies from the next message on, both for the AI to answer and for the Auditor to check.

Approve with the keyboard
In the queue, A approves, E edits, R rejects, and J and K move from one card to another.
"Categoria" (Category)
Those from your industry, plus "Outros" (Other). The Curator picks; you change it on the card.
"Validade" (Validity)
"Sem validade" (No expiration); "Até uma data" (Until a date) (the fact goes out of use on its own the next day); or "Revisar em 90 dias" (Review in 90 days) (it stays valid and shows up in "Para fazer" (To do) on that date).
"Renovar" (Renew)
On the "Vencidos" (Expired) tab, choose the new expiration and the fact applies again immediately.
Edit the approved fact
In the fact's drawer, "Editar" (Edit): the new text applies immediately and is kept in the history.
Contradiction
When the new fact contradicts an approved one, the button becomes "Aprovar e substituir" (Approve and replace): the old one is archived.

"Sincronizar com a base" (Sync with the base)

Under "Ações" (Actions), "Nova ação" (New action) and "Sincronizar com a base" (Sync with the base). The entire list from your system is pulled every so many hours and the catalog or the base updates itself. Use it for lists the AI consults all the time: product catalog, prices, service table.

  1. "Conexão" (Connection): Give the connection a name (it appears in notices, such as “Store system did not respond”) and store the token in the vault. It never appears again.
  2. "Lista" (List): The URL of the list and, if needed, where it is in the response. "Testar a lista" (Test the list) reads all the pages and shows how many items came back.
  3. "Campos" (Fields): Give each column a name in Portuguese and its role: "Nome" (Name), "Preço" (Price), "Estoque" (Stock), "Chave" (Key) or "Outro" (Other). Whatever is left "oculto" (hidden) does not reach the AI.
  4. "Destino" (Destination): "Catálogo de produtos" (Product catalog), with the collection, or "Base de conhecimento" (Knowledge base).
  5. "Frequência" (Frequency): Every 1, 6, or 12 hours, or once a day. The screen shows the upcoming runs and the month's forecast of queries.
  6. "Itens que somem" (Items that disappear): "Marcar como indisponível" (Mark as unavailable) or "Tirar da base" (Remove from the base), and the "Freio de segurança" (Safety brake).
How the AI will read it
The "Operador de ações" (Action Operator) agent rewrites each new or changed item in plain text, only once, and the preview shows the first three. Codes inside the text (such as L12, CX30 or 50MG) stay the same.
"Aguardando revisão do texto" (Awaiting text review)
The run does not wait for the rewrite: items go in right away with the text from your system, and the AI can already find them. The text review comes right after, up to 1,000 items per run; the rest is left for the next one. The screen shows how many are still waiting.
One list, one sync
The same list can only be connected to one sync, so the catalog does not end up duplicated. To switch, archive the old one before turning on the new one.
"Freio de segurança" (Safety brake)
If more than 20% of the items disappear in a run, nothing changes in the base and you decide: "Aplicar mesmo assim" (Apply anyway) or "Ignorar esta rodada" (Skip this round).
System down
The run fails, the AI keeps using the last good version, and we try again in 15 minutes; on the third failure you receive an email. "Tentar agora" (Try now) runs it immediately.
"Sincronizar agora" (Sync now)
Starts a run outside the schedule, with page-by-page progress shown on the button. Between one run and the next, wait 5 minutes: the screen shows the time when it becomes available again.
Item limit
100 thousand items per sync. Above that the run is rejected and the base stays as it was.

Switching over and going back to the spreadsheet

If you imported a spreadsheet into the "Base de conhecimento" (Knowledge base), the "Trocar pela sincronização" (Switch to sync) notice appears next to it, when creating the sync, and on the "Painel" (Dashboard) (when the file is more than 15 days old). "Ver a comparação" (See comparison) shows, column by column, what matches, the prices that changed, the new columns, and the ones that become facts for you to approve.

  • Yes: The spreadsheet stays in effect until the first sync finishes successfully; only then does it go away, and it is kept for 30 days.
  • Yes: If the first run errors out: nothing changes and you receive the notice.
  • Yes: "Manter a planilha por enquanto" (Keep the spreadsheet for now) (account owner only) leaves the sync as a draft.
  • Yes: "Voltar a planilha" (Back to the spreadsheet), in the sync, returns the file to the base and pauses the sync while the file is kept: its items and offers leave the search and the catalog. "Retomar" (Resume) brings both back.

"Consultar na hora" (Query on the spot)

Under "Ações" (Actions), "Nova ação" (New action) and "Consultar na hora" (Query on the spot). The AI asks your system during the conversation: coverage at an address, order status, the 2nd copy of a boleto. Start from a template for your industry (you only point to your system's URL) or from scratch, with any API that responds in JSON.

  1. "Conexão" (Connection): "Método" (Method) (GET to query, POST to write), the URL with the fields in braces, such as ?cep={cep}&numero={numero}, and the token, which is stored encrypted in the vault. "Vai chamar" (Will call) shows the URL with sample values. "Tempo limite" (Timeout) of 5, 8, or 15 seconds.
  2. "Entrada" (Input): What the AI collects from the lead: the field, the format (CEP, number, CPF, date…), the phrase it uses to ask, and whether it is required. It never makes a call with an empty required field: it asks first. In addition, {telefone_do_lead} and {nome_do_lead} are filled in automatically with the lead from the conversation, never with what someone types.
  3. "Resposta" (Response): Appears after the first test. For each field that your system returns, "usa" (uses) or "oculto" (hidden). What is hidden the AI never sees, and neither the token.
  4. "Quando usar" (When to use): The description, the phrases that should and should not call the action, and the lead's intents (question about product, price, purchase, schedule, support). Outside those intents the AI doesn't even consider the action.
  5. "Testar" (Test): The call is real, to your system, and nothing goes to any lead or counts as a query. You see the request (with the token hidden), the response, and "O que a IA diria" (What the AI would say), in a simulated conversation. "Salvar como avaliação" (Save as evaluation) saves the conversation as an example. An action that writes also really writes during the test: only the account owner tests it, confirming they understand this and with the 2-step code.
  6. "Publicar" (Publish): Only the account owner publishes. The evaluations run again against your system (read-only) and the dialog shows what changed since the previous version.
Versions
Each publication becomes a version; the AI uses the published one until the next. Editing does not change what is live ("Alterações não publicadas" (Unpublished changes)). Under "Versões" (Versions), "Voltar para esta" (Go back to this one) publishes a copy of the old version as the next one.
"Avaliações" (Evaluations)
Sample conversations with the expected response: it calls, it doesn't call, or it asks for a field. With one failing, only the account owner can publish, using "Publicar assim mesmo" (Publish anyway), and it is logged.
An action that writes
Before each call the AI asks the lead for confirmation with the data it will use; it only calls after the yes. Publishing requires the code from the account owner's two-step verification (each code is valid once; 5 attempts every 15 minutes). An evaluation only calls GET actions. Each write carries the Idempotency-Key header, the same one for the same confirmation: if the lead's message arrives again, your system recognizes the key and does not write twice.
Personal data by ID document
An action that shows data about whoever owns a CPF or CNPJ needs more than the document: anyone can type in someone else's CPF. Send {telefone_do_lead} along with it (the templates already do) and have your system CHECK that the phone belongs to the account holder before responding. In the same conversation, the AI queries at most 2 different documents in 24 hours; on the third, it hands the conversation to the team.
"Limites" (Limits)
20 calls per minute per lead and 200 per minute in total on each action, and 10 thousand per month. Above that the action does not run and the conversation carries on as if your system were down; the refused call appears in "Execuções" (Runs).
Lead ready to buy
When the lead wants to buy and has already given everything the action asks for, the AI queries first, responds with the result, and hands the conversation to the team in the same message. On an action that writes, it asks for confirmation first. A request to talk to a person triggers the handoff immediately.
"Execuções" (Runs)
Each call, with the action and version, the conversation, the input, the result, the time, and the cost. Personal data appears masked (free text shows only the first 3 letters); a manager clicks to reveal it, and that is logged. "Exportar" (Export) downloads the spreadsheet with the same filter. Kept for 90 days; deleting the conversation or forgetting the lead deletes their runs.
Query
Each call that gets a response counts as 1 query, at no charge on your plan. Failures and timeouts do not count.
If your system goes down
The AI doesn't make things up: it says it will confirm and hands the conversation to the team, with the reason. The same applies when the action doesn't run because of a limit. The alert appears in "Visão geral" (Overview).

"Webhooks de entrada" (Inbound webhooks): notices from your system

Under Webhooks, your account gets its own URL and a secret; with a "Domínio próprio" (Custom domain) in the dashboard, the URL uses that domain. Your system sends a notice (a JSON) to that URL when something happens: fiber reached a neighborhood, a payment was confirmed, an installation was scheduled. Each notice becomes an event, which you name in Portuguese, and each event can have a rule: when it arrives, for the right leads, do this.

  1. Register the URL in your system: "Copiar" (Copy) next to the URL. The secret is masked: "Mostrar" (Show) reveals it for copying (this is logged) and "Trocar" (Change) generates another. The previous secret stays valid for 24 hours, so your system can switch without stopping; "Invalidar o antigo agora" (Invalidate the old one now) cuts it off immediately, if it leaked.
  2. Sign each notice: Three headers: X-Webhook-Timestamp (the time in seconds, 5-minute window), X-Webhook-Id (one ID per notice; the same ID within 24 hours is ignored) and X-Webhook-Assinatura, the HMAC SHA-256 of the secret over timestamp.id.corpo. In three lines: ts = agora(), assinatura = hmac_sha256(segredo, ts + "." + id + "." + corpo), send the three headers with the JSON. Body up to 256 KB, 60 notices per minute.
  3. Name the events: The first notice for each key (cobertura.disponivel) appears under "Eventos" (Events) as "Sem nome ainda" (No name yet). "nomear" (name) gives it a name in Portuguese and an icon; "+ Evento" (+ Event) registers the key before the system sends it.
  4. Build the rule: "Quando" (When) the event arrives, "Para" (For) the leads with a tag from the "Base de contatos" (Contact base) (with an optional filter: a lead field equal to, within, or existing in the notice), "Faça" (Do): propose a fact for the "Memória" (Memory), send a message to the lead, remove from the list, set a field. The rule is created off; the switch turns it on.
  5. Test before turning it on: "Enviar evento de teste" (Send test event) simulates with the sample body: how many leads would receive it, how many inside and outside the 24 hours, how many skipped by the brake. Nothing is sent.
Inside and outside the 24 h
A lead who wrote in the last 24 hours receives a message written by the AI with the account's persona and the notice as a fact (the Auditor checks it first). Outside the window, WhatsApp only accepts a Meta-approved template: choose the template in the rule and say where each variable comes from (a field from the notice or the lead's first name): filling is direct, without AI, and if the notice does not carry the data, the template is not sent to that lead. Without a template, a lead outside the 24 h does not receive it. Before each batch, the expected cost is checked against the balance and the spending cap. The template cost is charged by category, from the balance.
Brake and schedule
"No máximo 1 aviso por lead a cada" (At most 1 notice per lead every) 7 days (or 14, or 30) and only between 8h and 20h, in the account's time zone; a notice that arrives at night waits for the next opening. 500 leads per notice and 2,000 notices per day per account. Anyone who opted out, was anonymized, is "Fora das campanhas" (Outside campaigns), has no legal basis, or is with an agent does not receive it. In each rule, "Quem já recebeu" (Who already received it) lists those who were notified.
Propose a fact for approval
The rule's sentence (“We have served the {bairro} neighborhood since {data}.”) goes into the "Memória" (Memory) queue with the source "Aviso do seu sistema" (Notice from your system), for you to approve. Nothing becomes an AI reply without approval.
Latest deliveries
Each call to the URL: accepted (with what the rule did), refused (invalid signature, outside the window, large body, burst) or repeated. When some lead on the list does not receive the notice, the row turns to a warning ("alguns leads não receberam" (some leads did not receive it)) or red ("não entregue" (not delivered), none received it), with the reason and how many: no WhatsApp connection, text blocked by the check, send failure, no balance, missing template data. Those who did not receive it are not retried in the same delivery; if a whole batch fails to go out, the rest of the list is left as not attempted, without calling the AI again. Too many wrong signatures get a 429 and do not take the correct notice offline. The rule's test example uses only the accepted notices. The notice body is stored encrypted and is only read by the rule.
The notice is data, not instruction
What comes in the JSON never commands the AI: it only uses price and terms that appear as numbers in the notice, and the Auditor blocks the rest.

"Fluxos" (Flows): the path the AI follows

Under "Fluxos" (Flows), you design node by node what the AI does when something happens. "Novo fluxo" (New flow) asks for a name and the trigger: the lead's message (runs before normal service), a notice from your system (once per notice, after the event's rules notify the leads), a recurring schedule, or a service event (the lead changed stage, became hot). The editor opens full screen: the node list on the left, the canvas in the middle, and the inspector for the selected node on the right.

AI nodes
"Classificar intenção" (Classify intent) (you list the intents; below the "Confiança mínima" (Minimum confidence) it becomes "outro" (other)), "Extrair campos" (Extract fields) (CEP, number, CPF…; if something is missing, the AI asks the lead and the flow waits for the reply), "Gerar resposta" (Generate response) (with the instruction, the persona, and the facts) and "Resumir" (Summarize) (for the team or for the CRM record).
"Lógica" (Logic)
"Condição" (Condition) (rules on the intent, the extracted fields, the action's response, the system notice, and the lead; outputs yes and no), "Esperar" (Wait) (a set time, the lead's reply, or whichever comes first; in a loop, the wait must be at least 60 minutes) and "Dividir" (Split) (A/B by percentage; the same lead always lands on the same side).
Actions and team
"Chamar ação" (Call action) uses a published action; if your system does not respond, the flow continues through the "erro" (error) output. Queries count and have the same limits as actions in the conversation: when the query cannot run, the flow also continues through the "erro" (error) output. "Testar com uma conversa" (Test with a conversation) does not count a query. An action that writes first asks the lead, with the data, and only calls after the yes (without the yes, nothing is written and the conversation goes back to normal service); for that reason it cannot be used in the "Aviso do seu sistema" (Notice from your system) trigger, which has no lead. "Marcar no CRM" (Mark in CRM) (tag, "Funil" (Pipeline) stage, field), "Passar para a equipe" (Hand off to the team) (with the summary) and "Avisar a equipe" (Notify the team) (in the bell, without taking it from the AI). "Segue o atendimento" (Continue service) returns the conversation to the usual AI: if the flow has already replied, its reply goes out and the usual AI only comes back on the next message.
LGPD and security
Before the flow replies, the AI checks the intent of the message: anyone who asks to leave becomes an opt-out immediately, and the consent notice from the first contact goes along with the flow's reply. If a node fails, the message continues through normal service and the run keeps the error. "Agenda" (Calendar), "Evento" (Event), and resumes do not contact anyone who opted out, lacks a legal basis, or is with an agent, and send at most 6 messages per lead in 24 hours.
One trigger per flow
Every flow starts with a trigger. To change it, swap the trigger in the inspector (the output connection stays attached). In a published flow, the new trigger only takes effect when you publish: until then, the live version keeps running on its own trigger. The other nodes are removed with Delete, Backspace or "Excluir nó" (Delete node), along with their connections.
"Testar com uma conversa" (Test with a conversation)
The canvas button runs the draft in simulation with the message you type: each node lights up as it is passed through and, at the end, a notice summarizes (nodes, time, and the response). Nothing is sent, saved, or charged; the query to your system is read-only and the action that writes is not called.
Publishing and versions
Only the account owner publishes, and only one flow per trigger is live. The sample conversations ("Avaliações" (Evaluations)) run when the dialog opens; a failing one blocks, unless the owner uses "Publicar assim mesmo" (Publish anyway), which is logged. An action that writes in the flow requires the 2-step code. The version selector goes back to an old version (it becomes the next one) and "Tirar do ar" (Take offline) frees the trigger.
"Execuções" (Runs)
The "Execuções" (Runs) mode of the editor lists the conversations that went through the flow in the last 24 hours, with the node-by-node path; clicking lights up the path on the canvas. On the canvas connections, the counts for the last 24 h.
On mobile
To edit, use a computer. On a phone you can see the flow, the runs, and test with a conversation.

Delete and archive

Everything you create can be removed from the screen: the ⋯ menu on the card or the button at the end of the edit page, for an action, flow, webhook URL, rule, sample conversation, and connection. The modal tells you beforehand what will happen:

  • Yes: Deleted permanently: what has never run (a draft with no runs, a sample conversation, a rule). A manager can do it.
  • Yes: Archived: what has history (a published action or one with runs, a flow with versions or runs, a URL with deliveries). It disappears from the list and stops running: the action leaves the Operator, the flow frees the trigger, the URL stops receiving, and the rules stay off. Runs, charges, versions, and audit trail stay. Account owner only.
  • Yes: An action used by a published flow cannot be removed: the modal lists the flows and you take them offline first. The same goes for a connection used by an action or sync.
  • Yes: Archived webhook URL: "Criar endereço novo" (Create new address) generates another identifier and another secret; the named events and the rules (off) remain, and you turn back on the ones you want. The old deliveries stay on the list, and the new URL appears as "Aguardando o primeiro aviso" (Waiting for the first notice) until the first one arrives.

Included in "IA própria" (Own AI)

On your account with "IA própria" (Own AI), the "Base avançada" (Advanced base) comes included in the size-based monthly fee: no trial, no separate monthly fee, and no per-query charge. Its agents — the "Curador de conhecimento" (Knowledge Curator), the "Operador de ações na conversa" (In-conversation Action Operator), the "Mensageiro de avisos" (Notice Messenger), and the "Construtor de fluxo" (Flow Builder) — run on your company's models, connected under "IA própria" (Own AI).

In an account with "IA própria" (Own AI):

On your company's model

The agents run on your company's model, chosen under "IA própria" (Own AI) → "Roteamento" (Routing): the "Curador de conhecimento" (Knowledge Curator) and the "Operador de ações" (Action Operator) on background tasks, the "Operador de ações na conversa" (In-conversation Action Operator), which decides the query and understands the lead's confirmation, the "Mensageiro de avisos" (Notice Messenger), which writes the message for the notice from your system, and the "Construtor de fluxo" (Flow Builder), which runs the AI nodes in the editor.