...
Most settings can be changed whilst your team are dialing and will take affect almost immediately. Settings under the above Fields tab (don't confuse this with the list of fields below which can be changed at any time) are the only aspect of the Campaign Template that cannot be changed whilst staff are dialing.
Fields
| Field | Description |
|---|---|
| Name | A unique name for this Campaign Template. |
| Description | A description of the purpose of this Template which will help you or someone else remember the purpose of this template in 2 years time. |
| Show Contact Hours | Controls whether Contact Hours is displayed to the agent when using the Dialer. You may want to show the Contact Hours to the agent to assist them in scheduling a callback during an appropriate time for the Customer. This is useful when calling customers that live in a different timezone as the agent. If you select the 'Editable' option then the Agent can modify the customers contact hours on the lead. This will affect when the dialer will schedule calls to the customer as we will only call the customer during the leads Contact Hours. |
| Contact Hours | Sets the default Contact Hours for leads imported into this Campaign Template. You can override individual Contact Hours for a lead by adding a column with the heading 'njContactHours' to the csv files you import with the name of the appropriate Contact Hours. |
| Team | Defines the team that has access to this Campaign Template and associated Campaigns and Allocations. The default Team 'Global' means that all user have access. You can create a Team via the 'Users | Team Management'. |
| Callback Availability | Controls how Client Approved Callbacks are handled when staff are working on Allocations from this Campaign Template. NOTE: this setting controls whether callbacks from 'Other' Allocations are presented to the agent. If a Client Approved Callback is due in Allocation 'A' and Agent that owns the Callback is working on Allocation 'B' the Callback Availability setting will determine whether the callback is delivered to the Agent. There are three Availability settings: Global - Callbacks from any Allocation (regardless of Campaign Template) will be delivered to the Agent when working on Allocations from this Campaign Template. Template - Callbacks from Allocations owned by this Template will be delivered providing the Agent is working on an Allocation that belongs to this Campaign Template. Standard - the Callback will only be delivered if the agent is working in the same Allocation that the Callback belongs to. You can also suspend callbacks completely from the Allocation screen. |
| Disposition Set | The disposition set that will be made available to Agents to select from when dialing. |
| Stop code Set | The Stop code set that will be made available to Agents to select from when the stop the dialer. |
| Hide CallerId | If check then the all calls from Allocations belonging to this Campaign Template will not show a Caller Id. Note: for this to work your telephone Trunk must be configured correctly. Contact Noojee support if you are unsure. Also note that in some circumstances it is illegal to hide your caller id. |
| Caller Id | The Caller ID to display when calling from Allocations belonging to this Campaign Template. Note: for this to work your telephone Trunk must be configured correctly. Contact Noojee support if you are unsure. |
| Voicemail Route | Noojee Campaigner has the ability to deliver a pre-recorded message to a customer if their answering machine answers the call. If a Voicemail Route is selected the Agent will be given the ability to click a 'Voicemail' button when a call is answered by them but they note that they have been connected to a Voicemail box. Clicking the voicemail box will send the call to the selected route and free the Agent to move on to the next lead. You must have first configured a valid route. The route would normally just play a message and hangup the call. |
| Callback priority threshold for reporting. | A number of reports display information regarding callbacks. This threshold will basically exclude any callbacks that have a priority below the given threshold. |
| Enable Deduplication | If check than this Campaign Template supports the advanced deduplication mode. |
| De-dupe threshold | The De-dupe threshold is an integer (normally 100) that serves as a threshold above which a lead is considered a deduplicate. Using the Campaign Template 'Fields' tab you can assign Deduplication Points to each field. When considering if a lead is a duplicate each field of a lead is matched to the corresponding field in each of the leads in the Deduping Campaign. For each field that matches the Deduplication points are accumulated. If the total points accumulated matches or exceeds the De-dupe threshold then the lead is considered a duplicate and rejected. As an example you might set the de-dupe threshold to 100. Any phone fields and email fields should be assigned 100 deduping points as a match on any of these fields indicates that we have a duplicate lead. Fields like Firstname and Surname however aren't considered sufficient in their own right to be considered a duplicate. So in this case you you should give each of these fields a value less than 100. A good example might be that we consider that a matching Firstname, Surname and Post code constitutes a duplicate. In that case we might give the following points: Firstname: 40 Surname: 40 Postcode: 20 You may also give other fields points. Remember that when ANY combination of fields accumulates to the threshold then the lead will be considered a duplicate. |