CT Center Documentation > Reference Manual Menu
The CT Center interface has the ability to produce batch campaign files and to process batch result files. The actual dialing for these campaigns might be performed by your in-house dialer, IAT’s hosted CTImpact service, or some other outside hosted dialing service which complies with our standard file formats, which are defined below.
Standard campaign files are tab-delimited ASCII files which are written to your configured CTD (Cubs-To-Dialer) folder. The first record in the file consists of field headers and the second and subsequent records consist of data fields. Here is the layout for the data in the batch campaign files built by the CT Center interface:
Field# |
Header Text |
Data Source |
Notes |
1 |
ACCT_ID |
Dnum |
|
2 |
LAST_NAME |
D2.1 |
|
3 |
FIRST_NAME |
D2.1 |
|
4 |
CLI_ID |
D1 |
|
5 |
CLI_NAME |
CLI 1.1 |
|
6 |
LOGON |
|
Cubs account |
7 |
DESK |
D10 |
|
8 |
CAMPAIGN |
|
As defined in the Campaign Definition screens |
9 |
CALLBK_PHN |
|
As defined for the logon in the Process Parameter screen |
10 |
HOME_PHN |
D8 |
|
11 |
EMP1_PHN |
F36 |
|
12 |
EMP2_PHN |
F40 |
|
13 |
ALTPYR_PHN |
F45 |
|
14-x |
|
|
Extra phone numbers from FISCAL, as configured |
x-y |
|
|
Extra DEBTOR or FISCAL data fields, as configured |
Not all of the data returned by CT Center is actually used by the Cubs interface. Only those data elements which are used are defined below:
Field# |
Description |
Notes |
1 |
|
|
2 |
Dnum |
|
3 |
Phone Number |
|
4 |
|
|
5 |
Result Code |
|
6 |
Call Date |
YYYYMMDD |
7 |
Call Time |
HHMMSS |
8 |
Campaign |
|
9 |
|
|
10 |
|
|
11 |
|
|
12 |
Logon |
|
13 |
Agent ID |
|
Copyright 2010, Cubs Consulting, Inc.