Configure Keyword Triggers

Map customer keywords and matching methods to approved response resources or flows.

What this guide helps you do

Map customer keywords and matching methods to approved response resources or flows.

Who should use it

Workspace owners, managers, automation users and authorized technical users responsible for AI configuration or customer workflows.

Before you begin

  • Use the correct workspace and minimum required role.
  • Use a business-controlled provider account where applicable.
  • Understand provider billing, usage and data settings.
  • Use fictional Pakistan test data.
  • Define human handover before enabling automatic replies or calls.

Main concepts and fields

Concept / FieldMeaning or Use
ExactWhole message matches.
ContainsKeyword appears anywhere.
Partial / FuzzyLimited typo tolerance.
Starts / Ends WithPosition-based match.
Response ResourceContent sent after match.

Step-by-step instructions

  1. Open Keyword Triggers.
  2. Add an action.
  3. Enter keyword variants.
  4. Choose matching method.
  5. Select response resource or flow.
  6. Add priority/conflict rule where available.
  7. Test matching and non-matching messages.
  8. Activate.

Test and verification

  1. Run one complete successful path.
  2. Run an invalid or failure path.
  3. Confirm fields, assignment and logs.
  4. Confirm human handover.

Common issues and solutions

IssueWhat to Check
Flow does not startActive status, channel, trigger and entry condition.
Wrong branchField type, stored value and condition order.
Repeated messagesLoop, retries, duplicate event and overlapping flows.
Action failsCredential, endpoint, schema and timeout.
Handover failsTeam, agent and permission.

Security, privacy, consent, cost and provider notes

  • AI-provider charges and Wemblo AI-action usage are separate controls.
  • Do not expose provider keys or customer data in screenshots, tickets or client-side code.
  • Use human review or handover for sensitive, private, regulated, urgent, high-value or final decisions.
  • Do not promise perfect accuracy or guaranteed business outcomes.

Last reviewed: