This article provides guidelines for setting up Usage Notifications in CostGuard. It covers
A quick overview
Setup:
Permissions
Setting Thresholds and using the configuration grid
Determining which services on an account receive notifications
Opting Out of notifications
Establishing a Wait period to ensure subscribers do not receive repetitive notifications
Customizing/managing usage notification templates
Recommendations on how often services can be evaluated
Ensuring subscribers are not charged for notifications
Using auditing reports
Quick Tips – Things to Watch Out For
Usage notifications via SMS must be free of charge. See Not Charging Subscribers for Notifications.
Avoid sending redundant notifications to the primary service when a discount is shared by multiple services. See Guidelines for Accounts with Multiple Services, Case 4 – A Configuration to Avoid – Bombarding the Primary Service.
If you have services with SMS blocking, see Auditing Tips for Services with SMS Blocking.
Why Usage Notifications?
Usage Notification functionality has been added in CostGuard to address Bill Shock – a sudden and unexpected increase in monthly bills. A recent Federal Communications Commission (FCC) survey found that 30 million Americans — or one in six mobile users — have experienced Bill Shock.
The CostGuard Usage Notifications solution enables CostGuard users to:
Monitor services (unit balances) as a percentage of the total allotted units (covering all discounted units including minutes, occurrences and currency).
Configure user-definable rules per a defined limit (threshold). These rules dictate when to send configurable notification messages (via SMS or E-mail) to alert subscribers as they approach or pass a usage threshold.
This new functionality can help carriers maintain positive relations with their customers who may otherwise become disenchanted with their service due to the sometimes exorbitant overage charges.
How it Works
Monitoring Usage
CostGuard calculates billable usage as a percentage of the total available units on a service and compares the result to configured thresholds. Usage is calculated as X/Y where:
X = Units within a discount category used in the current bill period
Y = Units within a discount category available in the current bill period (recurring allotment + roll over)
Note:
CostGuard users must properly configure their discount categories.
Usage is checked once per day. Usage in each applicable category (minutes, data and/or messages) is checked independently. On each instance when usage is checked, if usage has reached or exceeded a specified threshold, CostGuard takes the appropriate action according to configured automation rules. When loading/rerating of usage fails, CostGuard does not send notifications until the error has been resolved, loading/rerating is successfully completed and the job is run again (either wait for the next iteration or manually via clerk/service request).
This example illustrates how usage is monitored and compared to configurable thresholds, where notification thresholds are set at 80%, 90% and 100%, and monthly allotment = 100 units. Unused units from bill periods 1 and 2 are rolled over and added to the remaining totals for bill periods 2 and 3 respectively. In bill period 3, by mid-month the subscriber has already used 80% and so a notification is sent. Two days later, the usage reaches 90% so a second notification is sent. By 7/22 the subscriber has used 100% so a notification is sent and overage is charged.
Units Count | Bill Period 1 (May) | Bill Period 2 (June) | Bill Period 3 Thru July 15 | Bill Period 3 Thru July 17 | Bill Period 3 Thru July 22 |
|---|---|---|---|---|---|
Recurring Allotment | 100 | 100 | 100 | 100 | 100 |
Roll Over | 0 | 25 | 35 | 35 | 35 |
Used | 75 | 90 | 108 | 121.5 | 135 |
Remaining Raw Units | 25 | 35 | 27 | 13.5 | 0 |
% Used | 75% | 72% | 80% | 90% | 100% |
This example illustrates the operation of the configurable wait period. In this case the wait period = 7 days. In bill period 3, by mid-month the subscriber has used 80% and so a notification is sent. Two days later, the usage is still at 80%. Since the wait period has not expired, a second notification is not sent. On 7/22 usage is still at 80% and the wait period has expired so a second notification is sent.
Units Count | Bill Period 1 (May) | Bill Period 2 (June) | Bill Period 3 Thru July 15 | Bill Period 3 Thru July 17 | Bill Period 3 Thru July 22 |
|---|---|---|---|---|---|
Recurring Allotment | 100 | 100 | 100 | 100 | 100 |
Roll Over | 0 | 25 | 35 | 35 | 35 |
Used | 75 | 90 | 108 | 108 | 108 |
Remaining Raw Units | 25 | 35 | 27 | 27 | 27 |
% Used | 75% | 72% | 80% | 80% | 80% |
Setup
Setting up Usage Notification functionality in CostGuard requires users to:
Establish one or more usage thresholds to trigger notification
Select the delivery method (SMS or e-mail)
Select a template to define the message
Establish a wait period to limit the frequency of sending the same notifications within a bill period
Select which services receive notifications or opt out on a service basis
Ensure subscribers are not charged for usage notifications sent via SMS by marking the originating customer service numbers as unbillable
Usage Notification functionality is configured via CostGuard Client and Admin Console. Most of the configuration is performed via the new Usage Notifications Configuration form which is described later in this section. Some configuration is performed on existing forms that have been modified to support Usage Notifications.
The basic configuration steps are:
Configure related permissions via the Admin Console Security node.
Configure the following Global Settings via the new Usage Notifications Configuration form:
Wait Period – This is the number of days the system waits before sending another notification for the same discount category/threshold. This helps you avoid annoying subscribers with too many repeat notifications in the same bill period.
Disable/Enable Opting Out – Currently you may allow subscribers to opt out of receiving usage notifications at their discretion. CostGuard provides a means to disable this option globally in the event a future regulation prohibits opting out.
Default Send Usage Notifications To– Where to send notifications (or choosing to opt out) is configured at the service level. This global setting establishes the default to be applied if services are not explicitly configured at time of sale. It also establishes the default on all forms in Make Sale and Customer Management where you set the Send Notifications To option.
Display Send Usage Notifications To Form in POS Make Sale – This setting lets you choose whether to incorporate this step into POS Make Sale, or defer to Customer Management after the sale.
Configure rules. Rules are established by discount category/threshold, for example: send a notification when a service reaches or exceeds 80% of their allotted data usage. Each rule consists of the following elements:
Discount Category
Threshold (% usage)
Notification template to be used
Delivery Type (email or SMS)
Rules can be enabled/disabled on an individual basis. Rules may also be deleted if no longer needed.
Configure usage notification templates.
Coordinate with the IDI Billing team to schedule when usage notifications processing will occur. This configuration is actually done by the IDI Billing Team; however, each customer must coordinate with the team to ensure the schedule fits their needs.
Permissions
The following permissions control the behavior of the Usage Notification Configuration form:
/Application/CostGuardClient/CustomerNotification/UsageNotifications
This controls whether or not users can access the configuration form. If this permission is disabled, the menu item is not available in the menu.
If this permission is enabled but the Modify permission below is disabled, the user has read-only access to the configuration form, with the exception of the Manage Templates link. Access to Usage Notification templates is controlled by the Customer Notification > Manage Templates permissions.
/Application/CostGuardClient/CustomerNotification/UsageNotifications/Modify
This controls whether or not users can edit the fields on the configuration form.
Accessing the Usage Notifications Configuration Form
A new menu item provides access to the Usage Notifications configuration form.
The path is: Applications>BackOfficeManagement>Customer Notifications> Usage Notifications.
The Usage Notification Configuration form, shown below, allows you configure Usage Notification rules by discount category and threshold level.
This form also provides global settings that govern system behavior related to RateBill operation processing, POS MakeSale and other areas of CostGuard related to Usage Notifications. Authorized users can add rules and adjust global settings and then submit the changes as a batch by clicking the Apply button.
The Apply button is disabled for unauthorized users.
The configurable fields and links on this form are described in Table 1 – Global Settings and Table 2 – Rules Settings.
Table 1 – Global Settings
Wait Period (Days) | Number of days the system waits before sending another notification for the same rule (discount category/threshold). Resets on each new Bill Period. Value Range = 1-31 (days) Default = 7 days |
Disable Opt-Out Option | Lets you enable/disable the opt-out option globally. This is needed in case a future regulation disallows opting out of usage notifications. When checked, the Opt-Out option is not displayed in the drop-down menu. Default = enable Opt-Out (unchecked) |
Display ‘Send Usage Notifications To’ Form for New Services in POS | Controls whether or not the Send Usage Notifications To form is displayed during POS Make Sale. If enabled (checked) the system displays the Send Notifications To form after the user clicks the Complete Sale button in POS Make Sale. If disabled, the system automatically applies the default setting (see below), and defaults can only be changed via the Edit Service form in Customer Management. Default = do not display (unchecked) |
Default Send Usage Notifications To | Establishes the default Send Usage Notifications To option. This default is automatically applied if the system is configured to not display the Send Usage Notifications To form during POS Make Sale. It also applies to the drop down menu on applicable forms. The choices are:
Default = Service Only |
Manage Templates link | This link launches the Customer Notifications Template Management form. When accessing the form via this link, the form is filtered to list Usage Notification templates only (templates associated with the Usage Notifications data source). The existing permissions associated with the customer notification framework template management functionality apply when managing Usage Notification templates. |
Table 2 – Rules Settings
Mark To Delete | Let’s authorized users delete a Usage Notification Configuration rule. Marked rows are deleted on saving changes (clicking Save). |
Discount Category | Discount category for which this rule applies.
|
Threshold Percentage | Percentage of total allotment used for the associated discount category that triggers a usage notification. Multiple thresholds (within reason) may be established for each discount category. Range = 1 – 100 |
Notification Template | Notification template used for this rule |
Delivery Type | The system supports:
Caution: If you offer SMS blocking products or a line of service that is not SMS-capable, be aware those customers will not be able to receive usage notifications by SMS. If you have services with SMS blocking, see 3.7 – Auditing Tips for Services with SMS Blocking. |
Enabled | Lets you enable/disable individual rules Unchecked (Disabled) by default |
Created By | User who created the rule |
Created | Date and time when the rule was created |
Modified By | User who modified the rule |
Last Modified | Date and time when the rule was modified |
Limiting Notifications Frequency in a Bill Period
You can ensure subscribers are not subjected to too many repeated notifications by configuring a wait period. This is done via the Usage Notifications Configuration form.
The wait period is defined as the number of days the system waits before sending another notification for the same rule (discount category/threshold). For example, where the wait period is seven days, if on one evaluation data usage is found to exceed 80%, and on the next evaluation data usage is found to exceed 82%, a second notice for exceeding 80% is not sent. Then, if one week later (within the same bill period) a subsequent evaluation finds data usage exceeds 82%, a second notice for exceeding 80% is sent.
The wait period resets at the start of each new bill period. For example, again using a seven-day wait period, a notification for reaching the 80% threshold is sent on the last day of the bill period. At the start of the next bill period both usage and wait period are reset. Then, just two days into the next bill period (and three days since the last 80% notification) the service reaches 80% again. In this case the wait period does not apply and a notification is sent.
Note:
If you want to ensure a maximum of one notification per threshold/discount category is sent per bill period, set the wait period equal to or greater than the duration of the bill period.
Configuring Rules
A rule consists of a discount category, threshold, and notification template and delivery method. All four columns are required. Once you start a new rule, the system does not let you click outside the row – not even to close the form until the rule is finished. If you wish to stop configuring a row once you’ve begun, press Esc.
Threshold Guidelines and Recommendations
Establish at least one threshold for each discount category. You may establish additional thresholds on each discount category (for example at 80%, 90% and 100%). Do not configure too many thresholds as this may negatively impact system performance, and could annoy customers (notification recipients). CostGuard does not enforce a limit, so it’s up to you to use discretion.
For simplicity, it is recommended that you configure the same thresholds for all discount categories, and not have different thresholds for minutes, messages, and data (i.e. avoid setting a threshold of 80% for minutes, 85% for messages and 75% for data). This is not enforced by the system, and does not impact system performance, so you are free to set different threshold for different discount categories if need be.
Rule Configuration Step-by-Step
To define a rule:
Select the discount category.
Note:
On starting the configuration of a rule, a new row is automatically inserted below.
Enter the threshold (for example 80 = 80%). You can enter the value directly or use the up/down arrows.
Select the template for the notification to be sent when this discount category/threshold is reached or exceeded. Any required customizations should be done prior to configuring rules. See Section 2.6 Configuring and Managing Notification Templates.
Select the delivery method.
The rule must be enabled (Enabled checkbox checked) in order to be used in the usage notification evaluation.
To set a second threshold (rule) for a discount category:
In the new row, select the same discount category as above and enter the second threshold (for example 90).
Repeat steps 3-5 to complete the rule configuration.
To temporarily disable a rule, uncheck the Enabled check box. To permanently remove a rule from the grid, click the Mark to Delete check box. The rule is deleted upon saving configuration changes.
Determining Who Receives Notifications
Where to send notifications for each service is configured on a service basis. There are two areas in CostGuard where you can perform this configuration – POS Make Sale and Customer Management.
The Send Notifications To form is displayed in POS Make Sale if the corresponding option is enabled via the Usage Notifications Configuration form. This form lets you configure this option for new services as they are added via Make Sale. If you choose not to display this form during Make Sale, services are initially configured with the default as set on the Usage Notifications Configuration form.
The default can always be changed through Customer Management – Edit Service form.
This section describes:
The Send Notifications To Options
Guidelines for accounts with multiple services
How to establish the primary service
Where to set Send Notifications To in POS Make Sale
Where to set Send Notifications To in Customer Management
Send Notifications To Options
The following options are available:
Both (Service and Primary Service) – Send notifications to this service and the account’s primary service
Service only – Send Notifications to this service
Primary Service only – Do not send notifications to this service. Send notifications to the primary service instead
Opt-Out – Do not send notifications for this service. This applies globally to all usage notifications.
Note:
This option is only available if the global setting, Disable Opt-Out Option, is unchecked.
For accounts with one service, the only logical choices are Service Only or Opt-Out. For accounts with multiple services, refer to the following scenarios for guidelines on how to configure each service.
Guidelines for Accounts with Multiple Services
For cases 1-3 presented below, the account has four services. Three services A, B & C (where A is the primary service) share a plan that provides 1000 free anytime minutes. The fourth service D has its own plan for 400 free anytime minutes and does not share in the 1000 free anytime minutes.
Case 1 – Primary Service Gets All Notifications & Child Services Get Their Own As Well
Primary service A wants to be notified when any one of the four services is in danger of exceeding their allotted usage. Also each individual service should be notified when they are in danger of exceeding their usage.
How to Configure
Service | Send Notifications To Setting |
|---|---|
A | Service only |
B | Service only |
C | Service only |
D | Both |
How it Works
Combined usage of anytime minutes for services A, B & C exceeds 800 in the bill period.
Services A, B & C receive notifications. (Service A receives just one notification.)
Service D uses in excess of 320 anytime minutes in the bill period.
Service D receives notification as does primary service A for service D approaching overage.
Case 2 – Notify Primary Only for the Shared Plan, Notify Service D Only for Its Plan
Services B & C need not be notified regarding the shared plan, and service A need not be notified regarding service D’s plan.
How to Configure
Service | Send Notifications To Setting |
|---|---|
A | Service only |
B | Opt-out |
C | Opt-out |
D | Service only |
How it Works
Combined usage of anytime minutes for services A, B & C exceeds 800 in the bill period.
Service A receives one notification. Services B & C do not receive a notification.
Service D uses in excess of 320 anytime minutes in the bill period.
Service D receives a notification. Service A does not.
Case 3 – Notify the Primary Service Only
Only the primary service should receive notifications. Services B, C and D need not be notified.
How to Configure
Service | Send Notifications To Setting |
|---|---|
A | Service only |
B | Opt-out |
C | Opt-out |
D | Primary Service only |
How it Works
Combined usage of anytime minutes for services A, B & C exceeds 800 in the bill period.
Service A receives one notification. Services B & C do not receive a notification.
Service D uses in excess of 320 anytime minutes in the bill period.
Service A receives a notification for service D. Service D does not receive a notification.
Case 4 – A Configuration to Avoid – Bombarding the Primary Service
This case does not include the fourth service (D). The account has three services A, B & C that share a plan for 1000 free anytime minutes. The primary service A wants to be notified; however, due to over-configuration it will receive three notifications for the same infraction.
Not Recommended Configuration
Service | Send Notifications To Setting |
|---|---|
A | Service only |
B | Both (or Primary Service Only) |
C | Both (or Primary Service Only) |
How it Works
Combined usage of anytime minutes for services A, B & C exceeds 800 in the bill period.
Service A receives three notifications (for itself and services B & C).
Services B & C may or may not receive notifications depending on their respective configurations.
How is the Primary Service Set?
When entering an order with multiple services, users need to know which service is the primary service when configuring the Send Notifications To option for each service.
By default the first service added to an account is assigned as the primary service. You can mark a different service as the primary service via the Edit Service form. This form is available via Customer Management, and may also be displayed during the Make Sale process. When processing an order with multiple services, use this form during the Make Sale process if you need to change the primary service assignment. This is demonstrated below.
Caution: The Collections workbook also uses the primary service setting for determining where to send collections-related notifications. Be aware that marking a service as the primary service on an account for usage notifications also impacts collections-related notifications and vice versa.
Send Notifications To Form in POS Make Sale
The Send Notifications To form is displayed in POS Make Sale if this option is enabled on the Usage Notifications Configuration form.
The Send Notifications To form is displayed after Complete Sale (after all services have been added to the order). The Send Notifications To form only displays new wireless services associated with the order.
Note:
The instructions on this form are hard-coded, so the Opt Out description will be included whether or not this option is enabled via the global settings.
Fields
Service Number | Service number associated with the wireless service. |
Send Usage Notifications To | Drop-down menu with the Send Notifications To options.
|
Send Notifications To Menu in Customer Management
The Edit Service Number form in Customer Management provides a Send Usage Notifications To drop down menu. This can be used to change the Send Notification To setting after sale.
Configuring and Managing Notification Templates
Notification messages are user-definable and associated to a rule by referencing a template.
What You Get Out-of-the-Box
One generic template is provided out-of-the-box. Users can configure additional templates as needed, or you may choose to have IDI make the changes for you via the Adaptive Request process.
The generic template covers both SMS and email. The only difference is that emails include a subject line. The system ignores the subject line for SMS notifications.
The main content of the notification template is as follows (where bracketed content is auto populated by the system):
Service Number {Merge Service # } has used {Merge Percent of Usage}% of its {Discount Category}. Please contact Customer Support for your available options to avoid paying overage charges.
Example: Service Number 5853149876 has used 84% of its Night & Weekend Minutes. Please contact Customer Support for your available options to avoid paying overage charges.
The default email subject line is as follows: Usage Notification Alert for [Service Number] – [DiscountCategory]
Example: Usage Notification Alert for 5853149876 – Night & Weekend Minutes
Managing Usage Notification Templates
The easiest way to access usage notification templates is via the Manage Templates link on the Usage Notification Configurations form.
This link launches the Template Management form with a filtered list that includes only usage notification templates. Other than filtering, this form operates the same as it currently does for all other notifications.
Note:
To list the Default Usage Notification template on this form, check the Show Protected Templates check box.
The Add/Edit Template Properties form lets you create notification templates and modify existing templates. For a new or existing notification template the system only allows the Usage Notifications data source to be selected for the Source field.
The figures below depict the Template Editor form for SMS and Email templates respectively. These forms let you customize the actual content of the notification template.
Template Editor (SMS Example)
Template Editor (Email Example)
Not Charging Subscribers for Notifications
The new Usage Management architecture in CostGuard software version 9.07 enables CostGuard users to ensure subscribers are not charged for usage notifications sent via SMS. This new architecture supports unbillable rules for configurable treatment of usage categories.
Note:
CostGuard users on versions with usage notification functionality prior to 9.07 will not be able to take advantage of unbillable rules as a way to ensure customers are not charged for usage notification SMS. These customers need to open ARs to make any necessary front end changes if they wish the SMS records to be bypassed. Otherwise, they will need to use existing functionality to ensure customers are not charged for these messages.
Bypassing usage Notification SMS – Orig Term Table Set up
In order to ensure usage notifications sent via SMS are not billed, those instances should be bypassed. This is configured in the Orig-Term Numbers table located in the Admin Console Data Management node. This sets up an unbillable rule in the CostGuard system to bypass the number used to send usage notification SMS messages.
Orig-Term Number Field | Value |
|---|---|
Front End ID | SMS |
Term Number | Customer supplied Short Code or 10 digit SMS number |
Service Type | Wireless |
Comparison | Equals or Starts or Ends |
Description | Customer supplied description. No pre-determined value needs to be entered here. |
Configuring the UnBillable Rule for SMS Usage Notifications
In order to use this functionality, custom derive bypass logic and a corresponding unbillable rule needs to be present. The unbillable rule configuration in CostGuard must be configured to have default action set to Bypass. This configuration is completed by IDI.
From the CostGuard Client main menu go to Applications > BackOffice Management > RateBill > RateBill Request Center.
In the RateBill Request Center, under Unbillable Management, click Rules.
On the Unbillable Rules form, select the Custom Rules group (typically abbreviated customer name), find the rule named SMS from Customer Service not loaded (or simply SMS not loaded) and set the Default Action to Bypass Record.
Managing the Usage Evaluation Operation
There is a new RateBill operation called Usage Notification in the RateBill Request Wizard. The IDI Billing Team configures and schedules this operation to run at an appropriate time during the Rating & Billing processes. This operation runs once per day. Customers must coordinate with IDI to ensure the operation is scheduled to occur at the appropriate time that best fits their application.
.png?sv=2026-02-06&spr=https&st=2026-08-05T21%3A45%3A38Z&se=2026-08-05T22%3A20%3A38Z&sr=c&sp=r&sig=moK4GoDufWR5LBxHyZ3gSjLQVe7dhWaqckhMSoxclKE%3D)
New operation Usage Notification on RB Request Wizard operations form
The operation is typically run across all open bill periods for all services. When needed, the operation may be run on a single bill period, with the option to specify one or more customer account(s).
.png?sv=2026-02-06&spr=https&st=2026-08-05T21%3A45%3A38Z&se=2026-08-05T22%3A20%3A38Z&sr=c&sp=r&sig=moK4GoDufWR5LBxHyZ3gSjLQVe7dhWaqckhMSoxclKE%3D)
Form for selecting type of Usage Notificationoperation
Form for selecting bill period and optionally customeraccount(s)
Using the Audit Reports
Six CostGuard reports support monitoring usage notification functionality in CostGuard.
Report Name | Main/Drill Down | Description |
|---|---|---|
Usage Notification History | Main | List the Usage Notification Request Details that ran during a specified date range |
Usage Notification By Discount Category & Threshold | Drill-down | List the Usage Notification totals by discount category and threshold for a selected Request Detail |
Usage Notification Detail | Drill-down | List the Usage Notification Request details by service number |
Usage Notification Configuration Summary | Main | Indicate the number of services using each send notification to option |
Usage Notification Configuration By Account Type | Drill-down | Indicate the number of services using each send notification to option by Account Type |
Usage Notification Configuration Detail | Drill-down | List the services using a selected send notification to option |
Usage Notification History
This report provides a history of usage notification request detail operations that ran during a specified date range. It shows the number of services and number of notifications by request detail ID.
Note:
Request Detail Operation refers to the Rate Bill Operation that evaluates usage for usage notifications.
This report is available via the Report Explorer. For each request detail, this report returns:
Request Detail ID
Start and End date & time
Status
Number of services for which notifications were sent
Number of notifications sent
This report lets users drill down for more detail by double-clicking a selected row. Two drill down levels are available:
From the main report users can select a request detail (row) and view notifications for the selected request detail by discount category and threshold (3.2).
From the first drill down users can select a row and view notification details based on discount category and threshold (3.3).
Usage Notification By Discount Category and Threshold
This report is run as a drill-down from the Usage Notification History report. It lists the notifications for a selected request detail by discount category and notification type. The date range is the same as the main report.
For the selected request detail, this report returns:
Request Detail ID
Start and End date & time
The discount category
The type of notification (threshold)
Number of notifications sent for a discount category and notification type – A total count for this column is provided in the last row
Number of services for which notifications were sent – A total count for this column is provided in the last row
From this report users can select a row and view notification details based on discount category and threshold (see below).
Usage Notification Detail
This report is run as a drill-down from the Usage Notification By Discount Category and Threshold report. It provides details on notifications sent (or not sent) for a selected discount category and threshold based on the request detail represented in the Usage Notification By Discount Category and Threshold report. The date range is the same as the main report.
For each row (notification or no notification instance), this report returns:
Request Detail ID
Account number
Customer name
Bill period end date
Service number
Service configuration (Send Notifications To option)
Whether or not this is the primary service
Discount category
Allotted units
Units used (raw quantity)
Units used as a percentage
Whether or not a notification was sent
Template Name
Notification (evaluation) date
From this report users can select a row and, for the associated service number, open the customer window to the Notifications tab.
Usage Notification Configuration Summary
This report, available via the Report Explorer, indicates the number of services using each Send NotificationsTo option. This report lets users drill down for more detail by double-clicking a selected row. Two drill down levels are available:
From the main report users can select the row for a Send NotificationTo option and view the number of services configured to use that option by account type (3.5).
From the first drill down users can select the row for a Send Notification To option and view the services configured to use that option (3.6).
Usage Notification Configuration By Account Type
This report indicates the number of services using a selected Send NotificationTo option by Account Type. It’s run as a drill-down from the Usage Notification Configuration Summary report. For each row (Account Type), this report returns the following information:
Account Type
Number of Services using the selected Send Notification To option – A total count for this column is provided in the last row
From this report users can select the row for a Send NotificationTo option and view the services configured to use that option (see below).
Usage Notification Configuration Detail
This report lists the services configured for a selected send notification group.
It’s run as a drill-down from the Usage Notification Configuration By Account Type report. For each service, this report returns the following information:
Account Number
Customer Name
Bill period end date
Service Number
Whether or not this is the primary service
From this report users can select a row and, for the associated service number, open the customer window to the Services tab.
Auditing Tips for Services With SMS Blocking
If you have services with SMS blocking and need to determine whether or not any of those services should have received a usage notification:
Generate a list of services that have an SMS blocking product.
Run the CostGuard report – Usage Notification Detail report. This report is run by drilling down from the Usage Notification History and then Usage Notification By Discount Category and Threshold reports. It shows usage notification activity by service, including the units used as a percentage and an indication whether or not a notification was sent.
Compare the lists to find services with SMS blocking that exceeded a usage threshold.
Notify subscribers manually (outside of CostGuard) as needed.