We rolled out Jabra Evolve2 85 headsets to 200 agents, and approximately 30% report that the headset hook button (answer/hangup) does not work in Genesys Cloud.
Before deploying, we tested with 5 agents and it worked perfectly. The agents are frustrated and losing trust in the new equipment. How do we communicate this issue without causing a mass revolt?
The hook event relies on the WebHID API in Chrome, which requires explicit user permission.
When the agent first connects the Jabra headset, Chrome displays a small permission prompt asking to allow the site to connect to the HID device. If the agent dismisses that prompt (which 30% of users will do instinctively), the hook events are silently disabled.
The fix is to have agents go to chrome://settings/content/hid and manually grant permission to the Genesys Cloud domain.
At scale, this WebHID permission issue creates a measurable performance impact.
We tracked the average answer speed across our 500-agent test group. Agents with working hook buttons answered 1.8 seconds faster than agents who had to click the on-screen answer button. At 500 agents × 80 calls/day × 1.8 seconds, that’s 20 lost agent-hours per day.