This Genesys Workspace Desktop Edition extension adds value to call center agents using selected Jabra headsets.
This extension supports:
- Genesys Workspace Desktop Edition version 8.5
- The following Jabra headsets: Jabra BIZ 2300, Jabra LINK 260, Jabra LINK 265 or Jabra BIZ 2400 II CC
When an Interaction window is shown – a new tab named Headset is shown. When selecting this tab the name and firmware version of a connected Jabra headset is shown. When the Interaction goes into a state where it is possible to mark is as Done – it can be done from the headset controller box.
It is possible to implement another use use. Developer skills are required. This is done by change the implementation and rebuild the software solution. Genesys Workspace Desktop developer information can be found in the Developer’s Guide and API Reference found here: https://docs.genesys.com/Documentation/IW
- Fork this GitHub repo
- Modify this C# file. Look at the method CloseInteractionIfPossible(), and implement your custom use case like this
- Read the note and rebuild the solution
- Copy the output files to C:\Program Files (x86)\GCTI\Workspace Desktop Edition to test and debug your custom use case implementation
Before deploying the extension to an organization, you can test this extension from a PC with Genesys Workspace Desktop Edition version 8.5 installed:
- Close the Genesys Workspace Desktop Edition software
- Unzip the zip file and copy the content to C:\Program Files (x86)\GCTI\Workspace Desktop Edition
- Start the Genesys Workspace Desktop Edition software
To remove the extension, close the Genesys Workspace Desktop Edition software and remove the files copied from the zip file.
Genesys recommend using the ClickOnce technology for deploying Genesys Workspace Desktop Edition to an organization. Unzip the zip file and copy the content to C:\Program Files (x86)\GCTI\Workspace Desktop Edition to prepare and publish a new ClickOnce revision as documented here: https://docs.genesys.com/Documentation/IW/latest/Dep/DeploymentProcedures
Use the the dedicated Windows installer (.MSI file) from a release. This installer supports mass deployment scenarios.