Difference between revisions of "Events"
(→See also) |
|||
| Line 29: | Line 29: | ||
E.g. a customer reaches 90% of their usage allocation for a given period. | E.g. a customer reaches 90% of their usage allocation for a given period. | ||
| − | + | = See Also = | |
| − | + | * [[Events/Event Text Library|The Event Text Library]] | |
* [[SMS Event Gateways | SMS Gateway information for SMS events]] | * [[SMS Event Gateways | SMS Gateway information for SMS events]] | ||
* [[InvoiceEmailTemplate|Setting up the Invoice Delivery (via email) template]] | * [[InvoiceEmailTemplate|Setting up the Invoice Delivery (via email) template]] | ||
Revision as of 09:15, 29 September 2016
Introduction to Events
The Emersion Events System is more than just a notifications system. It automates many activities that typically support to Emersion's core features. Examples of how events can be used are:
- Sending the customer their invoice via email.
- Scheduling a report to be sent to a nominated email address.
- Sending a customer a welcome letter.
- SMS a customer when they have reached a given % of their available usage.
Emersion provides a set of default events to you during your implementation. We have events for Wholesale & Retail Service Providers. We also have events specific to service types, and various features. These will be added to you on an as-needed basis.
Anatomy of an Event
An event comprises three parts:
- A pre-defined trigger
- An action
- A set of conditions
A trigger is the initiation of an event when the conditions of the event have been satisfied. E.g. Your customer's invoice becomes overdue today (the predefined condition is met, trigging the event) therefore the system will initiate an email (perform an action) to advise the customer that their invoice is overdue.
An action is what the system will do once the condition is met. Each action occurred only one a template has been set up by the Service Provider. The template for an event gives you the ability to customise the action any way you choose. Email events can be plain text, or HTML/CSS based. E.g. email, sms, log.
Conditions are the pre-determined status of a dynamic object, or instance, that trigger an event to occur. E.g. a customer reaches 90% of their usage allocation for a given period.
