What are scenarios?

What are scenarios?

These are the paths that you can make your contacts go through and in which, at any time, you can intervene. You can create specific messages through any of the communication channels that we have in MDirector. You will be able to schedule these tours using your users' contact information or their online behavior habits. These tours will be triggered by a date (birthdays, anniversaries, etc), event or based on subscriber behavior, or they can come from another scenario.

You can start by creating a subscription type scenario that sends a welcome message to all new registered contacts, then you can adapt it according to your needs.

How do scenarios work?

All scenarios contain the following elements with which the paths are formed and you can create them from the Scenario editor that you can access when you want to Create or Edit a scenario.

Elements of a scenario:

• Entry points: They are the ways in which a contact enters our scenario (when they subscribe, when they unsubscribe, when they click on a link in an email, etc.). When creating a scenario the first thing you will do is add an entry point to your scenario. For example a user's subscription through a form.
  
  
• Steps in the scenario (actions and conditions): They are the stages through which the contact will go, depending on the behavior they show in relation to the messages sent to them. The steps can be: 
  • Actions: Perform actions based on the entry points you have chosen. For example: send an email, a sms, etc.
  • Conditions: The conditions are the ones that will allow us to divide it into different branches depending on the subscriber's interaction with what happens inside your emails or other external events.
    
    

What is the path of a contact through a scenario?

As soon as you activate a scenario, your contacts will be able to enter it. The path of a scenario is as follows:

1. The contact enters the scenario, if it meets the validation conditions of at least one of the entry points.
2. The contact then goes through the different steps of the scenario (actions and conditions). The steps are the workflows.
1. If it meets the criteria for a step, it will move on to the next step.
2. If it does not meet the criteria of a step, it will exit the scenario, except if it is an if/else condition (yes/no) in which case it will go to the "No" branch.
3. The contact exits the scenario: when there are no more steps to be performed in relation to its behavior or it reaches an exit element.

The path(s) are made in a continuous way, without stopping, unless stop actions are entered in which it is indicated how many units of time you want to wait to pass to the next node.