This guide will provide 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.
...
The Core setting is necessary to connect the DaFeeder instance with an organization's MeloTel telephone system. This configuration will authenticate DaFeeder to manage agents calling, reports and actions.These setting are managed and updated by the support team.
- Extension Prefix: This four digit number is associated 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).
- App Key: is a code passed 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. 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 has already been dispositioned with the action of public callback, such as leads with disposition like but not limited to; voicemail, no answer, etc.
...
Restarting the engine should only be performed if multiple users are experiencing an issue with the feeding page.
Restarting the engine ensures that the feeding page will perform as expected again. Consequently restarting the engine will also interrupts all leads being viewed, and they become undispositionable. After an engine restart all users must refresh the feeding page.
In cases where able to, it is recommended to provide notice to all representatives working in DaFeeder, as after performing an engine restart services will be interrupted and work/leads will be lost.
