Journey templates
Eight ready-made journeys for Fintech & BFSI, each ending in a goal.
Banks, NBFCs, lenders, wealth and payment apps use Flowfox to move customers from sign-up to a first transaction, remind them before due dates and keep consent on record.
8 journeys, 4 segments and the data schema, added to your workspace.
Eight ready-made journeys for Fintech & BFSI, 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.
kyc_startedEventkyc_completedEventcard_activatedEventemi_dueEventpayment_failedEventtransaction_completedEventkyc_statusAttributeproduct_typeAttributecredit_limit_bandAttributedue_dateAttributeconsent_offersAttributepreferred_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 Fintech & BFSI 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.
A bank or lender cannot treat every message the same. A reminder that a payment is due is a service message. An offer for a new product is promotional. They differ in consent, in timing and in the rules that apply, and a good engagement platform keeps them apart.
Flowfox lets you keep service and promotional templates in separate libraries, attach consent as a rule on a segment and send each type on the right channel.
Start where money is lost. Stalled KYC, missed payments and unused cards cost most. A KYC nudge journey follows people who stop at step two, waits a day and reminds them on the channel they use. An EMI reminder journey sends one message three days before the due date and a second the day before, then stops when the payment arrives.
SMS and WhatsApp carry the time-sensitive messages. Push and in-app work for customers who have the app. Email is the right place for statements and longer explanations. In Flowfox one journey can use all of them, and a wait step lets a lower-cost channel go first.
Track completion and payment outcomes rather than opens. Funnels show the exact step where KYC drops. A goal on each journey ends the path when the customer completes the task, so nobody is reminded after they have paid.
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 minKYC completion rate and more.
Explainer · 4 minValidate, test, approve.
Checklist · 3 minFor DLT and Meta review.
Guide · 5 minYes. Templates, journeys and consent rules can be kept apart, so reminders and offers follow different paths and different consent checks.
Consent is recorded per channel on each profile and can be used as a rule in a segment. A journey checks it before each send.
The pack includes SMS wording written for the DLT template format. You still register the templates with your operator before sending in India.
Yes, using a WhatsApp template that Meta has approved. The approval status is shown on the template.
Set the payment event as the journey goal. When the event arrives, the person leaves the journey.
Industry packs are included in both plans. See the pricing page for limits.
Start a free workspace, connect a data source and send your first journey. Or book a guided demo.