Skip to content

When the agent steps in ​

Triggers define what makes the agent start answering. They are in the Channel and triggers panel, below the channel banner.

By the end of this guide you will know how to check the right triggers, route messages by keyword and understand why the agent stops replying.

They add up ​

Check as many as you want: triggers stack up, and the agent steps in when any one of them happens. It isn't a choice between one and the other.

An agent can, at the same time, answer every incoming message, be fired by a webhook from the website and accept conversations transferred from another agent.

Message received ​

The most common trigger. When you turn it on, you choose between two modes:

Answer every message — anyone who writes in is answered.

Route by rule — the agent reads the text of the message and decides whether to answer, and where to send it. Each rule has three parts:

OperatorValueRoute to
containstarciso123this agent
keyword listquote, price, how muchSector · Sales

The available operators are contains, is exactly, starts with, ends with, keyword list and regex.

The destination is what makes routing useful: the rule can send the conversation straight to a sector, without going through the agent. It is the right mechanism for a business rule with an exact answer — more reliable than asking for it in the prompt.

What to do with whoever matches no rule ​

Below the rules there is a choice that changes everything:

  • go to this agent — the rules work as a fork. Whoever doesn't match is answered normally.
  • are not answered by the agent — the rules become a gate.

Gate mode leaves messages unanswered

In this mode, a message that matches no rule gets no automatic reply and no one is notified. It is only seen if someone opens the conversation in the panel. Use it only in a controlled test.

The legitimate use of the gate is to release the agent to a few people before opening it to everyone — a keyword agreed upon with the team.

Webhook ​

An external system sends a POST and the conversation starts with the payload data. It's for website forms, Make, RD Station and the like.

Checking the trigger isn't enough: click Configure and complete the four steps — generate the URL, capture a test submission, map the fields and review the variables.

Without mapping, the endpoint doesn't create leads

Without a generated URL and field mapping, the endpoint responds 200 listen_mode and processes no lead at all. It is listening mode, meant for capturing the sample — it is not operation.

Phone or email is required in the mapping: without one of the two there is no way to reach the lead.

After capturing the sample, the fields from your payload start showing up in the variable picker of the Prompt, with the test value next to them.

Transfer from another agent ​

Lets another agent hand the conversation over to this one. Without this trigger on, the transfer is silently ignored — the other agent tries to hand it over and nothing happens.

When it's on, choose what it does when receiving:

  • starts replying — speaks as soon as it takes over;
  • starts with its own opening line — says a sentence you define;
  • stays silent until the customer writes — takes over but doesn't interrupt.

When the agent stops ​

Below the triggers, a toggle: Stop when a human replies.

It applies to replies sent from GetRaze and from the channel's app — if someone on the team replies through WhatsApp on their phone, the AI pauses all the same. The pause applies only to that conversation; the others stay on automatic.

How to know it worked ​

  • The banner at the top of the panel describes the resulting behavior in one sentence.
  • In the menu, Channel and triggers has a ✓ and the summary shows the trigger count.
  • In Test, the agent replies to the first message.

Common problems ​

The agent doesn't reply to anyone, but everything is checked. Cause: gate mode is on and no message matches the rules. How to check: in Route by rule, see whether the final choice is set to "are not answered by the agent"; an amber warning appears when it is. Solution: switch back to "go to this agent", or review the words in the rules.

The webhook responds 200 and nothing happens. Cause: the field mapping is missing. How to check: open Configure on the webhook trigger — without mapping, the listen_mode warning appears. Solution: capture a test submission and map at least phone or email.

Another agent transfers and the conversation disappears. Cause: this agent doesn't have the transfer trigger on. How to check: in the source agent, the Transfers screen shows an amber warning naming the agents that don't accept incoming conversations. Solution: turn on the trigger here and save.

GetRaze - AI-Powered Lead Generation