Skip to content
Small Business Chatbot Docs
Support Open the app

Actions across two messages

Set up one action that looks a record up and a second that changes it, so the customer confirms what the AI receptionist read back before anything changes.

What this does

A Conversation Action runs all its steps inside one reply. When the customer has to answer in between, set up two actions in Small Business Chatbot. The first looks the record up, and the AI receptionist reads it back. The second makes the change, and its When to use it says to run it only after the customer confirms.

Where
Conversation Actions › Your actions
Pattern
Look up, read back, confirm, then act
Uses
Two actions, linked by their instructions
Field First action: Find order Second action: Cancel order
When to use it "The customer wants to cancel an order. Ask for the order number and the email on the order first." "Run only after Find order has found the order in this conversation and the customer has said yes to cancelling it. Use the same order number and email."
Parameters order_number, email order_number, email
Steps One Send an API request step with the method GET A GET step that finds the order again, then a step with the method POST that cancels it
Only answer if customer_email matches email The same row, on the GET step
What the agent gets back status, total status
What to do with the result "Read the status and the total back to the customer. Ask if they want to cancel this order, and wait for their answer." "Tell the customer the order is cancelled."

The first action's result stays in the conversation, so the AI receptionist still has it when the customer answers.

Set it up

  1. Create the first action

    In the app, open Conversation Actions and click New action. Build the lookup as Connect any API describes, and add the Only answer if row from Verify the customer.

  2. End it with a question

    In What to do with the result, tell the AI receptionist to read the record back, ask the customer to confirm and wait for the answer.

  3. Create the second action

    Click New action again. In When to use it, name the first action and say the customer must have said yes.

  4. Check the customer again

    Give the second action the same parameters, and start it with the same lookup step and Only answer if row. The change then runs only for a record that matches.

  5. Add the change

    Click Add step, pick Send an API request, and set the method and address of the change, such as POST and https://shop.example.com/api/orders/{{parameters.order_number}}/cancel.

  6. Test each action

    Under Test, run the first action, then the second with a test order. A test of the second action makes the change for real.

  7. Try the whole exchange

    In Playground, ask to cancel an order and follow the conversation through both actions. To try it on the phone, call your number.

What keeps the change from running twice

  • Actions that change something run once per customer message and three times per conversation. Limits lists every limit.
  • The same action with the same details for the same customer message returns its first result. The request is sent once.
  • The AI receptionist is told to run an action once for the same request.

If something goes wrong

What you see Why What to do
The AI receptionist makes the change without asking The second action's When to use it doesn't say to wait for a yes, or the first action's What to do with the result doesn't ask the question. Write both as in the table above.
The AI receptionist says the team will follow up The conversation has reached its three runs of actions that change something. Your team finishes the request. The customer's details are in the conversation under Conversations.
Step 2, address: {{steps.find_order.entity_id}} is not available here. A value must be one of this action's parameters, a field kept by an earlier step, or a system value. The change step uses a field that the second action's own lookup step doesn't keep. Each action uses its own parameters and the fields its own steps keep. Add the field under Fields to keep on the lookup step of the second action.

Next steps