CT Center Documentation > Reference Manual Menu
·
Why
aren’t all of the selected accounts in the campaign?
·
Can/should
we allow yesterday’s campaign to be dialed today?
·
When
campaigns are built automatically, what time are they built?
·
How can we add
extra phone or data fields to campaign data?
·
How can we
either include or exclude from dialing accounts with a future next work date?
·
How are
packets handled in building campaigns?
·
How are
packet members updated when processing dialer results?
·
Why are there
timing conflicts between Cubs and dialer logs?
·
Why
didn’t the interactive IO recognize a changed configuration option
immediately?
·
Why aren’t result codes tied to Cubs’ action codes?
·
Why
does IAT support say that Cubs is not responding?
After having been selected, but before being included in a campaign, all accounts go through an exclusion process. The multiple reasons why an account may be excluded are fully explained in the “Exclusions” section of the “Campaign Building Logic” documentation page. For any particular campaign, a recap of build-time exclusion counts can be found in the detail screen of the Campaign Query screen.
There is nothing in the software to stop you from doing this. However, we don’t recommend it for a couple of reasons:
- The various attributes of accounts which are used to select them for campaigns can change from day to day. It would be best to re-select yesterday’s campaign, making it a fresh list as of today.
- When batch or CTImpact campaigns are built, the accounts added to the campaign have their WIPs marked as having been worked. Overnight, the WIPs get rebuilt, so if you are dialing from yesterday’s batch campaign, it is possible to contact an account twice (once with the dialer and once through the WIP) opening yourself up to complaints of harassment.
The program which automatically builds scheduled campaigns has been added to the end of your dayend processing as part of the interface software installation. It must be run after WIPs are built because one of the build strategies works off of the current WIP, and because some of the campaign types (batch and CTImpact) update the WIP for accounts on those campaigns as having been worked. There is no way to reliably predict exactly when the automatic campaign building will take place. It is entirely dependent upon the start time of the dayend process and the duration of the programs which are executed before it.
At the request of IAT, adding extra fields to the campaign detail data records is restricted to Cubs Consulting, Inc. personnel. Their reasoning is that any changes to campaign data will affect the CTCenter software and so must be carefully coordinated between the 2 platforms. If you would like to add extra phone or data fields to the campaign interface, please contact CCI or IAT, and it will be taken care of for you.
There is a switch that you can configure at the bottom of the top section of the Processing Parameters Definition screen.
The usage of packet data in building campaigns is explained in the “Packet Data” section of the “Campaign Building Logic” documentation page.
Documentation in process...
Documentation in process...
Documentation in process...
Documentation in process...
Documentation in process...
Documentation in process...
Copyright 2009, Cubs Consulting, Inc.