The classic Workflow form provides three step buttons:
Steps run in sequence from top to bottom.
A Workflow must contain at least one step.
When no steps exist, the interface states:
Add at least one step. Steps run top-to-bottom; a question pauses the flow until the visitor replies.
A Message step sends a Chat bubble to the visitor.
Use it for scripted information that should appear as part of the Workflow.
The interface notes that Message text supports variable interpolation using the Workflow's stored variables.
Keep scripted messages conversational and appropriate to the trigger that started the Workflow.
A Question step sends a Chat bubble and pauses the Workflow until the visitor responds.
The visitor's response is saved to a Workflow variable.
For a Question step, the form provides:
Save the answer to var_name
The default variable name for a newly created Question step is:
visitor_answer
Use a descriptive variable name when later steps need to reference the visitor's response.
Message steps support interpolation in the form:
{{var}}
This allows a later scripted message to reuse information captured from an earlier Question step when the relevant variable exists.
An Escalate step sends a final or handoff-oriented line and flags the Conversation for human takeover.
The default text for a newly added Escalate step is:
I'll connect you with a human now.
Edit the wording when necessary so it accurately describes the handoff experience your workspace provides.
Escalation is appropriate when:
Each standard-form step includes a delete control.
Before removing a Question, verify that later messages or Workflow logic do not depend on the variable it was capturing.
Review the visible Step number and type carefully. A Question pauses the sequence, while a Message continues immediately and an Escalate moves the interaction toward human takeover.
After building the Workflow: