Journey templates
Eight ready-made journeys for E-commerce & D2C, each ending in a goal.
Online stores and D2C brands use Flowfox to recover carts, keep customers informed about orders and bring buyers back for the next purchase, on the channel each shopper reads.
8 journeys, 4 segments and the data schema, added to your workspace.
Eight ready-made journeys for E-commerce & D2C, each ending in a goal.
Wording written for the channel, ready for DLT or Meta approval.
Four audiences you can use on day one.
The numbers this industry watches most.
Events and attributes to send, with their properties.
Pick a template to see its path from trigger to goal. Install it, change the wait or the channels, send a test and approve it.
Send these from your app, site or system by SDK or API. The schema is inferred from incoming data and can be locked.
product_viewedEventcart_updatedEventcheckout_startedEventorder_placedEventorder_dispatchedEventorder_deliveredEventlast_order_dateAttributeorder_countAttributelifetime_valueAttributefavourite_categoryAttributecoupon_usedAttributepreferred_channelAttributeA guided checklist walks you through each step. Timing depends on how quickly your data and templates are approved.
Create the workspace, connect a data source or SDK and import your contacts with the import wizard.
Install the E-commerce & D2C pack, map your events to the schema and approve the first message templates.
Validate the first journey, run a test send and go live. Watch the counts per step.
Most online stores spend heavily to win a first order and far less to win the second. Engagement closes that gap. After an order, the customer should hear about shipping, delivery and, later, something relevant to buy next.
Flowfox treats these as journeys driven by the events your store sends, so each message follows what the shopper did rather than a calendar.
Cart recovery works because the shopper already showed intent. Send the first reminder after an hour, on WhatsApp where consent exists, and the second by email the next day. Add an order goal so the journey stops at purchase.
Confirmation, dispatch and out-for-delivery messages are read more closely than any promotion. They are also a trusted place to suggest a related item or ask for a review a few days later.
India’s shopping calendar is dense. The festival calendar in Flowfox suggests plans for each moment, and the catalog brings products and coupons into the message.
Add the journeys, segments and schema to your workspace.
Help CenterStart from a trigger, add a wait and a goal.
Help CenterSend an event so a journey can react to it.
Help CenterBring a list in from a file.
Help CenterEvery step, in plain words.
Playbook · 5 minEdit the wait, the channel and the wording.
Playbook · 5 minStart small, grow the schema.
Guide · 4 minCart recovery rate and more.
Explainer · 4 minValidate, test, approve.
Checklist · 3 minFor DLT and Meta review.
Guide · 5 minSend cart_updated events from your store, build a journey that waits an hour, checks for an order and then sends a reminder on WhatsApp or email. Set order_placed as the goal.
Yes. The catalog lets messages pull in products and coupons.
Shopify is one of the connections in FlowConnect. You can also send events by SDK or API.
Keep a holdout group out of the journey and compare conversion against the group that received it.
Yes. Both are supported, with DLT rules for India SMS and Meta approval for WhatsApp templates.
Yes, industry packs are included in both plans.
Start a free workspace, connect a data source and send your first journey. Or book a guided demo.