|
|
| (26 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | == Introduction to Events == | + | =This Content Has Moved House= |
| | | | |
| − | The Emersion Events System is a notifications system. It automates many activities that typically support to Emersion's core features. Examples of how events can be used are:
| + | This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base. |
| | | | |
| − | * Sending the customer their invoice via email.
| + | We are sorry for the untidiness while we are shifting locations and we appreciate your patience during the transition to our new home. |
| − | * 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
| + | [https://resources.emersion.com/display/EKB/Events Take me to the Emersion Knowledge Base article] |
| | | | |
| − | == Anatomy of an Event ==
| + | [[file:new_home_sm.jpg|900px]] |
| − | | |
| − | An event has four parts:
| |
| − | | |
| − | A pre-defined trigger
| |
| − | An action
| |
| − | A set of conditions
| |
| − | A template
| |
| − | | |
| − | Each action is characterised by a template that defines the action the system performs. Actions are linked to one or many account profiles to determine what accounts the action is performed against. So an event is simply the complete mapping of a trigger, an action, account profile, and a template.
| |
| − | | |
| − | Events are configured by Emersion’s support team specifically to your individual requirements. Each event trigger is defined for each action and mapped accordingly to suit your business. Please contact our support team to configure events and triggers for you.
| |
| − | There are basically two types of events available: account centric; or process centric. Account centric events examine customer records to determine whether certain conditions exist within the customer accounts, such as invoice overdue, credit card expired, and add new customer or service. Process centric events check for other system process driven conditions, such as usage threshold reached, payment failed, and payment received. The Emersion support staff will set up the right event type to suit your business rules
| |
| − | | |
| − | | |
| − | [[SystemEvents/Templates|Event Templates]]
| |
Latest revision as of 08:16, 17 January 2019
This Content Has Moved House
This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base.
We are sorry for the untidiness while we are shifting locations and we appreciate your patience during the transition to our new home.
Take me to the Emersion Knowledge Base article
