Difference between revisions of "Provisioning/AutomaticSuspensionAndRestriction/Configuration/Events"

From Emersion
Jump to: navigation, search
(Configuring the Restrict Events and Customer Notifications)
(Automatic Account Suspension and Service Restriction Events)
Line 3: Line 3:
 
=== Automatic Account Suspension and Service Restriction Events ===
 
=== Automatic Account Suspension and Service Restriction Events ===
  
A number of Events are used by the system to perform a number of functions related to Automatic account suspension & restoration.  
+
Events are used by the system to perform functions related to Automatic account suspension & restoration.  
  
* System Events constantly run in the background looking for customers who meet the criteria for auto-suspension or restoration. They are responsible for initiating the suspension of an account and removing a previously applied suspension.
+
Some of the Events used by the system are invisible to you. Constantly running in the background 24/7/365, they are scanning the database looking for customers who meet the criteria for auto-suspension or restoration. They are responsible for initiating the suspension of an account and removing a previously applied suspension.
* The autoSuspendEvent is concerned with the suspension of services based on business rule criteria. They are also then concerned with the restoration of those services when the invoices are paid or based on other exceptions that cause the account to be unsuspended
 
  
 +
In addition, you can leverage the Events system in Emersion to assist you with automating important customer notifications if you wish.
  
You will be provided with:
+
As part of the Automated Suspension & Restriction feature set, you will be provided with:
additional Overdue Invoice events pre-configured to align to your auto-suspension business rules
+
 
For notifying customers that their service(s) will be suspended due to non-payment (24 hour advanced warning)
+
* an Auto Suspend Event
for notifying customers that their service(s) have been restricted (is sent when the service is restricted)
+
* an Auto UnSuspend Event
For notifying customers that their services will be / have been restored.  
+
 
Due to timing of provisioning actions outside Emersion's control, Emersion cannot guarantee a notification regarding service restoration will be delivered before or after the service is physically reactivated.
+
These events will be mapped to your Service Provider account. You do not have to do anything with them if you do not wish. They will used to automatically restrict the service on your customer's account based on your [[Provisioning/AutomaticSuspensionAndRestriction/Configuration/BusinessRules | business rules]].
Auto-suspend Administration screens where you will:
+
 
set up and configure automatic suspension rules
+
Optionally, you can configure the event to send an email or SMS notification+ to be sent at the time the event is triggered. For example, you may wish to notify your customer by SMS that their service has been suspended. Please be aware that the above events are service-based. For each affected service belonging to a customer, one notification per service will be sent.
configure the days and times when automatic suspension can occur
+
 
configure when the services of a customer can be restored and reactivate the account.
+
If you prefer, Emersion can map additional <b>Overdue Invoice</b> event(s) pre-configured to align to your auto-suspension business rules once they are set. These might be useful for giving a customer a 24-hour advance warning that if they do not pay the overdue outstanding balance on the account, that their service(s) will be suspended.
 +
 
 +
+requires separate subscription to SMS Events.
 +
 
 +
== Emersion Suggests ==
 +
 
 +
To get the most out of Events that are available, we suggest the following configuration:
 +
 
 +
# the '''Invoice Due''' event contain text that explains the terms under which a customer's service(s) will be restricted.
 +
# an '''Invoice Overdue''' event is used to advise a customer that restriction is imminent (advance warning notice)
 +
# the Auto Suspend Event is used to notify a service contact/account holder that their service has been restricted
 +
# the Auto UnSuspend Event is used to notify a service contact/account holder their service has been restored.
 +
 
 +
Due to the timing of provisioning actions being outside Emersion's control, Emersion cannot guarantee a notification regarding service restriction or restoration will be delivered before or after the service is physically altered.
 +
 
 +
== See also ==
 +
 
 +
[[SystemEvents/Templates | Setting up Event templates]]
  
 
== See Also ==
 
== See Also ==
  
 
xxxxx
 
xxxxx

Revision as of 17:52, 3 October 2014

Configuring the Restrict Events and Customer Notifications

Automatic Account Suspension and Service Restriction Events

Events are used by the system to perform functions related to Automatic account suspension & restoration.

Some of the Events used by the system are invisible to you. Constantly running in the background 24/7/365, they are scanning the database looking for customers who meet the criteria for auto-suspension or restoration. They are responsible for initiating the suspension of an account and removing a previously applied suspension.

In addition, you can leverage the Events system in Emersion to assist you with automating important customer notifications if you wish.

As part of the Automated Suspension & Restriction feature set, you will be provided with:

  • an Auto Suspend Event
  • an Auto UnSuspend Event

These events will be mapped to your Service Provider account. You do not have to do anything with them if you do not wish. They will used to automatically restrict the service on your customer's account based on your business rules.

Optionally, you can configure the event to send an email or SMS notification+ to be sent at the time the event is triggered. For example, you may wish to notify your customer by SMS that their service has been suspended. Please be aware that the above events are service-based. For each affected service belonging to a customer, one notification per service will be sent.

If you prefer, Emersion can map additional Overdue Invoice event(s) pre-configured to align to your auto-suspension business rules once they are set. These might be useful for giving a customer a 24-hour advance warning that if they do not pay the overdue outstanding balance on the account, that their service(s) will be suspended.

+requires separate subscription to SMS Events.

Emersion Suggests

To get the most out of Events that are available, we suggest the following configuration:

  1. the Invoice Due event contain text that explains the terms under which a customer's service(s) will be restricted.
  2. an Invoice Overdue event is used to advise a customer that restriction is imminent (advance warning notice)
  3. the Auto Suspend Event is used to notify a service contact/account holder that their service has been restricted
  4. the Auto UnSuspend Event is used to notify a service contact/account holder their service has been restored.

Due to the timing of provisioning actions being outside Emersion's control, Emersion cannot guarantee a notification regarding service restriction or restoration will be delivered before or after the service is physically altered.

See also

Setting up Event templates

See Also

xxxxx