Use this reservation confirmation flow as an example.
Cmd/Ctrl + C
and Cmd/Ctrl + V
in the Flow Editor.reservation confirmation
.
It also acts as a breadcrumb, allowing you to return to the list of all flows. This is useful when working across multiple projects or agents.
Collect confirmation code
. The 🏁 icon indicates it’s the start step of the flow.
Each step contains:
save_confirmation_code
if the user provides a valid input.
This example uses both the conversation and flow objects:
/
and appear as underlined blocks in the prompt editor.
See the transition function page for more details.
goto_step()
calls inside a single function. Always return
after calling goto_step
.
save_first_name
, save_last_name
) and proceeds.confirmation code
, first name
, and last name
against entries in the $reservations
list.confirm_reservation
function and moves forward.transfer_call
with the following parameters:
destination="RESERVATIONS"
reason="RESERVATION_NOT_FOUND"
utterance="Right, let me put you through to someone who can help. Just a moment."
return
after flow.goto_step()
to prevent silent overridesgoto_step_4
) — use intent-based names like match_reservation
or retry_lookup
twenty seventh of june twenty twenty five
, which can be hard to parse — especially if you’re enforcing a strict format like DD/MM/YYYY
.
The user will say a date. You must extract the intended date and convert it to DD MM YYYY format. If they use a different format, rewrite it before returning.