You can find settings by navigating to This guide will give an overview of the different functions of the System Settings page. Please note that only users with Privilege level 'Owner' in DaFeeder are able to navigate to this page.
Note | ||
---|---|---|
| ||
It is important to note that changes made on this page will affect the way DaFeeder behaves/functions. |
System Settings page can be found by selecting System >> Settings.
Within the System setting, you will fin there are different tabs that perform specific task and we each will be explain each one below.
Core
The Core setting is necessary to connect the DaFeeder instance with your Organization an organization's telephone system. This These setting are managed and updated by the support team.
- Extension Prefix: This 4 four digit number is associated with your Organization to the specific Organization's telephone system. DaFeeder will use the extension prefix, along with the User's unique extension to connect the call to the Agent's device (e.g. Agent A > 0000*300, Agent B > 0000*301, Agent C > 0000*302, etc). Having set the Extension Prefix is how calls get passed through DaFeeder to the representative's calling device.
- App Key: is a code passed in through 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 It 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 has already been dispositioned as with the action of public callback, such as leads with disposition like but not limited to; voicemail, no answer, etc.
...
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