How to Configure ViciDial Script Tab — Agent Call Scripts

Configuring ViciDial Script Tab for Agent Call Scripts involves several steps. First, ensure your ViciDial installation is up-to-date (version 2.9 or higher) and that you have root or sudo access to the server. You'll also need MySQL/MariaDB access with credentials for the asterisk database, understanding of ViciDial user roles, a text editor, and access to the ViciDial web administration interface.

Understanding ViciDial script architecture is crucial. Call scripts are customizable templates that agents view during active calls, serving purposes like visual guidance, dynamic variable substitution, call flow logic, and customizable HTML/plain text rendering. The script processing flow involves retrieving the assigned script, parsing special syntax tokens, substituting lead-specific variables, rendering the script in real-time, and logging interactions.

The core script tables in ViciDial's MySQL database include vicidial_scripts and vicidial_campaigns. The vicidial_scripts table stores script information with columns like script_id (primary key), script_name, script_text (script content), script_lang (language code), active (enable/disable status), user_group (restrict to specific user groups), and timestamps for creation and modification.

The vicidial_campaigns table links scripts to campaigns, with columns like campaign_id, campaign_name, script_id, and script_screen (determines when the script displays).

To create your first agent call script, connect to the ViciDial database using the mysql command, insert a basic script with a simple inbound support message, verify the insertion, and then create an advanced script with HTML formatting for more sophisticated agent screen rendering. Remember to link the script to the appropriate campaign using MySQL updates.