Collect answers and route a Logic Flow

Use Collect response when the next step needs a customer answer. Use Condition when that answer or another known value should choose a path. Validate the input before using it in an action.

Collect the right answer

1. Add Collect response and write a prompt that asks for one useful detail.
2. Choose its response type. The supported types include text, name, email, phone, number, URL, date, time, a constrained regular expression, media, location and contact.
3. Choose the destination field or flow variable. Match its type to the value you expect.
4. Configure the validation shown for that type, such as number bounds or accepted media. Write an invalid-answer message that explains how to correct the answer.
5. Set the allowed retries and, where needed, a response timeout.
6. Connect valid, wrong type, retry exhausted, optional timeout, and any configured send-failure path. Use a human handoff when the customer needs help.

A customer reply is not automatically valid. Test an empty or mismatched answer as well as the ordinary successful input. A rejected answer should not reach an action that requires the value.

Decide whether to replace known values

Choose whether a new answer always replaces the stored value, only fills an empty value, or asks before replacing it. Ask before replacing cannot also skip a response whose value is already known. These choices affect whether the customer sees a question and whether existing information changes.

For example, a returning customer's email can remain unchanged until they deliberately provide a replacement. Do not overwrite it with an unrelated message simply because that message arrived next.

Route with ordered conditions

A Logic Flow Condition uses named branches. Within each branch choose whether all or any of its conditions must match. Put more specific branches before broader ones and connect the fallback for no match. The first matching branch determines the route.

For an illustrative enquiry, you might route a group-stay request before a general room enquiry. Give the unmatched branch a clarification or human exit. Do not assume an unknown answer belongs to the first branch.

Automation's separate Check a condition step uses true/false outcomes. Do not copy that shape into a Logic Flow condition.

Next: Reuse a published sub-flow, configure a connected action, or validate and publish.