Difference between revisions of "Events"
m (fixed event mapping report list) |
(→See Also) |
||
| Line 32: | Line 32: | ||
= See Also = | = See Also = | ||
* [[Introduction to Events Video]] | * [[Introduction to Events Video]] | ||
| + | * [[InvoiceDeliveryApproval| Invoice Delivery and Approval Settings]] | ||
| + | * [[SystemEvents/EventTypes|List of all Event Types]] | ||
* [[System_Event_Mapping_Report | System Event Mapping Report]] | * [[System_Event_Mapping_Report | System Event Mapping Report]] | ||
| + | == Advanced Event Features == | ||
| + | |||
* [[Events/Event Text Library|The Event Text Library]] | * [[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]] | ||
| Line 38: | Line 42: | ||
* [[SystemEvents/Templates|Setting up your Event Templates]] | * [[SystemEvents/Templates|Setting up your Event Templates]] | ||
* [[Editing SystemEvents/Troubleshooting|Troubleshooting Events]] | * [[Editing SystemEvents/Troubleshooting|Troubleshooting Events]] | ||
| − | |||
Revision as of 15:43, 27 February 2017
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.
See Also
- Introduction to Events Video
- Invoice Delivery and Approval Settings
- List of all Event Types
- System Event Mapping Report
