Spoks supports all the essential flows required for your e-commerce store, including:
Welcome Series
Thank You Flow
Win-Back Flow
Abandoned Checkout
Abandoned Browse
Abandoned Cart
Active on Site
Back in Stock
Creating Your First Flow:
Navigate to the Flows screen.
Click New.
Select one of the pre-built flow templates or choose to Start from scratch.
Recommendation: We highly recommend beginning with a template. This ensures that your trigger and initial flow settings are configured correctly.
Turning a flow on
A flow has switches at two levels, the steps inside it and the flow itself, and both have to be on before anything sends.
Start with the steps. Turn on each step inside the flow. If you try to activate while every step is still off, Spoks tells you that no actions are active and does not activate the flow.
With the steps on, activate the trigger. Spoks then asks whether you want to activate the flow as well. Confirm, and the flow is live.
What the numbers on a send step mean
The numbers on a send step are all-time totals for that step: sends, clicks, click rate and sales. Click them to open the step's full statistics. Spoks credits an order to a campaign or flow message using 7-day last-touch attribution.
Splits and Branches: A Different Approach
Spoks' flow builder is designed to work seamlessly on our mobile app. Because of this, we handle splits and branches differently than many other platforms.
In Spoks, each step (a Send email or Send SMS) in the flow builder has its own filter. You can adjust this filter to precisely control the recipients for that specific step.
How to Add a Conditional Filter:
Click New to add a step.
Select Send email or Send SMS.
Build your email or SMS as intended.
Click Review and Save & Exit.
Back in the flow editor, locate the card for the step you just created.
Click "Only continue if" and set up the necessary condition (e.g., "only send to customers who made their second purchase").
While this experience may take a couple of attempts to feel familiar, you will find it allows you to achieve all the conditional splitting and branching you need.
Example: Filtering by Purchase Behavior in a Welcome Flow
To tailor your welcome email flow and exclude contacts based on their purchase behavior, consider the following examples:
Using Filters to Exclude Contacts Without Purchases: Add a filter to the last step of your flow with a condition such as "Total orders = 0." This ensures that only non-purchasers receive the final email, while purchasers are excluded from this step.
Configuring Conditions for Pre-Enrollment Purchases: Adjust the gating logic by adding a condition like "Last purchase is more than N days ago," where N represents the number of days before the message is sent. This approach excludes contacts who made a purchase just before enrollment, ensuring that true non-buyers continue through the flow.
Note: Step filters only gate the specific message they are applied to; they do not remove contacts from the entire flow.
To take someone out of the flow entirely once they stop qualifying, put the condition on the trigger rather than on a step. Trigger filters keep being checked after enrollment, so a contact who no longer matches is removed when their next step is due. Last purchase is before flow started is the common one: it removes anyone who buys while they are still in the flow.
For where each kind of filter lives and how it behaves, see Using filters in flows.
Coming Soon: A/B testing functionality in the flow builder is currently under development.
A flow email did not arrive
Work down this list in order.
Is there a Delay before the email? A Delay step pauses the flow for the days, hours and minutes you set, so the email will not arrive until that time has passed. This is the most common reason a test looks like it failed. Open the flow and check whether a Delay sits between the trigger and the Send email step.
Is the flow on, and is the Send email step on? These are two separate switches and both have to be on. See Turning a flow on above.
Does the contact actually enter the flow? Check the trigger, and if you added a trigger filter for one specific form, confirm your test submission came from that form.
Does the Send email step have an "Only continue if" filter? If the contact does not meet the condition, they carry on through the flow but this particular email is not sent.
Does the email itself send? Open the email inside the step and click Review, then Test. If the test arrives, the email and its content are fine and the problem is further up this list.