|
|
You can modify any information for a strategy at any
time. However, if the strategy is associated with a segment as a Champion
or Challenger strategy, when comparing effectiveness metrics, select dates
so that you are not mixing effectiveness metrics for the period before
and after the changes were made.
To modify autonomous tasks for a strategy branch:
Select Admin.
The Admin Home Page appears. From the Policy
Administration tab, select Strategy Setup.
The Strategies screen appears. Select view/edit
in the row for the strategy for which you want to modify an auto contact
task.
The Strategy Definition screen appears. In the Branches
section, select view/edit in the row for the branch that has the auto
contact task you want to modify. The Task Type column lists Auto for autonomous
tasks.
The Branch Definition screen appears. In the Tasks
section, click view/edit in the row for the auto contact task.
The Task Definition screen appears. You can change
any of the following information for the task:
Note: You can
change the Auto selection to Yes to make this auto task a collector task.
In this case, you enter the information required for the contact task
type you select.
Task name Number of offset
days Priority for
the task. For an autonomous task, the priority is only relevant if the
task will ever be converted to an action item in a collector's Work Queue,
that is, if Error Notification is set to Yes.
The Contact
Category as external or internal to your organization. The contact category
helps to determine the contact who receives the correspondence, and must
match a contact entered for the invoice or customer. The Contact
Type that describes the role that the contact performs, such as bank,
sales, or company rep. For the message to be successfully sent, there
must be a contact of the contact type and category entered for the invoice
or customer. Is primary
to determine if the contact to receive the correspondence is the primary
contact for the invoice. The contact entered for the invoice or customer
should match the 'Is Primary' selection you make. Look Ahead
days to determine the number of days to look ahead for correspondence
action items that use the same template and are for the same contact using
the same address. Look ahead days are used differently depending on whether
or not your eCredit implementation is set up to group the same action
items for multiple invoices into a single correspondence. The Primary,
Secondary, and Tertiary Delivery Methods. The primary method is used if
sufficient address information is entered for the contact specified for
the task. The secondary method is used if sufficient information is not
available for the primary method. The tertiary method is used if sufficient
information is not available for the secondary method. Error Notification:
Select Yes or No. If Yes, an action item is created for the correspondence
if eCredit fails to send it.
If your implementation
is not set up for grouping, you
can change the Schedule Mode as follows:
Sequenced:
The task executes when its due date is reached and when all tasks with
previous due dates have executed Dependent:
The task executes when its due date is reached, and another, specified
task in the branch has executed If your implementation
is not set up for grouping, you
can select one of the following for Confirmation Mode. Confirmation Mode
converts an autonomous correspondence task to a user interactive task.
When Promise
of Dispute is Active: eCredit convert the autonomous task to an action
item in a user's work queue when a dispute or promise is active. Never: the
task is always autonomous Always: the
task always becomes a user-interactive task
Click Save. |
