help_documentation
Σύνολο εγγραφών στον πίνακα: 1581
| help_id | help_title | help_text |
|---|---|---|
| settings-alt_log_server_ip | Alt-Log DB Server | <QXZ>This is the alternate log database server. This is optional, and allows some logs to be written to a separate database. Default is empty.</QXZ> |
| settings-alt_log_dbname | Alt-Log DB Name | <QXZ>The database name for the Alt-Log database. Default is empty.</QXZ> |
| settings-alt_log_login | Alt-Log DB Login | <QXZ>The login user for the Alt-Log database. Default is empty.</QXZ> |
| settings-alt_log_pass | Alt-Log DB Password | <QXZ>The password for the Alt-Log database. Default is empty.</QXZ> |
| settings-tables_use_alt_log_db | Alt-Log Tables | <QXZ>These are the tables that are available for logging on the alternate log database server. Default is blank.</QXZ> |
| settings-enable_queuemetrics_logging | Enable QueueMetrics Logging | <QXZ>This setting allows you to define whether the system will insert log entries into the queue_log database table as Asterisk Queues activity does. QueueMetrics is a standalone, closed-source statistical analysis program. You must have QueueMetrics already installed and configured before enabling this feature. Default is 0.</QXZ> |
| settings-queuemetrics_server_ip | QueueMetrics Server IP | <QXZ>This is the IP address of the database for your QueueMetrics installation.</QXZ> |
| settings-queuemetrics_dbname | QueueMetrics Database Name | <QXZ>This is the database name for your QueueMetrics database.</QXZ> |
| settings-queuemetrics_login | QueueMetrics Database Login | <QXZ>This is the user name used to log in to your QueueMetrics database.</QXZ> |
| settings-queuemetrics_pass | QueueMetrics Database Password | <QXZ>This is the password used to log in to your QueueMetrics database.</QXZ> |
| settings-queuemetrics_url | QueueMetrics URL | <QXZ>This is the URL or web site address used to get to your QueueMetrics installation.</QXZ> |
| settings-queuemetrics_log_id | QueueMetrics Log ID | <QXZ>This is the server ID that all contact center logs going into the QueueMetrics database will use as an identifier for each record.</QXZ> |
| settings-queuemetrics_eq_prepend | QueueMetrics EnterQueue Prepend | <QXZ>This field is used to allow for prepending of one of the list data fields in front of the phone number of the customer for customized QueueMetrics reports. Default is NONE to not populate anything.</QXZ> |
| settings-queuemetrics_loginout | QueueMetrics Login-Out | <QXZ>This option affects how the system will log the logins and logouts of an agent in the queue_log. Default is STANDARD to use standard AGENTLOGIN AGENTLOGOFF, CALLBACK will use AGENTCALLBACKLOGIN and AGENTCALLBACKLOGOFF that QM will parse differently, NONE will not log any logins and logouts within queue_log.</QXZ> |
| settings-queuemetrics_callstatus | QueueMetrics CallStatus | <QXZ>This option if set to 0 will not put in the CALLSTATUS entry into queue_log when an agent dispositions a call. Default is 1 for enabled.</QXZ> |
| settings-queuemetrics_addmember_enabled | QueueMetrics Addmember Enabled | <QXZ>This option if set to 1 will generate ADDMEMBER2 and REMOVEMEMBER entries in queue_log. Default is 0 for disabled.</QXZ> |
| settings-queuemetrics_dispo_pause | QueueMetrics Dispo Pause Code | <QXZ>This option, if populated, allows you to define whether a dispo pause code is entered into queue_log when an agent is in dispo status. Default is empty for disabled.</QXZ> |
| settings-queuemetrics_pause_type | QueueMetrics Pause Type Logging | <QXZ>If enabled, this option will log the type of pause in the queue_log table data5 field. You must make sure that you have a data5 field or enabling this feature will break QM compatibility. Default is 0 for disabled.</QXZ> |
| settings-queuemetrics_pausereason | QueueMetrics PAUSEREASON Logging | <QXZ>If set to EVERY_NEW, this will start a new pause session within the queue log for each pause code that happens, starting when the pause code is set. The STANDARD default behavior is for QM to only use the last PAUSEREASON in any single pause session in its reports. Default is STANDARD.</QXZ> |
| settings-queuemetrics_pe_phone_append | QueueMetrics Phone Environment Phone Append | <QXZ>This option, if enabled, will append the agent phone login to the data4 record in the queue log table if the Campaign Phone Environment field is populated. Default is 0 for disabled.</QXZ> |
| settings-queuemetrics_record_hold | QueueMetrics Hold Call Log | <QXZ>This option, if enabled, will log when a customer is put on hold and taken off hold in the newer record_tags QM table. Default is 0 for disabled.</QXZ> |
| settings-queuemetrics_socket | QueueMetrics Socket Send | <QXZ>This option, if enabled, will send QM data to a web page that will send it through a socket for logging. The CONNECT_COMPLETE option will send CONNECT, COMPLETEAGENT and COMPLETECALLER events to the url defined below. Default is NONE for disabled.</QXZ> |
| settings-queuemetrics_socket_url | QueueMetrics Socket Send URL | <QXZ>If Socket Send is enabled above, this is the URL that is used to send the data to. Default is EMPTY for disabled.</QXZ> |
| settings-enable_vtiger_integration | Enable Vtiger Integration | <QXZ>This setting allows you to enable Vtiger integration with the system. Currently links to Vtiger admin and search as well as user replication are the only integration features available. Default is 0.</QXZ> |
| settings-vtiger_server_ip | Vtiger DB Server IP | <QXZ>This is the IP address of the database for your Vtiger installation.</QXZ> |
| settings-vtiger_dbname | Vtiger Database Name | <QXZ>This is the database name for your Vtiger database.</QXZ> |
| settings-vtiger_login | Vtiger Database Login | <QXZ>This is the user name used to log in to your Vtiger database.</QXZ> |
| settings-vtiger_pass | Vtiger Database Password | <QXZ>This is the password used to log in to your Vtiger database.</QXZ> |
| settings-vtiger_url | Vtiger URL | <QXZ>This is the URL or web site address used to get to your Vtiger installation.</QXZ> |
| settings-webphone_url | Webphone URL | <QXZ>The URL of the web phone inteface.</QXZ> |
| system_statuses | System Statuses | <QXZ>Through the use of system statuses, you can have statuses that exist for all campaigns and in-groups. The status must be 1-6 characters in length, the description must be 2-30 characters in length and Selectable defines whether it shows up in the system as an agent disposition. The human_answered field is used when calculating the drop percentage, or abandon rate. Setting human_answered to Y will use this status when counting the human-answered calls. The Category option allows you to group several statuses into a category that can be used for statistical analysis. There are also 7 additional settings that will define the kind of status: sale, dnc, customer contact, not interested, unworkable, scheduled callback, completed. The MIN SEC and MAX SEC fields for each status will determine whether an agent can select that status at the end of their call based upon the length of the call. If the call is 10 seconds and the MIN SEC for a status is set to 20 seconds, then the agent will not be able to select that status. Also, if a call is 40 seconds and the MAX SEC for a status is set to 30 seconds, then the agent will not be able to select that status.</QXZ> |
| admin_phones_bulk_insert-login_password | Login Password | <QXZ>This is the agent screen login password that will be used for all of the phones that are created.</QXZ> |
| admin_phones_bulk_insert-create_alias | Create Alias Entries | <QXZ>Setting this option to YES will create a phones alias entry for each of the extensions listed above that will tie all of the same extension entries on each server together allowing phone login load balancing to work in the agent interface.</QXZ> |
| admin_phones_bulk_insert-alias_suffix | Alias Suffix | <QXZ>This is the suffix that will be added to the extension to form the phone alias id. For example, if the extension is cc100 and the alias suffix is x, then the phone alias id used for that would be cc100x.</QXZ> |
| admin_phones_bulk_insert-protocol | Client Protocol | <QXZ>This is the phone protocol that will be used for all phones created when submitted. SIP, PJSIP and IAX2 are VOIP protocols that will create conf file entries to allow those phoens to register on the servers.</QXZ> |
| status_groups | Status Groups | <QXZ>Through the use of status groups, you can have statuses that exist for lists or in-groups specifically. The Status must be 1-6 characters in length, the description must be 2-30 characters in length and Selectable defines whether it shows up in the system as an agent disposition. The human_answered field is used when calculating the drop percentage, or abandon rate. Setting human_answered to Y will use this status when counting the human-answered calls. The Category option allows you to group several statuses into a category that can be used for statistical analysis. There are also 7 additional settings that will define the kind of status: sale, dnc, customer contact, not interested, unworkable, scheduled callback, completed. The MIN SEC and MAX SEC fields for each status will determine whether an agent can select that status at the end of their call based upon the length of the call. If the call is 10 seconds and the MIN SEC for a status is set to 20 seconds, then the agent will not be able to select that status. Also, if a call is 40 seconds and the MAX SEC for a status is set to 30 seconds, then the agent will not be able to select that status. The Status Group ID field must be between 2 and 20 characters in length, must not match a current campaign ID, and cannot contain spaces or other special characters.</QXZ> |
| inbound_groups-populate_lead_vendor | Populate Lead Vendor | <QXZ>If this option is not DISABLED, and the inbound call was not delivered with a VID option, then the system will put the value entered in this setting into the vendor_lead_code field when a new lead is inserted. Special options include INBOUND_NUMBER which will use the inbound phone number dialed. Default is INBOUND_NUMBER.</QXZ> |
| inbound_groups-populate_lead_comments | Populate Lead Comments | <QXZ>If this option is not DISABLED, then the system will put the value entered in this setting into the comments field when a new lead is inserted. Special options include CALLERID_NAME which will use the CallerID Name as supplied in the incoming phone call. Default is CALLERID_NAME.</QXZ> |
| screen_labels | Screen labels give you the option of setting different labels for the default agent screen fields on a per campaign basis. | <B><QXZ>Screen labels give you the option of setting different labels for the default agent screen fields on a per campaign basis.</QXZ></B> |
| screen_labels-label_id | Screen Label ID | <QXZ>This field needs to be at least 2 characters in length and no more than 20 characters in length, no spaces or special characters. This is the ID that will be used to identify the screen label throughout the system.</QXZ> |
| screen_labels-label_name | Screen Label Name | <QXZ>This is the descriptive name of the screen label entry.</QXZ> |
| screen_labels-user_group | Admin User Group | <QXZ>This is the administrative user group for this record, this allows admin viewing of this record restricted by user group. Default is --ALL-- which allows any admin user to view this record.</QXZ> |
| screen_labels-label_hide_field_logs | Hide Label in Call Logs | <QXZ>If a label is set to ---HIDE--- then the agent call logs, if enabled on the campaign, will still show the field and data unless this option is set to Y. Default is N.</QXZ> |
| screen_labels-default_field_labels | Default Field Labels | <QXZ>These fields allow you to set the name as it will appear in the agent interface as well as the administrative modify lead page. Default is empty which will use the hard-coded defaults in the agent interface. For the first 19 fields, which are form entry fields, you can also set a label to ---HIDE--- to hide both the label and the field. Another option for most fields is ---READONLY--- which will display but not allow an agent to modify the field. One more option for most fields is ---REQUIRED--- which will force an agent to populate that field on all calls before being able to hang up and disposition each call. For the REQUIRED option to work, the campaign must have Allow Required Fields enabled.</QXZ> |
| screen_labels-active | Active | <QXZ>Set whether the screen label is active or not.</QXZ> |
| screen_colors | Screen colors give you the option of setting a different color scheme and logo for the web interface in the System Settings. | <B><QXZ>Screen colors give you the option of setting a different color scheme and logo for the web interface in the System Settings.</QXZ></B> |
| screen_colors-colors_id | Screen Colors ID | <QXZ>This field needs to be at least 2 characters in length and no more than 20 characters in length, no spaces or special characters. This is the ID that will be used to identify the screen colors in the system.</QXZ> |
| screen_colors-colors_name | Screen Colors Name | <QXZ>This is the descriptive name of the screen colors entry.</QXZ> |
| screen_colors-user_group | Admin User Group | <QXZ>This is the administrative user group for this record, this allows admin viewing of this record restricted by user group. Default is --ALL-- which allows any admin user to view this record.</QXZ> |
| screen_colors-menu_background | Menu Background | <QXZ>This is where you set the hex color value for the sidebar menu background. It must be a darker color since white text will be displayed on top of it. Default is 015B91.</QXZ> |