syncDings is available in two installation variants:

• WebInstaller
• MSI installation package

Both variants are available as direct downloads.

If you use custom policies for software rollout, the MSI package is recommended, as it offers individual options for software distribution.

Follow the steps in the installation guide. The new version can be installed via our WebInstaller or our MSI.

Yes, a custom installation is possible with an MSI package.

The dingsConnector extension is needed to obtain the user token from the browser. This is required for authentication and allows syncDings to identify who is currently logged into Genesys. The dingsConnector consists of two components: the browser extension and an application on the local computer. Both components are necessary for syncDings to function.

You can find the extension in the Chrome Web Store at: https://chromewebstore.google.com/detail/dingsconnector/hdgfagobifamclbicbnopfpgmmablfnc

Agents: architect:datatable:view; architect:datatableRow:view; integration:syncDingsApps:Agent. Administrators: integrations:integration:view; architect:datatable:view; architect:datatableRow:view; architect:datatable:edit; architect:datatableRow:add; architect:datatable:add; integration:syncDingsApps:View.

No. Administrators who only need access to the AppWizard page require the permission integration:syncDingsApps:View. This access does not count as a license.

No, the price is always the same – whether standard or custom. You can create as many rule sets as needed.

Windows 10 and 11.

Yes. It must be installed on the virtual desktop – not on the host system. The browser for Genesys must also run on the same system.

Yes, syncDings can be used in Citrix environments.

All Chromium-based browsers such as Google Chrome (recommended) or Microsoft Edge. Note: The automatic installation of the dingsConnector extension only works with Chrome – other browsers require manual installation.

No, that is not possible.

Yes, that is possible.

No additional setup or permissions are required.

No, syncDings is not compatible with the desktop app. Users must be logged into Genesys Cloud via a supported browser (Edge or Chrome).

Updates are infrequent, typically about once per year. It does not require regular maintenance.

Make sure syncDings was installed via the AppFoundry, the correct permissions are in place, and you are in the right organization. For local licenses: Close syncDings, open %appdata%/Deliberate/syncDings, edit cfg.json and enter your LicenseCode, then restart syncDings.

Your Genesys reseller must enable distribution. Please contact them to gain access to syncDings.

Open your browser and log in to Genesys.

Close syncDings via the system tray, install the dingsConnector extension from the Chrome Web Store, and restart syncDings.

Run the installation again – either with the WebInstaller or manually with all required components: syncDings app, dingsConnector (local), dingsConnector (browser extension).

Go to %appdata%/Deliberate/syncDings, rename cfg.json (e.g., cfg_old.json), and restart syncDings.

Wait about 1 minute. If the error still persists: Click on Logout – Genesys Cloud, refresh the Genesys page (F5). If that didn't help: Close syncDings via the system tray (don't just close the window).

Close syncDings. Delete the uda folder in the directory %localappdata%/Deliberate/syncDings. Then restart syncDings. If syncDings still doesn't work properly, please contact software@deliberate.de with a description of the problem.

Verify that you have all the necessary permissions for the apps.

An updated version of syncDings is available. Please contact your administrator or IT department.

Simply log in with your usual Microsoft Teams credentials.

You don't need to log in to syncDings separately. Authentication is handled automatically via Genesys once syncDings is started.

Simply refresh the Genesys page in your browser and wait a few seconds.

Yes, the Genesys status should change to Busy in this case.

Yes, the Genesys status should also change to Busy in this case.

Yes, the Teams status should change to Do Not Disturb. Due to the rule, the Genesys status is also set to Busy. After the call, the Genesys status automatically switches back to On Queue.

The Teams status should change to Available. This keeps the agent generally on queue, unless they are presenting or in a Teams meeting.

No, this synchronization should not occur, as Teams does not differentiate whether the status was changed manually or due to inactivity.

No, the Teams status should not be adjusted in this case.

No, the Teams status should not be automatically set to Away.

Yes, although not directly through Genesys data tables at this time. syncDings allows rule files to be stored locally or on a network drive, which users can select via the UI. Alternatively, configuration files can be deployed with the path to the rules file preconfigured.

The Teams status should change to Available. This keeps the agent generally on queue, unless they are presenting or in a Teams meeting.

No, this synchronization should not occur, as Teams does not differentiate whether the status was changed manually or due to inactivity.

No, the Teams status should not be adjusted in this case.

No, the Teams status should not be automatically set to Away.

Yes, although not directly through Genesys data tables at this time. syncDings allows rule files to be stored locally or on a network drive, which users can select via the UI. Alternatively, configuration files can be deployed with the path to the rules file preconfigured.

In the syncDings window, you'll find a Report Problem button. The window allows you to enter an error description. When you click Generate Email, Outlook opens and automatically attaches the relevant files. If you don't use Outlook, please send an email to software@deliberate.de and attach the log files from %localappdata%/Deliberate/syncDings.

Yes, although not directly through Genesys data tables at this time. syncDings allows rule files to be stored locally or on a network drive, which users can select via the UI. Alternatively, configuration files can be deployed with the path to the rules file preconfigured.