Your Rasa Mantle agent makes a booking when the customer taps a Yes button, then says “I haven’t booked it yet, and I need your confirmation first.” Claude never saw the tap. Here’s why that happens in Rasa Pro 3.22, and the one setting that fixes it.
What I Was Doing
I was building Part 8 of the Rasa Tutorial, where a banking agent books appointments with an adviser. Following Rasa’s Tool Constraints (opens in a new tab) guide, I made Rasa ask for confirmation before the book_appointment tool runs:
tool_constraints:
- book_appointment:
requires: >
session.book_appointment.branch
and session.book_appointment.topic
and session.book_appointment.day
requires_confirmation:
enabled: true
utter_for_confirmation: utter_ask_book_appointment_confirmation
utter_on_user_denial: utter_book_appointment_cancelled
I also gave the confirmation question Yes and No buttons with Rasa’s confirmation payloads, so a tap answers without a call to Claude:
utter_ask_book_appointment_confirmation:
- text: >-
Shall I book this appointment? Branch: {branch}. Topic: {topic}.
Day: {day}.
buttons:
- title: Yes, book it
payload: "set:session.system.confirmation=true"
- title: No, cancel
payload: "set:session.system.confirmation=false"
What I Expected
A tap on Yes, book it would book the appointment, send the booking confirmation from responses.yml, and then Rasa’s wrap-up question.
What I Got

The booking was made, with reference APT-7960, and Rasa sent the confirmation. Then Claude added its own message, listed the details again and asked:
I haven't booked it yet, and I need your confirmation first.
...
Shall I go ahead and book this appointment? (yes/no)
What I Checked
I switched the Inspector to Inspect and opened the LLM call that wrote that message. Its prompt ends like this, one message per line:
[user] Riverton Station, please. It's about a loan, and Tuesday suits me.
[system] A canned reply was already sent this turn. Do not repeat, summarize, or paraphrase it. Continue from there with whatever naturally comes next.
[tool] branch: set to 'Riverton Station'; topic: set to 'loan'; day: set to 'tuesday'
[tool] {"status": "awaiting_confirmation", "message": "Shall I book this appointment? Branch: Riverton Station. Topic: loan. Day: tuesday."}
[assistant] Shall I book this appointment? Branch: Riverton Station. Topic: loan. Day: tuesday.
[assistant] Your appointment is booked. Your booking reference is APT-7960. Please bring a photo ID with you.
There’s no message from the customer after the question, and the booking tool’s last result still says awaiting_confirmation. Rasa’s Explicit confirmations (opens in a new tab) section explains why: a typed reply goes to Claude, which spends a call on resolve_tool_confirmation to decide yes or no, but a tap agrees or declines without that call.
Why It Happens
The tap settles the confirmation inside Rasa. Rasa runs the tool and sends your confirmation, but Claude takes no part, so its history still shows the tool waiting for an answer. The skill was still open after the booking, so Rasa gave Claude one more call in the same turn, telling it to carry on after the canned reply. Claude read a history with no yes in it, and asked for one.
The Fix
End the skill as soon as the booking is made. Add complete_when with a condition on the booking reference to the skill’s frontmatter, after description:
complete_when:
condition: "session.book_appointment.booking_reference"
Rasa’s guide to stating when a skill is finished (opens in a new tab) says a condition with no criteria completes the skill on its own once it’s true. The booking tool saves the reference after a successful booking, so the skill ends right there, and Rasa’s Completed skill asks the wrap-up question without another call to Claude. Train again and restart the Inspector:
rasa train
rasa inspect
If Customers Also Tap No
A No tap is hidden from Claude the same way. Rasa sends the denial line and ends the turn, but when the customer writes again, Claude still sees a booking waiting for an answer, and asks again:

If customers may keep talking after a no, let them type the answer instead: remove the buttons from the confirmation question. Claude then records the answer itself with resolve_tool_confirmation, at the cost of one more call per confirmation:
utter_ask_book_appointment_confirmation:
- text: >-
Shall I book this appointment? Branch: {branch}. Topic: {topic}.
Day: {day}.

Claude saw the decline, so when the customer said they were done, it cancelled the booking skill, and the wrap-up question followed.
After the Fix

Now a tap on Yes books the appointment, the confirmation goes out, and the wrap-up question follows, with nothing from Claude in between. In Inspect mode, Book an Appointment skill completed comes right after the booking, with no LLM call.
Common Mistakes
| Mistake | Do this instead |
|---|---|
| Expecting Claude to know about a tap | In Rasa Pro 3.22 it doesn’t. End the skill with complete_when once the tool has done its job, or let the customer type the answer. |
| Asking for confirmation in the skill’s instructions as well | Let Rasa ask. With requires_confirmation on, the instructions only say when to call the tool. |
| Putting the confirmation payloads on another response | Use set:session.system.confirmation=true and =false only on the response named in utter_for_confirmation. |
Troubleshooting
| Problem | Fix |
|---|---|
| Claude says it hasn’t booked after a Yes tap | Add the complete_when condition from The Fix, train again and restart rasa inspect. |
| Claude asks to book again after a No tap | Remove the buttons from the confirmation question, so the customer types the answer. |
rasa train rejects a confirmation button | Every button on the confirmation question must use one of the two payloads, set:session.system.confirmation=true or set:session.system.confirmation=false. |
FAQ
Was the appointment booked twice?
No. Rasa ran the tool once, on the tap. Claude’s second question was only text: it didn’t call the tool again.
Does this happen with typed answers?
Not this way. With a typed yes, Claude records the answer with resolve_tool_confirmation, so its history shows the booking. Ending the skill with complete_when is still worth it, so nothing more is said after the confirmation.
Conclusion
In Rasa Pro 3.22, a confirmation tap settles the booking without Claude, so Claude’s history keeps saying the tool is waiting for an answer. End the skill with a complete_when condition once the booking is made, and let customers type their answer if they might keep talking after a no.
Additional Resources
- Explicit confirmations (opens in a new tab) (Rasa docs)
- Confirmation payloads (opens in a new tab) (Rasa docs)
- complete_when (opens in a new tab) in the skill.md reference (Rasa docs)
- State when the skill is finished (opens in a new tab) (Rasa docs)
Related
- Rasa Tutorial — Part 8: Tool Constraints: Make Your Agent Ask Before It Acts
- Rasa Tutorial — Part 7: Responses: Control the Exact Wording
- Rasa Tutorial for Beginners: Mastering Rasa Pro in Python, with every part of the series
Rasa, Claude and other names mentioned are trademarks of their respective owners. JD Bots isn’t affiliated with or endorsed by Rasa Technologies or Anthropic.
0 comments