Verify the customer
Add an Only answer if row so an action answers only when the record matches what the customer said, such as the email on an order.
What this does
An Only answer if row makes a Conversation Action check the customer before it answers. The step compares a field it got back, such as the email on an order, with what the customer said. When they differ, Small Business Chatbot tells the AI receptionist that nothing was found, the same answer it gets for a record that doesn't exist.
- Where
- Conversation Actions › an action › a Look up in a table or Send an API request step › Only answer if
- Rows on one step
- Up to 5, and every row must match
- Default
- No rows, so the step answers for any record it finds
What the check adds
Order 100482 belongs to Jane, whose email is [email protected]. Bob types order number 100482 and his own email, [email protected].
- A required
emailparameter makes the AI receptionist ask Bob for an email. A request that fetches an order by its number returns Jane's order whatever email Bob gave. - With the row Only answer if
customer_emailmatchesemail, the two emails differ. The AI receptionist tells Bob it could not find a match with those details.
When your own system does the comparison, such as a search filtered on both the order number and the email, the required parameters are enough and the row can stay empty.
Add a check
- Keep the field to check
In the action editor, open the step. On a Send an API request step, add the field under Fields to keep, such as
customer_email. On a Look up in a table step, tick its column under Columns to return. - Add the row
Under Only answer if, click Add a check.
- Fill in the row
Pick the field the step keeps, then the parameter it must match, then how the two are compared in the compare as list.
- Pick what the customer hears
Under What the agent gets back, tick the values for the reply, such as the status. The checked field can stay unticked. The check runs either way.
- Test both cases
Under Test, click Run once with matching details and once with a wrong email. The step shows Done, then Did not match.

While an action with an Only answer if row runs, customers see or hear only the action's own Status line, so a step's line never shows that an earlier step found the record.
Compare as
| Choice | What is ignored | Example that matches |
|---|---|---|
| Text | Upper and lower case, and spaces at the ends | [email protected] and [email protected] |
| Phone number | Everything except digits. The last 10 digits are compared. | +1 (613) 555-0142 and 6135550142 |
| Postal code or ID | Case, spaces and hyphens | k1a 0b1 and K1A0B1 |
| Number | Number formatting | 100 and 100.00 |
- A row passes when the two values are equal under its choice.
- An empty value on the record never matches.
- When the record holds a list, such as an order with two emails, one matching item is enough.
The caller's phone number
A row can also compare with The caller's phone number: the number a call or a text conversation comes from, as the phone carrier reports it. Picking it sets compare as to Phone number. The app shows this note beside it: "A caller's number can be faked. Use it to recognise a caller, not to release account details."
| The number can | The number cannot |
|---|---|
| Recognise a returning caller, fill in a form and pick the right record to look at | Prove who is calling. Before an action releases account details, add a row that compares something the customer says, such as the email or the postal code on the record. |
A website chat has no caller's number, so a row that compares with it finds no match there.
Use a key limited to what the action needs
- In the step's Credential, pick a key that can do only what the action does, such as read-only order access for a lookup.
- Under Fields to keep, keep only the fields the action needs. The rest of the reply is dropped.
- Under What the agent gets back, tick only what the customer should hear.
The cap on "not found" answers
An action with an Only answer if row or a Send an API request step gives 3 "not found" answers in one conversation. A wrong detail and a record that doesn't exist count the same. After the third, the action stops answering in that conversation: the AI receptionist says it cannot do this at the moment and offers to take the customer's details so your team can follow up. A lookup table step with no row gives 10.
If something goes wrong
| What you see | Why | What to do |
|---|---|---|
| Add a check is greyed out | The step keeps no field yet. | Add a field under Fields to keep, or tick a column under Columns to return. |
| Step 1: "Only answer if" uses "customer_email", which this step does not keep. | The field was taken out of the step after the row was added. | Keep the field again, or pick another field in the row. |
| Step 1: "Only answer if" must compare with one of this action's parameters or the caller's phone number. | The row's parameter was removed from the action. | Pick a parameter in the row's second list. |
| A test with the right details shows Did not match | The two values differ under the row's compare as choice, or the record's field is empty. | Remove the row and run the test to see the value the step keeps. Pick the choice that fits it, then add the row back. |