Choices let a person pick a direction. Capture steps let the automation wait for something they type and save it to their contact. In AP3K, use the quick Chat editor for a saved response and email or phone collection; use Flow builder for branching choices and custom answers.
Adding choices in Flow builder
Add a question/choice step, write the question and give each choice a short label. Connect each option to the message or step that should follow it. A choice should lead somewhere useful before you publish.
For example, “What are you here for?” can offer Get expert tips and Discover products. Each option leads to its own response. A link button opens a website; a choice routes the conversation. Use the right kind of button for the job.
Keep the labels short. Two or three words are easier to read in a chat bubble than a full sentence. Use a Condition node when the branch depends on stored information instead of a button tap.
Collecting a reply
In a quick Chat automation, choose Collect info → Email o bien Phone on a paid plan. Write the request. The automation waits for the reply, validates it and saves a valid value to the sender’s contact.
In Flow builder, use an email, phone or capture-answer step. Set the next connection so the conversation continues after the answer. Capture-answer stores free text in the field you select.
Email, phone and free text
| Tipo | Use it for |
|---|---|
| A valid email address. | |
| Phone | A phone number; ask for the country code. |
| Capture answer | A name, city or other free-text value in a flow field. |
Email and phone details appear in Contactos on the profile that provided them. Free text needs a clear question because the automation cannot infer whether an arbitrary answer is useful.
Ask for one thing at a time
Every question is a point where someone may stop replying. Ask only for details the next step needs, explain why, and confirm what happens after the person answers.
A worked conversation
- Greet and offer choices: “What are you here for?”
- Branch: each choice leads to a response that answers it.
- Collect where useful: request an email in the branch that needs one.
- Confirm: deliver the promised link or explain the next step.
The Capture leads from DMs and Sell products or services from DMs templates demonstrate these flow patterns.