Revision as of 09:37, 17 September 2015

Event Types

Introduction

Events types are defined by Emersion and determine the condition, or conditions, each event will be triggered. As mentioned in the introduction, there are two broad categories of events, account or process centric. Within each event category, there are many event types, each with a set of specific, system defined trigger points or conditions. The event is triggered when all the trigger conditions are met. For example, the overdue invoice event may have trigger conditions based on the number of days overdue, the amount overdue and the number of overdue invoices.

Additional event types may become available in the future. See below for more information about each event type.

Account Creation

When a new customer account is created, this event can be triggered to send an email to the customer e.g. welcome pack, FAQs, contact numbers and other new account details.

Account Status Change

When a customer’s account status changes (i.e. active / inactive) this event can be triggered to inform the customer of the changes. For example, when a customer’s account is made active after being inactive for whatever reason, you could send them message.

Account Add Package Subscription

This event can be triggered when a new package is purchased to send information to the customer e.g. usernames, service setup information etc.

Account Package Migration

This event can be triggered when a customer’s existing package is migrated to a new package e.g. when the customer upgrades or chooses other service packages etc. The new package details and related information could be sent to the customer.

Account Password Change

This event can be triggered when the customer changes their account password via the End User Portal e.g. to send a confirmation to the user as well as notify your support staff.

Automatic Payment Set up Notification event

This event sends a notification when an automated payment method is enabled for an account.

Auto Suspend

This is a service-based event and is used to automatically restrict the customer's service for non-payment.

Requires subscription to the Automatic Account Suspension and Restriction feature.

Auto Renew Account Credit

This event is primarily used for pre-paid services. When the service usage has met a particular threshold (e.g. pre-paid credit expiry in 10 days, or 10 hours credit remaining), this event can trigger an automatic renew or purchase of further pre-paid credit. This event could also be used to prevent further usage on the service.

While similar in natire to the auto top-up events described below, it is not the same. This is a service-based event, whereas the auto top-up features and events are account-based.

Auto Top-up credit limit threshold notification warning

This account-based event is triggered when a customer's credit limit threshold is reached and sends a notification by SMS or email.

Requires subscription to the Auto Top-Up feature.

Auto Top-up credit limit initiate payment

When the customer's account balance drops below the auto top-up threshold amount, this event will automatically take a payment.

Requires subscription to the Auto Top-Up feature.

Auto UnSuspend

This is a service-based event and is used to automatically lift the restrictions that have been placed on a customer's service.

Requires subscription to the Automatic Account Suspension and Restriction feature.

Automatic Payment Set Up Notification

Sends a notification when an automated payment method is enabled for an account

Bolt-on Add-ons Activation event

This event sends a notification when a bolt-on add-on is activated.

Bolt-on Add-ons Usage Notification Alerts

For subscribers to bolt-on add-ons and the TCP (Trade Consumer Protection) events, a new TCP event is available for alerting customers regarding bolt-on add-on usage. Like the Service, Bolt-on and Data TCP events, the default percentage thresholds given are 50%, 85% and 100%. Service providers can request additional thresholds if required.

Bulk Upload Processing Notification

This event is used with several of the bulk import and bulk update tools within Cumulus. It is triggered once an upload file has been parsed by the system and sends the results of the import via email to a nominated user.

Learn more about what you can update and import in bulk

Cancelled Package

If a package is cancelled, this event can be triggered to confirm the services cancellation, and inform the customer of the final balance.

Forgotten Password - SMS Password

Sending the customer a new password via SMS.

Forgotten Password - Email reset link

Sends the customer a link so that they can reset their password to the End User Portal.

Invoice Post

When the billing system has completed an invoice run, and there are invoices with the delivery method of ‘post’ (i.e. to physically send paper invoices to customers in the mail), this event can notify an Emersion user via email that the invoices are ready to be sent, as well as send all the invoices as attachments to be printed and posted.

Invoice Delivery

When the billing system has completed an invoice run, and there are invoices created with the delivery method of ‘email’, this event can trigger an email to be sent to the customer with the invoice attached.

Invoice Due

This event can be triggered on or after the invoice due date when payment has not been received e.g. email the customer a reminder note. The number of days from the invoice due date to trigger the event can be configured.

Invoice Overdue

Similar to the ‘Invoice Due’ event, this event can be triggered when the invoice due date has past and payment has not been received e.g. email the customer an overdue reminder note. The number of days from the invoice due date to trigger the event can be configured.

Credit Card Expiry

This event examines each customer account to determine whether the credit card expiry date recorded is approaching and if so to trigger an action. For example, when a customer’s credit card is within 2 months of expiry, send an email to prompt the customer to provide updated credit card details. The number of months before the expiry date, as well the ability to trigger multiple events at different points (e.g. at 2 months, at 1 month, and on the expiry month) can be configured.

Credit Limit Exceeded

This event is triggered when an account's outstanding balance exceeds the account's credit limit.

Automated Payment Received

When an automated payment has been successfully processed by the system, this event can be triggered to send a message and receipt details to the customer to confirm that the payment has been completed, as well as notify your accounts receivable staff.

Manual Payment Received

When a payment has been successfully processed manually by an Emersion user in the system, this event can be triggered to send a message and receipt details to the customer to confirm that the payment has been completed, as well as notify your accounts receivable staff.

Move Customer Profile And Group For Overdue Invoices

Part of the suite of debt collection management events, this event monitors for customers with overdue invoices. It requires the following 3 parameters to be set in the event mapping:

• Invoice Overdue Parameter
• Account Profile ID
• Account Group ID

When a customer has an unpaid invoice that exceeds this Invoice Overdue Parameter and is not already already assigned to the nominated Account Profile and/or Account Group, the event will move them into these profile and group accordingly.

Requires a subscription to Account Groups

• Information about Move customer Profile and Group for Overdue Invoices Event

Move Customer Profile And Group For Up To Date Invoices

Part of the suite of debt collection management events and the sister event to Move Customer Profile And Group For Overdue Invoices. When the end user no longer meets the conditions of the trigger, the former profile and group settings will be restored via this event.

Requires a subscription to Account Groups

Package Activated

This event can be triggered when a new package is activated, and could be used to send an email to the customer.

Payment Failed

When an automated payment cannot be processed by the system, this event can be triggered to send a message to the customer to notify that the payment has failed, as well as notify your accounts receivable staff.

Payment Extension

Informs the customer that their invoice due date has been extended. Requires subscription to Payment Extensions

Payment plan has been completed

Notifies the customer when the payment plan has been completed. For example, when all payments for the payment plan are successful and nothing further is owing. Requires subscription to the Payment Plans.

Payment plan has been cancelled

Notifies when the payment plan has been cancelled before the payment plan has been completed. This can be cancelled either by an Operator or by the system where there are too many failed payments. Requires subscription to the Payment Plans.

Payment plan has been created

Notifies when a new payment plan has been created. Requires subscription to Payment Plans.

Payment plan transaction has failed

Notifies the customer when a scheduled payment for a payment plan failed. Requires subscription to the Payment Plans.

Shape Bolt On

Finds customers whose current bolt on usage exceeds the Shaping Limit as defined in the bolt on. This will then send the request to shape the customer’s service.

Unshape Bolt On

Finds customers whose services are currently shaped by the ‘Shape Bolt On’ event but whose usage in the current period is now below the shaping threshold. This will then send the request to lift the shaping on the customer’s service

Shape Valid Service

This event examines service usage and triggers when the usage amount has reached the monthly allowance as set on the service plan. The system then shapes the service (i.e. by interfacing with the Radius server).

Remove Shaping from Valid Service

This event is closely linked to the ‘Shape Valid Service’ event, and triggers when the usage period of a shaped service rolls over to the next usage period (e.g. at the beginning of the month). The system then removes the shaping that was previously applied to the service.

Usage Threshold (Shaping)

This event is used to examine and monitor usage data and trigger when a particular percentage of the service usage allowance for the period has been reached. For example, trigger an event when a DSL service’s usage reaches 75% of the monthly quota. Multiple trigger points may be set up e.g. one for 75% of usage allowance used, and another at 90% etc.

Usage Over Limit (Shaped)

This event triggers when the usage of a service has exceeded the service usage allowance for the period i.e. at 100% of usage.

Rolling Usage Threshold

This event is used to examine and monitor usage data to identify unexpected or sudden changes in a customer’s service usage. Every day, the system calculates a rolling 30 day total of the service usage and then examines the current calculated amount with the previous day’s amount, and triggers the event when a particular threshold is reached. For example, if the rolling 30 day total of data used yesterday compared to the rolling 30 day total of data used today changes from say 80% yesterday to 100% today, the event can trigger to notify the customer. Usage thresholds can be specified separately for data upload, data download, and telephony.

Re-Rating Invoice Complete

When you audit your invoices following a bill run, some invoices may have fees, charges, or rates that were incorrect. After you have made the necessary corrections (e.g. update the product rate cards etc.) you can click the ‘Re-Rate’ button to have the invoice charges recalculated by the system. This event is triggered once the system has completed re-rating the invoices and can be used to notify your billing staff to review the updated invoices.

Re-Rendering an Invoice from UI

When updates have been made to invoices following a bill run (e.g. adding or modifying card lines etc.) you can click the ‘Re-Render’ button to have the invoice re-created by the system. This event is triggered once the system has completed re-rendering the invoices and can be used. to notify your billing staff to review the updated invoices.

Service Activation

This event will send a notification when a new service is activated.

Service Type Migrate

This event triggers a notification when the service type migration process begins. Requires separate subscription to Service Type Migrations

See also

• Events
• Event actions
• Event triggers
• Templates