Configure an Order Request node
Reads the variant the flow already picked and opens an order request that waits for operator approval. Wire the created, duplicate and error branches.
This node sends no payment link. It reads the selected variant, opens a request that waits for a decision, and ends the conversation. An operator decides. The request appears on the Siparişler tab of Sohbet Gözetimi. Approval and rejection happen on the Order Approvals page.
Before you start
- An account with the Ticimax integration connected
- A variant selection step before this node
- An operator who will decide on the request
Step by step
These screens sit inside the Intent AI section. Sign in, open Intent AI; the menu names below are in that section's left menu.
Add the node to the canvas
Drag the Order Request node out of the Action group in the palette.
Connect it after the variant selection
That step writes the choice to the selected_variant variable.
Leave the selection variable alone
Keep the default name in the selection variable field.
Fill the three messages and wire the branches
Write the received, existing and error texts, then give each output its own step.
See the request land on the Orders tab
Save, try it from a real line, then open the list in Sohbet Gözetimi.
Result checkIf it did not work
Check these
- A node that always leaves through the error branch is reading an empty selection variable. Use the same name in both nodes.
- While one request is open in a chat, no second one is created; the flow takes the duplicate branch.
- Close the open request on the Order Approvals page first.
- The Flow Test window never really runs this step, because a simulated session carries no chat identity.
Does this step look different in your panel?
We can review the screen and exact error text together.
This guide was checked against the product UI and code inventory on 29 August 2026.
