Skip to main content
Flows become useful when they remember what contacts said. Capture answers into custom fields, label contacts with tags, then branch or personalize later.

​
Before you start

  • Create the custom fields and tags you need.
  • Prefer clear field names (budget_range, not q3).
  • Decide validation rules (email format, phone, required answer).

​
User Input

Use User Input (or Get User Data, depending on your builder label) to ask a question and store the reply.
1

Add User Input

Place the block after the prompt message (or include the prompt in the block if your UI combines them).
2

Choose a reply type

Free text, email, phone, number, or multiple choice — match the data you need.
3

Save to a custom field

Select the target custom user field. Later blocks can read it with {{your_field}}.
4

Handle invalid answers

Configure retry / failure paths when the reply type is strict (email, phone).

​
Set Custom Field

Use Set Custom Field when the value is known without asking — for example source = instagram_story or a value returned from an External Request.

​
Tag / Untag

Tags are boolean labels. Use them for lifecycle and routing:
  • Apply qualified after a successful Condition path
  • Remove open_ticket when a Flow closes the loop
  • Let Automation Rules fire when a tag is applied

​
Multiple choice answers

For static choices, use Quick Replies or a multiple-choice User Input with fixed options. For options loaded from an API or spreadsheet, see Dynamic choices.

​
Use the data you collected

Collect only what you will use. Extra questions increase drop-off and privacy risk.

​
Next

Conditions

Branch on fields, tags, and channel.

Contacts

Field types, tags, and segments in depth.