Define the event precisely
Registration differs from enrolment, and enrolment differs from payment. Choose the event that matches the message's purpose so users do not receive instructions too early.
A forgotten welcome message, a delayed registration follow-up, a buying opportunity nobody revisits. Explore scenarios supported by Byaan and understand when they start, what they do, and what to review before enabling them.
This is an exploratory library. Choosing a rule here does not create automation or send a message.
An example from the available templates. Actual delivery remains subject to settings, eligibility, and usage limits.
Search for a process or choose a category. Open a scenario to see its prerequisite, trigger, action, and approval point, then follow a local example through its steps.
Matching rules 6
Creating an account does not prove that someone bought a course. Write the welcome for a new registration, and review messaging eligibility and delivery settings.
Illustrative scenarios only. The example does not read your academy's data, create a rule, or operate a messaging channel.
A new account with an email address eligible to receive messages, a configured email channel, and welcome content suited to your academy.
Before enabling several workflows, agree on the reviewer, why a learner enters the flow, and which message they should receive.
Registration differs from enrolment, and enrolment differs from payment. Choose the event that matches the message's purpose so users do not receive instructions too early.
One journey can match several rules. Review duplication, recipient eligibility, channel, and usage limits before enabling the workflows together.
Templates start disabled. The team reviews and approves their conditions before enabling them, while Laheeb suggestions follow a clear approval process.
No. Search, selection, and step walkthroughs run locally in this example. Real workflows are enabled inside the platform after their content, settings, and permissions are reviewed.
Templates are reviewed before activation, then run on matching events according to their settings. A Laheeb suggestion follows an approval process defining content, audience, and channel before execution.
The periods shown are template wait intervals. Execution and email delivery depend on the channel, settings, recipient eligibility, and usage limits. The library does not guarantee instant delivery or a conversion rate.
This library explains capabilities in the system; it is not a plan entitlement table. Discuss the rules and channels you need to confirm availability and settings before subscribing or activating them.
Describe the event that starts the work, who reviews the message, and the operational outcome required. Automation discussions become more precise when they start with a specific situation.