blinkyDings is available in the Genesys AppFoundry. Click on Free Trial, select the desired offer, confirm with Next, accept the terms of use, click Activate, and follow the instructions on the page after activation. Note: An installation guide is currently not publicly available on the website.

Follow the steps in the installation guide. Note: This is currently not publicly available online.

Yes, please contact us at software@deliberate.de. However, we strongly recommend the WebInstaller, as blinkyDings consists of multiple components that would otherwise need to be installed manually.

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

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

Agents require: analytics:queueObservation:view; analytics:conversationAggregate:view; analytics:conversationDetail:view; analytics:userObservation:view; architect:datatable:view; architect:datatableRow:view; routing:queue:view; routing:queue:join; routing:queueMember:manage; integrations:integration:view; integration:blinkyDingsApps:Agent. Administrators additionally require: architect:datatable:edit; architect:datatableRow:add; architect:datatable:add; integration:blinkyDingsApps:View.

No. Administrators only need the blinkyDingsApps permission. Access to the AppWizard page does not count as a license.

Yes, blinkyDings generally has no access to customer data or conversation content.

The application only receives limited status information about the agent, such as:
• Routing status
• Call status
• Presence (e.g., "available" or "on a call")

No, blinkyDings does not know
• who is calling
• who is being spoken to
• what is being discussed in the conversation

In addition, blinkyDings runs locally on the agent's PC. The processed information is not transmitted, stored, or shared with external systems or third parties.

Windows 7, 8, 10, and 11.

All Chromium-based browsers, e.g., Google Chrome (recommended) or Microsoft Edge. Note: The automatic installation of the dingsConnector extension only works with Google Chrome. Other browsers require manual installation.

Yes. However, blinkyDings must be installed on the virtual desktop – not on the host system. The browser used for Genesys must also run on the same system. Note that the hardware extension (Kuando Busylight) is not supported in virtual desktop environments.

Yes, blinkyDings can be used in Citrix environments.

No. blinkyDings works without a Busylight and displays status information directly on screen.

Make sure blinkyDings was installed via the AppFoundry, you have the required permissions, and you are logged into the correct Genesys organization. For local licenses: Close blinkyDings, open %appdata%/Deliberate/blinkyDings, edit the cfg.json file and enter your license code ("LicenseCode": "YOURLICENSECODE"), then restart blinkyDings.

Open your browser and log in to Genesys.

Open %appdata%/Deliberate/blinkyDings, rename the cfg.json file (e.g., to cfg_old.json), and restart blinkyDings.

Wait about one minute. If the error persists: Click on Logout – Genesys Cloud and refresh the Genesys page (F5). If the problem continues: Close blinkyDings via the system tray (menu item Exit, don't just close the window).

Contact your IT department or administrator. A new version of blinkyDings is available.

You can find the current prices in the Pricing tab on the AppFoundry page for blinkyDings.

Yes. A one-month trial period starts with the activation of blinkyDings in the Genesys AppFoundry.

Currently only English is supported.

Each user with the permission integration:blinkyDingsApps:Agent counts as a used license.

Currently the Alpha and Omega models from kuando Busylights are supported.

Yes, blinkyDings also works with the Salesforce client, for example.

No. blinkyDings is exclusively compatible with Genesys Cloud CX.

Yes, via kuando Busylights with sound function. Sound output via PC speakers is currently not supported.

Login is handled automatically via the Genesys login in the browser after blinkyDings has been started. If you clicked Logout – Genesys, refresh the Genesys page in your browser and wait a few seconds.

The extension is needed for authentication. It reads the user token from the browser to identify which user is currently logged into Genesys. The dingsConnector consists of two components: browser extension and locally installed application. Both are required for blinkyDings to function properly. When installing via the WebInstaller with Google Chrome, all components are installed automatically.

Use the built-in problem reporting function: Click Report Problem in blinkyDings, describe the issue, and click Generate Email. Outlook opens with the required log files. If Outlook is not available, please send an email to software@deliberate.de and manually attach the log files from %localappdata%/Deliberate/blinkyDings.

Yes, absolutely. Use the Report Problem → Suggest Feature function in blinkyDings or send us an email at software@deliberate. We welcome your feedback!

Alerts appear as a small banner that can be docked at the top or bottom of the main window. Optionally, a USB warning light can also be used.