Headsets, WebRTC & SIP phones

Customers judge a contact centre by what they hear. A crackling line, a delay that makes people talk over each other, or an agent fumbling to unmute all damage confidence before the conversation has really begun. The endpoint layer is also where agents feel friction every day: a headset that will not answer calls, a softphone that loses audio after a laptop sleeps, or a desk phone configured differently from the one next to it. Getting Genesys Cloud WebRTC phones, headsets and SIP desk phones right is therefore a direct investment in both customer experience and agent experience.

It is also where hybrid and remote working succeed or fail. When agents work from home, the contact centre inherits a huge variety of broadband connections, routers, laptops and personal habits. QVCCS helps you set clear standards for devices and networks, choose the right phone type for each user group, and roll out changes in a controlled way. We treat audio quality as a design outcome rather than a support problem, so it is planned before go-live instead of investigated after complaints begin to arrive from customers or team leaders.

Genesys Cloud CX supports four categories of phone: managed, unmanaged, remote and WebRTC. The WebRTC phone runs in the browser, the desktop app and embedded clients such as Genesys Cloud for Salesforce, Microsoft Teams and Zendesk, turning a supported computer and USB headset into a contact centre phone with no extra hardware. Managed phones, with base settings configured centrally, cover supported Polycom, AudioCodes, Genesys-branded and Spectralink devices. Genesys publishes an end-of-life position on older Poly VVX and SoundPoint models and some AudioCodes phones, and recommends WebRTC where a physical phone is not required. Choosing the mix for each user group is the first part of any endpoint design.

Headsets are the second part. Genesys Cloud gives audio support to any USB headset but built-in call control only to specific models from Poly, EPOS, Jabra, Yealink, Sennheiser and Cyber Acoustics. Each has its own requirement: Jabra and Yealink use WebHID in Chrome 89 or later, Poly needs Plantronics Hub, as Poly Lens is not supported, and EPOS needs EPOS Connect. Headsets must connect by USB cable or the vendor's dongle, because Bluetooth through a laptop's internal adapter does not support call controls. Audio profiles, stored in the cloud against each user, select input, output and notification devices. Our engineers check every model you use against current vendor compatibility lists.

Real-time voice is sensitive to packet loss, jitter and latency in ways that email and web browsing are not. A home connection that streams video happily can still produce choppy calls when the family is online at the same time. QVCCS carries out network readiness assessments for offices and representative home workers, reviewing bandwidth, Wi-Fi versus wired connections, VPN routing, firewalls and proxies against the Genesys ports and services diagrams for WebRTC, which differ by Genesys Cloud Voice or BYOC and by NAT type. We advise which traffic should bypass a VPN and what minimum standards home workers should meet before taking customer calls.

Device and client settings matter too. Laptop power management, browser permissions, operating system audio devices and conflicting communications software can all disrupt a WebRTC phone. In Chrome, advanced microphone settings let users clear automatic mic gain, echo cancellation or noise suppression where the defaults do not suit their environment, and in Genesys Cloud for Salesforce, Jabra and Yealink buttons need the WebRTC phone popped into its own window. Genesys also does not recommend running several embedded client variants at once. We document recommended settings, teach agents to run the WebRTC Diagnostics app, and give your service desk a clear path for diagnosing poor audio.

Endpoint quality depends on networks, desktops, telephony and people together, so the team from our own bench covers each. An IT Systems, Telecoms & SIP Engineer leads a remote network readiness survey of offices and representative home workers, and configures WebRTC trunks, sites and managed phones; a Solution Architect sets device standards and the endpoint design; a Trainer prepares agent guides; a Support Engineer builds the service desk runbooks. Testing is device by device: our Systems Integration Tester makes inbound and outbound calls, transfers and consults, and uses mute, hold and reject from each headset model and phone type, in the office and from home, then tries the known failure cases – a Bluetooth headset paired through the laptop, a blocked port, a VPN in the media path and a laptop waking from sleep.

Device choice deserves more thought than it usually gets. A short, standard list of headset models is far easier to support than whatever each team happened to buy, and makes firmware updates predictable. Noise-cancelling microphones matter in open-plan offices and busy homes; some agents prefer a binaural headset for concentration, others need one ear free. Home workers need a simple swap process, because a faulty headset should not cost a shift. Agents with hearing aids or other access needs may need adapted devices, agreed with them rather than assumed. Laptop builds and browser updates are usually controlled by IT, so we agree a test step before new builds reach contact centre users. Rollout then runs in waves, starting with a pilot group whose feedback shapes the rest.

Endpoints are never static. Headset firmware updates, new laptop builds, browser releases, office moves and new home workers all affect call quality and call control. QVCCS provides second- and third-line help with audio issues, behind your provider's or service desk's first line, or within SLA-based support where you contract it with us, and reviews platform and vendor releases for impact on your standard builds. We keep your device standards and network guidance current, and can monitor trends in call quality so recurring problems are tackled at the root rather than one ticket at a time.

As you grow, our team helps you onboard new sites, new agent populations and new device models without losing consistency. We can refresh standards when you change headset supplier, introduce desk phones for a new department or move more agents to home working. Because QVCCS engineers work only on Genesys Cloud CX and hold, or are completing, its certifications, the advice you receive is specific to the platform rather than generic voice guidance. That focus keeps your customers hearing clear, confident agents, wherever and however they work, and keeps the endpoint estate supportable as it changes.