How do I set up Request and End steps?

Request

The “Request” step takes the visitor's request and drops it into the panel's “Requests” queue.

Only the visitor's request is asked. The AI writes the subject, and the name is taken from earlier answers. If “Ask for contact details” under “Information to ask” is on (the default), contact details are asked too; if the conversation already has them, they aren't asked again. If you turn it off, the contact is taken from an email or phone collected earlier in the flow; if there is none, the request can't be answered and the queue shows a warning.

Then the visitor is asked “Shall I send your request?”; pressing “Send” opens the request. If the Request step is the last step of the flow, an end with a thank-you text is added after it automatically.

In later steps you can use the visitor's request as {talepAciklama} and, if contact details were asked, the contact as {talepIletisim}. See Requests.

End

The “End” step closes the agent and shows the visitor a thank-you card.

• “Outcome”: “Not set”, “Successful” or “Failed”. Analytics counts conversations reaching this end accordingly; “Your ticket is ready” is a successful end, “Booking cancelled” a failed one.
• “Link to open at the end”: shown as a button on the thank-you card and opened in a new tab (for example a secure payment page). The link must start with http://, https:// or a variable such as {system.page_url}; also enter the “Button text”. There is no automatic redirect.

A flow can have several End steps; separate ends for different outcomes make your analytics meaningful.

The End step isn't required: when a step with nothing connected after it runs, the conversation still completes and the thank-you card appears, but its outcome counts as not set.