Difference between revisions of "Provisioning/AutomaticSuspensionAndRestriction/Configuration/Events"
(Created page with "== Configuring the Restrict Events and Customer Notifications == === Automatic Account Suspension and Service Restriction Events === xxxxxx == See Also == xxxxx") |
(→Configuring the Restrict Events and Customer Notifications) |
||
| 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. | |
| + | |||
| + | * 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. | ||
| + | * 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 | ||
| + | |||
| + | |||
| + | 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) | ||
| + | for notifying customers that their service(s) have been restricted (is sent when the service is restricted) | ||
| + | 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. | ||
| + | Auto-suspend Administration screens where you will: | ||
| + | set up and configure automatic suspension rules | ||
| + | configure the days and times when automatic suspension can occur | ||
| + | configure when the services of a customer can be restored and reactivate the account. | ||
== See Also == | == See Also == | ||
xxxxx | xxxxx | ||
Revision as of 16:53, 3 October 2014
Configuring the Restrict Events and Customer Notifications
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.
- 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.
- 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
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)
for notifying customers that their service(s) have been restricted (is sent when the service is restricted)
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.
Auto-suspend Administration screens where you will:
set up and configure automatic suspension rules
configure the days and times when automatic suspension can occur
configure when the services of a customer can be restored and reactivate the account.
See Also
xxxxx
