PeopleSoft Enterprise Bill Presentment and Account Management 9.1 PeopleBook

Setting Up Prepaid Account Management

This chapter provides an overview of prepaid consumers and discusses how to:

Set up the prepaid consumer customer identity.
Set up a communications business unit.
Enable alerts and scripts for account management.

Understanding Prepaid Consumers

A prepaid consumer is anonymous and no records are retained on the system. The order uses this customer when a prepaid account order is placed and the customer is not identified. In order to use this functionality you must set up a prepaid customer in the CDM and associate this customer to the communications setup. The prepaid consumer has the Billing Account Administrator role to ensure they can create accounts.

Setting up the Prepaid Consumer Customer Identity

This section discusses how to set up the prepaid consumer customer identity.

Page Used to Set Up the Prepaid Consumer Customer Identity

Page Name	Definition Name	Navigation	Usage
Communications Setup	RBT_CONFIG_PG	Set Up CRM, Product Related, Communications, Communications Setup	Create a customer used when a prepaid account order is placed and the customer is not identified.

Setting up the Prepaid Consumer Customer Identity

Access the Communications Setup page (Set Up CRM, Product Related, Communications, Communications Setup).

Set the PREPAIDFIRST and PREPAIDLAST to the first and last name of the consumer. The Order process will use the prepaid consumer when a prepaid account order is placed and the customer is not identified.

A consumer needs to be created in CDM that can be used in place of a real consumer for Prepaid Services. This consumer will be used if the customer purchasing the prepaid service does not want to be identified. This consumer must have Sold To Consumer, Bill To Consumer, and Ship To Consumer purchasing options selected. In addition, on the Relationships page the consumer must have the Billing Account Administrator role to ensure they can create accounts. Once a consumer has been created, the Communications Setup can be modified to use that consumer.

Setting Up a Communications Business Unit

This section discusses how to set up a communications business unit for Prepaid Accounts.

Page Used to Set Up a Communications Business Unit

Page Name	Definition Name	Navigation	Usage
Communications	BUS_UNIT_RBT	Set Up CRM, Business Unit Related, Order Capture Definition, Communications	Set up communication industry information for Order Capture business units.

Setting Up a Communications Business Unit

Access the Communications page (Set Up CRM, Business Unit Related, Order Capture Definition, Communications).

Note. The Communications page is used to set up a number of the order capture functions specifically designed for the communications industry. This section discusses only those fields applicable to prepaid accounts.

See Defining Order Capture Business Units.

Prepaid Accounts

Prepaid Accounts Allowed	Select to enable prepaid accounts.
Threshold Amount	Enter the default threshold for threshold recurring. This amount is used as the default when setting up a Prepaid Account that will use threshold recurring — meaning that when the account balance reaches the specified dollar amount, an automatic top-up request is placed.
Auto Load	Set up whether or not the prepaid customer should automatically be loaded when using Add Prepaid Service from 360. A storefront may want to have the prepaid customer pre-loaded with each prepaid order, however a call center would not. With a call center, because of fulfillment, the customer needs to be identified.
Do Not Contact	Establish the default setting for whether or not Do Not Contact is selected in the CDM.
Security Question	Set up a default for the security question.

Enabling Alerts and Scripts for Account Management

Active Analytics Framework (AAF) is a decision-making system that invokes actions based upon the evaluation of user-defined business rules.

The policy builder provides a user-friendly environment for functional users to construct policies in a natural business language. A policy consists of three parts—a trigger point, conditions and actions:

Trigger points. A trigger point is the occurrence of an event that triggers the evaluation of conditions in policies associated with it. For example the customer calls into a call center and asks about his account.
Conditions. A condition is the if statement, which specifies under what circumstance would some action be performed. In this example, the system checks the account balance against the threshold, and the balance is below the threshold.
Actions. An action is the then statement, which is invoked if the associated conditions are evaluated to true. The system displays an alert message on screen to indicate that the account should be topped up.

Additional examples of alerts include:

The customer calls into a call center and asks a question about his account. When the account is brought up, an AAF policy fires if the account is prepaid. This policy attempts to upsell the customer and convince them to convert to a postpaid account.
The customer calls into a call center and asks a question about his account. When the account is brought up, an AAF policy fires if there is no customer information available for the account. The policy's intent is to get customer information by offering a cross sell product at a reduced price.

Policies are sample data. Three trigger points have been added to allow AAF processing in the account component — When Account Balance is Updated, When Account is Displayed, and After an Account is Saved. With these trigger points, new AAF Policies can be created to manage accounts.

See Working with Active Analytics Framework.