Quick Setup Checklist
Follow these steps to test your flow in real conditions before launching to a large audience.
- Connect a real channel for live testing
- Create a small test contact group
- Start the flow for the test group
- Complete the flow end-to-end as a contact
- Review Results to confirm paths and message actions
- Fix issues and re-test before launch
- Optional advanced testing (A/B, multi-channel, edge cases)
- Resolve common testing and launch issues
Connect a Real Channel
Before testing, ensure your preferred channel is fully connected and operational.
For SMS channels:
- A valid phone number must be connected
- The number must be active for each carrier you plan to use
[CAPTURE: Settings page with a fully connected SMS or local carrier channel (for example, an Orange carrier connection).]
Important: Testing with trial numbers or incomplete channel configurations may produce misleading results.
Create a Test Contact Group
Before sending a flow to a large audience, create a small group of test contacts.
- Navigate to the Contacts tab
- Click the ☰ menu icon
- Select New Group
- Name the group (for example: Flow Test Group)
[CAPTURE: Contacts page with the New Group option selected and a test group name entered.]
Tip: Use real phone numbers or accounts that you can actively monitor during testing.
Send the Flow to the Test Group
To launch the test:
- Select the test group
- Click Select All
- Click the Flow button that appears
- Choose the flow you want to test
[CAPTURE: Group view with Select All enabled and the Flow action button visible.]
Complete the Flow as a Contact
Your test contacts should:
- Complete the flow from start to finish
- Respond to all prompts
- Trigger all expected branches and conditions
This allows you to verify:
- Message clarity
- Correct branching logic
- Timing and delivery of messages
Important: A flow may appear correct in the simulator but behave differently when tested on a live channel.
Review Flow Results
As contacts move through the flow, review the Results view.
- Open the flow
- Click the ☰ menu icon
- Select Results
[CAPTURE: Flow editor with the ☰ menu expanded and Results selected.]
In Results, you can see:
- Which paths contacts followed
- Where contacts exited or stalled
- Whether message actions were reached
Fix Issues Before Launch
While testing, look for:
- Messages that failed to send
- Unexpected responses or behavior
- Confusing or unclear message content
Make adjustments to the flow and re-test until everything works as expected.
Warning: Launching untested flows can lead to failed messages, poor user experience, and unnecessary costs.
Optional Advanced Testing
You may also consider:
- A/B testing message content or logic
- Testing across multiple channels
- Testing with different contact profiles or data values
Tip: Testing edge cases (missing data, unexpected replies) helps ensure flows behave reliably in production.
Common Issues
The simulator works, but live testing fails
Cause: Live channels introduce real delivery constraints (connectivity, provider rules, opt-outs, or channel setup).
Fix: Verify the channel is connected, test with a real number/account, and check message logs for provider errors.
Messages fail during testing on Twilio
Cause: A trial number may be connected, or the number/channel is restricted for real delivery.
Fix: Use a purchased Twilio number for SMS testing, or test with a free channel such as Telegram for logic validation.
Test contacts don’t reach a Send Message step
Cause: Flow logic routed contacts away from message actions, or required inputs/data were missing.
Fix: Use Results to see where contacts exited or stalled, then adjust splits, validations, and default paths.
Messages are delivered, but timing looks wrong
Cause: Timezone settings, scheduling rules, or campaign/event offsets may not match expectations.
Fix: Confirm workspace timezone and re-test timing-sensitive steps with a known test contact.