You can find settings by navigating to System >> Settings.

Within the System setting, you will fin different tabs that perform specific task and we will explain each one below.

Core

The Core setting is necessary to connect the DaFeeder instance with your Organization telephone system. This setting are managed and updated by the support team

• Extension Prefix: This 4 digit number is associated with your Organization telephone system. DaFeeder will use the extension prefix along with the User extension to connect the call to the Agent device (e.g. Agent A > 0000*300, Agent B > 0000*301, Agent C > 0000*302, etc)
• App Key: is a code passed in to identify the user to the API. This is used for security reasons
• App Secret: This is used to encode and decode the App Key. Is another layer of security for the API
• Prioritize Open Leads before public Callbacks: This is to enable or disable the user to receive untouched or uncalled leads before any other leads that have been dispositioned as public callback, such as leads with disposition voicemail, no answer, etc.

SMTP

Here is where you enter your Simple Mail Transfer Protocol (SMTP) information. This setting is to connect DaFeeder with your email hosting provider

• Host: enter your SMTP host service provider
• Port: The default and standard port number is 465
• Username: If applicable, enter the username to login your SMTP
• Pass: If applicable, enter the password to login your SMTP
• Encryption: We always want to use encryption, the default its option SSL

Feeding

This setting can be updated by the Support team only.

The Lead Timeout will show you how long an agent can have a lead open until it timeout. When the lead timeout, it will promt the user to the Feed page

The Dialing Number Threshold would not let you call a number twice between a specific amount of seconds, so the amount of seconds in this section stand for the time limit between the calls for a specific number

Engine

If you are experiencing problem with the feeding page but everything else works fine, this probably mean the engine has failed. To solve this, you need to click on Restart Engine

This should only be use when you are experiencing problems or slowness with the feeding page (loading a lead, dispositioning a lead or direct viewing a lead).

Restarting the engine makes sure that the feeding page work properly again, it also interrupts all leads being viewed, and they become undispositionable. Therefor, after an engine restart all users must refresh the feeding page