The journey builder is a drag-and-drop interface to create automation or chatbot journeys.
With pre-built templates, customisation options, and integrations with other tools and platforms, you can create engaging journeys that are tailored to your specific needs and goals.
Journeys are primarily made up of blocks. They are of 3 types:
Triggers: These are the starting points of any journey.
Actions: These are the key action blocks of a journey.
Flow controllers:
As mentioned above, a journey is made up of blocks which are connected via edges.
This creates different branches in a journey.
Flow controllers decide in which path the journey will proceed.
Journey builder has 3 menus.
Top menu
Shows the name of the journey being edited.
Its status (active/inactive). And a toggle to switch its status from active to inactive and vice-versa.
Last saved at info.
Save button to save any changes being made to the journey.
Left menu
This is a contextual menu.
Depending on the block selected, this menu opens up and provides capability to edit that block.
Right floating menu
Consists of actions and flow controllers.
Channel & Action option will open all the channel specific actions. These are covered in the actions block section here.
Condition option will add a flow controller to the flow. These are covered here in details.
Start a flow option will insert a block, which can enable connecting and starting a new flow from the present active flow.
Sticky notes will insert notes on the flow builder.
BIK users can also use sticky notes to share notes with their team members or for references in the future.
In the flow library, BIK team has added more context in the flow as sticky notes.
It highlights key blocks, their objective, customisation recommendations as relevant.
Builder also has zoom in/out and mini map options at the bottom for better navigation.
Flow validation
Every time a flow is made active or saved, a validator is run behind the seen to check for possible errors.
If the flow contains any possible errors which can break it during runtime, then an error popup is shown and the block with errors are highlighted in red.
If the flow contains configurations which are not recommended and may break the flow, but can be ignored in most of the cases then a warning popup is shown and the block with warnings are highlighted in yellow.
Blocks: Triggers
Blocks: Triggers
BIK offers a list of triggers from customer actions taken on Shopify, Instagram, WhatsApp and other channels and tools, including payment link updates.
Some examples of triggers we support are:
Shopify: abandoned cart, ordered, shipping update, etc
Instagram: story mention, story reply, comment, etc
Integration triggers: payment link paid, subscription activate, etc
Special date triggers - Last or first order date X days ago
BIK also supports user input control (UIC) or keywords as triggers.
BIK’s journey triggers are divided into following types:
Blocks: Send Message
Blocks: Send Message
Send Email
Send SMS
Analytics and Attribution Module
Analytics and Attribution Module
Node Level Analytics (NLA)
BIK journey builder supports detailed analytics at each node to capture:
Node trigger
Whatsapp and Instagram message delivery information
Sent message
Delivered message
Messages read
Email delivery information - Email sent, delivered
SMS delivery information - SMS sent, delivered
QRB or Link click rates
Overall summary for the flow on top
Download information/customer ids at an overall and node level
Note - For now we support 7 days summary for node level analytics. For longer time queries - pls refer to journey summary here.
