|
To add an auto contact task to 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 to which you want to add an auto contact task.
The Strategy Definition screen appears.
In the Branch
section, select view/edit in the row for the branch to which you want
to add the auto contact task.
The Branch Definition screen appears.
In the Tasks
section, click Add.
The Task Definition screen appears.
Enter the task
name and the number of offset days for the task. eCredit calculates the
task due date by adding the offset date for the branch to the branch control
date, and then adding the offset days for the task to that date.
Select Yes
for the Auto option button.
Optionally,
if the autonomous task will ever be converted to a work queue action item,
select the priority for the task. The priority appears in the collector's
work queue.
Select the
Action Type as Contact.
The screen refreshes to display the fields for contact tasks.
Enter or select
the following for the Contact task:
The Contact
Type that describes the role that the contact performs, such as bank,
sales, or company rep. The contact
sent for the invoice or customer must match the contact category and type
defined for the task.
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.
The template
to use for the 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:
If you select Yes, if the auto Contact task fails, an action item for
the collector is created so that the collector can troubleshoot the problem
and resend the message.
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
If your implementation
is not set up for grouping, you
can select one of the following for Schedule Mode:
Click Save.
|