Skip to Content
This guide has been rewritten for the new Raion Hub.See what changed →
IntegrationsWhatsAppCapture leads from WhatsApp keywords

Capture leads from WhatsApp keywords

Turn a word someone sends you on WhatsApp into a lead with the right source attached, so you can tell the ad from the flyer from the walk-in. Setting up your first rule takes about five minutes.

Before you start — you need a WhatsApp number connected (see Connect your WhatsApp number). The tab itself opens for anyone who can reach the WhatsApp page, but saving a rule needs Lead Capture access on that number, so if a save fails with no obvious reason, ask a workspace owner to check Channel access.

A rule does one thing: when an incoming message matches your keyword, the person who sent it is captured as a lead with that keyword’s lead source on them. One extra rule — the catch-all — picks up everything no keyword matched.

Steps

Open the Lead capture tab

In the sidebar, under Automation, click Integrations, then the WhatsApp Business card, then the Lead capture tab.

You can also click Add in the top bar and choose Capture rule (Route incoming chats), which jumps to this tab and opens a new rule in one go. That shortcut does nothing while the page is still loading its numbers, or if no number is connected yet — wait a beat, or connect a number first.

Old bookmarks to the separate lead-capture page still work; they now forward here.

On a wide screen the list is on the left and the editor on the right. On a phone the list fills the width and the editor opens as a sheet from the bottom.

With more than one number connected, an account picker sits in the page’s own band. Rules belong to the number in that picker — switching it loads a different set of rules.

Add a rule

Click New rule, at the right-hand end of the row carrying the 2 rules chip. With no rules yet, the panel below offers Add your first rule, which opens the same editor.

**Add rule** stays greyed out until there is a lead source and either a keyword or a ticked catch-all.

The editor opens with Active already switched on, so the rule starts capturing as soon as you save it. Its hint says what switching it off does: Inactive rules stay saved but never capture.

Type the keyword

Keyword is required — the field is marked with a red asterisk — and its placeholder reads e.g. PRICING, DEMO. Under it, the only rule the app states about matching: Case-insensitive. Stored uppercased. So pricing, Pricing and PRICING are the same word to Raion Hub, and the rule is stored in capitals whichever way you typed it.

If you want two different words to feed the same lead source, add a rule for each.

Choose where the lead lands

Lead source is the source stamped on every lead this rule captures. Open it and pick one, or pick + Create new lead source to make one without leaving the page.

That swaps the dropdown for a name box — the placeholder suggests e.g. Facebook Ads — Spring Campaign. Type a name, then press Create (or Enter). The X beside it, or Esc, backs out without creating anything.

Two things can happen when you create one:

  • Created lead source "Spring Flyer" — a new source, now selected.
  • Using existing lead source "Spring Flyer" — a source with that name already existed in a different capitalisation, so Raion Hub reused it rather than making a near-duplicate.

The name in the toast is the one that was actually saved, and it may have been nudged to keep it unique — Website (1) rather than a second Website. Read it.

Leave the two checkboxes alone unless you need them

Directly assign captured leads to myself puts every lead this rule captures straight onto you. Its own note says it is on the way out: Being phased out — assignment will move to assignment automation, so prefer a distribution rule for new setups. For anything you are setting up now, leave it unticked and let your assignment rules do the distributing.

Catch-all (fires when no other keyword matches) turns this rule into the safety net. Ticking it clears the keyword and disables that field — the placeholder changes to *CAPTURE ALL* to say so. Use it once, for the people whose message matches none of your keywords.

Save it

Press Add rule. You get Rule created., the editor closes, and the list reloads from the server.

A finished rule reads as one line in the list: the toggle, the keyword in a code box (or a Catch-all chip), a Self-assign chip if you ticked that, and underneath Routes to Spring Flyer. A rule with no source set reads Routes to —.

To change one later, use the pencil — Edit rule — on its row. Saving gives Rule updated.

Switching a rule on and off

The toggle on each row saves by itself. There is no Save button, and you get Rule enabled. or Rule disabled. straight away. If it fails, the toggle flips back and says Failed to update rule.

A rule with no lead source cannot be switched on. Rather than failing, the editor opens so you can set the source. It looks like the toggle did the wrong thing; it didn’t — it is asking you for the missing piece. Set the Lead source, save, and the toggle behaves normally from then on.

Only one catch-all can be live

A catch-all decides where every unmatched message goes, so only one may be active at a time. Raion Hub does not refuse the second one — it offers to swap them.

Switch on a catch-all while another is live, and you get Replace the active catch-all? with Only one catch-all can be active at a time — it decides where every unmatched message goes. Beneath that it names the one being switched off, and closes with They stay saved and can be switched back on later. Press Replace to go ahead, or Cancel to leave things as they are.

If a workspace was set up before this check existed, it can still hold several live catch-alls. You will see a warning chip beside the rule count — 2 active catch-alls — and an amber banner telling you that only one can fire per message and which one wins is not predictable. Switch off all but the one you want.

Deleting a rule

Delete rule — the bin icon on the row — asks Delete this rule? and tells you what stops:

  • on a keyword rule: The keyword PRICING will stop capturing leads.
  • on a catch-all: This catch-all rule will be removed.

Delete confirms with Rule deleted.

A lead source that a capture rule points at cannot simply be deleted elsewhere in Raion Hub. When you try, the app counts what still depends on it and names the WhatsApp keyword among them. Delete the rule first, or point it at another source.

If something goes wrong

What you seeWhyWhat to do
The toggle opens the editor instead of switching onThat rule has no lead sourceSet Lead source, save, then use the toggle
Lead source is required.You saved without choosing a sourcePick one, or use + Create new lead source
Keyword is required (or mark as catch-all).The rule has neither a keyword nor a ticked catch-allType a keyword, or tick the catch-all box
Failed to save rule.The server refused the save. On a member account this is often the missing Lead Capture permissionAsk a workspace owner to check Channel access for that number
WhatsApp account not ready — try refreshing.The page had not finished loading the numberReload and try again
Failed to load lead-capture rules.Usually the selected number is not readyReload the page; if it persists, check the number is still connected
Failed to switch the catch-all over.The swap failed part wayReload and check which catch-all is live before trying again
Failed to delete rule.The server refused the deleteThe rule is still there — try again
Rules you made are missingThe list is per numberSwitch the account picker in the page band
Connect a WhatsApp account firstNo number is connectedPress Connect WhatsApp, which takes you to the Accounts tab
A chip reading 2 active catch-allsMore than one catch-all is live, from before the one-at-a-time checkSwitch off all but the one you want
A message came in and no lead was capturedNo keyword matched it and no catch-all is activeAdd a catch-all rule, or a keyword rule for that word
No way to reorder or search the rulesThere isn’t oneKeep the list short and the keywords distinct

Next

Last updated on