Reuse contact inputs reliably with @results
If you just need the essentials, follow this quick path:
- Understand what @results stores (values produced by Split Actions)
- Insert @results via the @ menu in message editors
- Use @results + Tab to browse available results
- Use result metadata (like value and category) when needed
- Validate variables in the Simulator before publishing
This keeps your flows “smart,” reduces repeated questions, and makes branching more consistent.
Step-by-Step Process
@results is a collection of values produced by Split Actions (especially Wait for Response).
When a contact replies and the split evaluates that reply, the flow stores a result you can reference later (example: @results.phone).
Each result can also expose extra metadata (like the selected category).
- In a text field (for example, a Send Message action), type @.
- Select the variable family you want (example: @results).
- Pick the exact variable you need (example:
@results.phone).
[CAPTURE: Message editor showing the @ auto-complete dropdown listing variable families, including @results.]
- In a message editor, type:
@results - Press Tab to show the list of results available in the current flow.
- Select the result you want to reuse.
[CAPTURE: Message editor where typing @results and pressing Tab reveals a list of available flow results.]
After inserting a result, add the metadata property you need. Common needs include:
- The value the contact submitted
- The category the contact matched in the split
[CAPTURE: Message editor showing a result variable expanded to reveal metadata options like value and category.]
- Test your flow in the Simulator.
- Confirm the result is created after the split runs.
- Confirm the variable renders with real content in downstream messages.
- If a variable is wrong, rename your results or adjust where you reference it.
[CAPTURE: Simulator showing a contact response being saved as a result, followed by a message that correctly reuses @results.*.]
Common Issues & Quick Fixes
My message shows “@results.something” instead of a real value
Problem: Your message renders the variable text, not the stored result.
Fix:
- Confirm the result exists (use
@results+ Tab to verify it’s available). - Make sure the variable is spelled exactly like the result name.
- Ensure the contact reaches the node that creates the result before you reference it.
@results is empty even though the contact responded
Problem: A reply was received, but no result is available where you reference it.
Fix:
- Confirm the response was collected by a Split Action like Wait for Response (not a plain message node).
- Check that the split saved a named result (use a clear result name).
- Test again in the Simulator and verify the action log.
My saved result is cut off or incomplete
Problem: Long input is truncated in the stored result.
Fix:
- Keep results short and structured (IDs, codes, labels).
- Split long user input into multiple questions/results.
- Store a short summary if you only need a reusable snippet later.