Automation flows are the perfect way to create and send multi-stage communications triggered by a certain event (e.g., subscribing to texts, placing an order, etc.). With Flow Builder, you can schedule individual messages, limit the frequency of how often a subscriber can enter your flow, and take advantage of Wait for Event Branching. Wait for Event Branching allows you to easily visualize and build your flow, add automated responses to subscriber replies, and even automate follow-ups to previous messages based on subscriber action.
How Wait for Event Branching Benefits You
- Scale your one-to-one customer conversations by automating follow-up messages unique to the responses you receive from subscribers.
- Collect zero-party data by using this feature in tandem with subscriber tags to add or remove tags based on subscriber replies to your automation flow.
Wait for Event branching will always include a none of the above or event never occurred branch so your brand can still scale automated responses for:
- Any responses that do not match the specifications for placement in the other branches.
- Subscribers who do not respond within the Max Wait Time configured when setting up the branching.
Add Wait For Event Branches to Automation Flows
- Select Messaging on the left-side navigation panel of your Postscript Dashboard.
- Select Flow Builder then select an existing automation flow.
- If you have not yet created an automation flow, select Create Flow in the upper right corner. Choose Automation. Select either Use an automation template or Create a new automation, then select Continue in the bottom right of the module.
- Set your automation properties. Learn more about how to set up your automation flow here.
- Under Flow Actions, select and drag Wait for Event Split to the space below the first message in your flow.
- Choose your event. The event indicates that you intend to branch subsequent messages based on the selected action (in the example above, the flow will branch subsequent messages based on if the subscriber creates an order).
- Under Max Wait Time, enter the amount of time you will allow for subscribers to complete the event (in the example above, we will wait 24 hours for the subscriber to create an order. If they create an order after 24 hours, they will flow into the default none of the above or event never occurred branch).
- Under Branches, select a property and add a value for each branch (in the example above, we have selected Discount Codes | Code as the property and added LOYALTY10 as the value to indicate we will send subsequent messages based on if the subscriber created an order with the discount code mentioned in the first message) (Note: when using is or is not logic, you can add multiple matches to your branch - these values are not case sensitive).
- Continue adding branches by selecting the + New Branch button under the none of the above or event never occurred branch.
- Select Save in the bottom right of the Wait for Event editor.
- Under Flow Actions, select either the Delay icon or the Send Message icon. Then, drag and drop the icon under each branch to add either a delay or a message to that branch.
- Select Save or Schedule or Activate in the upper-right area of Flow Builder. You can choose to activate the flow immediately or schedule the flow to activate at a certain time.
Understanding Approximate Matching
Postscript employs Approxmiate Matching to match subscriber responses to the intended response even if the subscriber’s reply is misspelled or contains a typo. For example, if a reply option is Summer and the subscriber replies with "summr", they will still funnel down the correct branch. With Approximate Matching, your brand can:
- Improve subscriber engagement. Since approximate matching allows for more accurate response routing, your messaging strategy can become more targeted and effective in order to improve engagement and drive conversions.
- Get time back. Spend more time focused on orchestrating an optimized SMS program and less time defining all possible permutations of an intended response within a single flow.
- Enhance the user experience for subscribers. Approximate matching facilitates a better conversational user experience since it ensures that subscriber responses are correctly matched to the intended response.
To enable Approxmiate Matching, be sure your Wait for Event filter settings are configured with the parameters Is or Is not. When your parameters are defined with Is or Is not, you'll be prompted with a checkbox to accept approxmiate matching.
Wait For Event Branching Use Cases
Have questions? Please feel free to reach out to our wonderful Support team at firstname.lastname@example.org or via live chat. You can also submit a support request here!
Need ongoing channel strategy guidance? Please fill out this form and we'll connect you to one of our certified partners.