Skip to main content

Event level processes

Azavista Support
Updated

 

This article provides insights into Event level specific processes. For more information on processes, please read our dedicated article.

 

Examples of event-level processes

  • Sending a reminder email to a Participant to complete registration: Registration workflow - Engagement sequence button

mceclip5.png

 

  • Sending additional emails only to attendees with a specific position (e.g. to CEOs in a Pre-arrival workflow): Pre-arrival workflow - Engagement sequence button

mceclip6.png

 

  • Notifying a specific address email every time a participant registers: Registration workflow - After registration actions button

mceclip7.png

 

Modifying a field & registering the date-time at which an action / a process was performed (e.g. an event planner is manually registering participants and it needs to be marked in the participant's profile) - Stage action workflow

    • Note: The participant will still automatically be placed in the "Pre-arrival" stage with all other registered participants, thanks to the "Next workflow" option in the Stage action workflow.

mceclip8.png

 

 

Workflow processes options

The engagement sequence & After invitation/registration actions options are found in Workflows -> Event Workflow Automations (at Event level)

 

The Engagement sequence allows users to create automated processes that are triggered simultaneously with the ones defined in the workflow template.

Examples:

  • scheduling the sending of emails to participants who are in a Registration pending stage (e.g. to update or inform them about the event, or remind/motivate them to complete their registration)
  • Modifying fields after a specific action (e.g. Ticking a participant's "Verified" checkbox field when a planner has manually approved a participant")

The After invitation/registration actions allow users to create automated processes that are triggered only after the Invitation or the Registration workflow has been completed.

Examples:

  • Sending an email to a specific email address (e.g. an event planner who is not using Azavista) whenever a new participant is registered.

The two buttons share the same set of tools, the only difference between them is in the moment at which those additional processes are operated. The Engagement sequence processes are incorporated within the workflow, whereas the After invitation/registration actions processes will be operated once the initial workflow operations are over.

 

Some workflows have both buttons, others only one, others none (here Registration workflow)

mceclip0.png

 

Related articles