Skip to content

Actions ​

Actions are what the agent can do beyond replying: write data to the CRM, tag, create an opportunity, search the base. It decides on its own when to use each one, based on the conversation.

By the end of this guide you will know what each action does and which ones to turn on.

Turn on few, on purpose ​

Every action turned on goes into the description the agent reads in every message. Two consequences: it costs space, and the more similar options there are, the worse the choice between them.

The recommendation is to turn on what the service actually uses. Three to five actions cover most cases.

The catalog ​

Knowledge ​

Search knowledge base — searches the lookup sources linked to the agent. The search is semantic: it writes the question in natural language, the way the customer asked it, and can search several times with different wordings.

Without this action the sources aren't searched

Linking bases without turning on this action makes the agent ignore them completely.

Contact data ​

Update contact field — writes to the CRM what the customer said: name, email, phone, company, job title. It's what makes the conversation feed the record instead of getting lost.

Look up contact field — reads a field from the record. It lets the agent recover something the customer already said before, in another conversation.

Classification ​

Add tag — marks the contact with one or more tags, recording facts discovered in the conversation: decision_maker, accepted_meeting, has_pain_X. It's what allows filtering later in the inbox.

Remove tag — removes a classification that turned out to be wrong.

Register lead source — records where the lead came from (ad, campaign, website, referral) based on what they said. Use the name as the customer knows it: "Instagram Ads", "Black Friday campaign".

Pipeline ​

Create opportunity — opens a deal in the CRM with pipeline, stage, estimated value and title. For when the lead has been qualified and deserves to enter the pipeline.

Move stage — advances the lead's opportunity in the pipeline or takes it out ("Qualified", "Lost"), when it becomes clear the conversation has moved on.

Communication ​

Suggest meeting — sends the booking link configured in the agent so the customer can book a meeting. The agent doesn't need to know the URL; it comes from the configuration. Use it when the interest is confirmed.

Send email — sends an email to the lead's registered address. It's for what doesn't fit in the current channel: a proposal, a list of documents, a payment link.

Transfer to human — ends the agent's work and hands the conversation to a person.

Prefer Transfers for the predictable case

This action is the agent's decision, in the middle of the conversation. For situations you already know exist — after-sales, quotes, an irritated customer — use Transfers: there the destination is chosen by you, not by the model.

Your technical team's actions ​

Besides these, your account may have its own actions, created as HTTP functions — looking up an order in your ERP, checking stock, validating a CPF. They show up in the same list, with the name the team gave them.

How to know it worked ​

  • In the menu, Actions shows "N of M active".
  • In Test, the actions performed show up in gray lines between the messages: "searched Karat table", "recorded in the contact record".

Common problems ​

The agent doesn't search the base, even with the sources linked. Cause: Search knowledge base is off. How to check: open Actions and check the toggle. Solution: turn it on.

The agent created an opportunity in a conversation where it shouldn't have. Cause: the action is on and the criterion is up to the model. How to check: see in Test whether it creates it too early. Solution: write the criterion in the prompt ("only create an opportunity after confirming budget and timeline"), or turn off the action and create the opportunity through a transfer to a sector.

An action from the technical team doesn't show up. Cause: the function wasn't created or is inactive. How to check: the list of actions is built from the account's functions. Solution: ask the team to publish it.

GetRaze - AI-Powered Lead Generation