Advanced Campaign Configuration

overview the advanced settings tab in campaign configuration is where administrators define the core, often technical, operational parameters for a specific campaign these settings control the campaign’s data sources, disposition logic, user interface, and outbound dialing algorithm performance by customizing these values, administrators can optimize the campaign's efficiency, data handling, and compliance parameter explanations data and interface definitions associated table definition function this parameter specifies the data table structure that the campaign uses to store and retrieve customer related information example if set to defaulttabledefinition, the campaign uses the primary, predefined table structure for all its customer data needs by default assign users to agent table definition function this parameter selects the template or layout that determines how customer information is displayed to agents on their console for this specific campaign, including which fields they can view or edit example if set to defaultagenttabledefinition, agents see the standard, pre configured view of the customer record column mappings function this policy defines how the columns (fields) of the data file or source are mapped and aligned with the internal column names of the database table, ensuring data integrity during upload or retrieval example if set to defaultoutboundcolumnmapping, the campaign follows the standard rules for aligning outbound related data fields dialer and data retrieval customer provider type function this parameter selects the dialer algorithm or logic used to select and queue customer records from the database for outbound dialing it is crucial for campaign performance and pacing options options include campaign based customer provider, lead based customer provider, and pace based customer provider, each having a distinct method for lead prioritization and retrieval min cache size function this defines the minimum size of the cache (measured in the number of customer records) that the customer provider (dialer algorithm) must maintain at a given time this value is used to ensure a continuous supply of numbers for dialing example a value of 1000 means the dialer always tries to keep at least 1,000 records ready in its memory cache fetch size function this value specifies the number of customer records the dialer retrieves from the database in a single query when refilling its cache example a value of 500 means the dialer executes a query to fetch 500 records whenever the cache drops below a certain threshold operational and compliance disposition plan function this selects the specific plan that dictates which disposition codes (reasons for the call outcome, like "sale," "busy," "dnc") and corresponding disposition classes are available for agents to use when wrapping up a call example if set to defaultovcdispositionplan, the campaign uses the standard set of wrap up codes for outbound voice campaigns restrict disposition from telephony panel function when enabled, this setting prevents agents from submitting a disposition code via their telephony panel the agent is thus forced to dispose of the call through the crm (customer relationship management) only purpose this prevents agents from submitting conflicting or duplicate disposition codes, ensuring data is consistently managed in the crm no of last calls function this parameter specifies the maximum number of previous call records (history) the system maintains and displays for a specific customer within this campaign example a value of 10 means the agent will see a history of the last 10 interactions with that customer file format function this determines the specific audio file format used by the system for saving all call recordings (voicelogs) generated by the campaign example options include formats like tulaw, alaw, tgsm, tg729, or the default talaw prerequisites the campaign must be a voice campaign (outbound, predictive, or interactive voice application) associated system objects such as table definitions and disposition plans must be pre configured and available in the system before they can be selected in the campaign's advanced settings