PBX & unified communications

Genesys Cloud PBX and unified communications capabilities are an intrinsic part of the platform, not an afterthought. Genesys includes unified communications in every Genesys Cloud CX licence tier, so the same service that runs your skills-based contact centre can also provide telephony, collaboration and presence for the rest of the business. That matters because most customer problems are solved by people outside the contact centre: the specialist in finance, the engineer in operations, the manager who can approve an exception. When agents can find those people, see whether they are available and reach them in a click, first-contact resolution improves and customers stop being passed around.

There are two broad ways to achieve this. Genesys Cloud CX can be your PBX and UC platform, replacing a legacy on-premises PBX for front office and back office alike. Or it can integrate with a UC platform you already depend on, such as Microsoft Teams, Zoom Phone or 8x8, so each community keeps the tools it knows while presence, directory and calling work across the boundary. Many organisations combine the two during a transition. Choosing well depends on your users, licences, carriers, number ranges and roadmap, and it is the first design decision we help you make.

The PBX functionality in Genesys Cloud CX is powerful and often underestimated. Users can have extensions and direct inward dial numbers, and group phone numbers ring members using broadcast, sequential or rotary distribution, with overflow to a backup group and group voicemail with transcription. Architect flows provide auto-attendants and business-hours routing for any number, so a back-office department can have the same professional call handling as the contact centre. Calls can be answered on the WebRTC phone in the browser or desktop app, on managed SIP desk phones, or on a remote number, and outside lines are shared rather than provisioned for every phone.

Telephony connectivity is open. Genesys Cloud Voice lets Genesys provide the phone service; BYOC Cloud connects SIP trunks from your preferred carrier to Genesys Cloud media in AWS; and BYOC Premises keeps media on your own Edge infrastructure where regulation or connectivity demands it. A shared trunk can carry geographic, non-geographic and toll-free numbers for the contact centre and the back office, while you keep your own extension numbering scheme. If you still run the BYOC Premises Genesys Hardware Solution, note that it is already past end of support and reaches end of life on 1 June 2027, after which it stops working. Genesys recommends moving to cloud media or customer-supplied premises hardware.

Genesys Cloud CX is also a full unified communications platform. Collaborate chat provides one-to-one and group conversations with persistent history, file and image sharing and search, and a one-to-one chat can become a call in a click. Video chat supports conferences of up to 12 participants with screen sharing, without leaving the application. Every user has a profile and presence, so colleagues can search the directory by name, skill, department or location, see real-time availability and hierarchy, and choose the right way to make contact. Voicemail, faxes and recordings arrive in one inbox. Users work in the browser, the desktop app or mobile apps.

Our approach to unified communications focuses on three areas. First, eliminating the silos that exist between teams, departments, business functions and the contact centre, through a directory, presence model and group structure that reflect how your organisation really works. Second, working methods: configuring the web, desktop and mobile capabilities so employees can do their best work from any location, with the right audio profiles, phones and headsets. Third, technology and integrations: deciding where Genesys Cloud CX is the UC platform, where it integrates with another, and how legacy PBX estates are bridged or retired along the way.

Genesys documents unified communication tools integrations for 8x8, Microsoft Teams and Zoom Phone, each available from AppFoundry and configured on both platforms. Depending on the integration and its configuration, capabilities include viewing the UC directory from Genesys Cloud, searching contacts, presence synchronisation, click-to-call and calling between the two platforms, so an agent can find a back-office expert in Teams and consult or transfer to them. Genesys Cloud for Microsoft Teams can also embed the Genesys Cloud client inside Teams. Each integration requires a licence for the UC platform and has separate pricing, which belongs in your business case from the start.

The details decide whether the experience works. Only one PBX phone integration can be enabled per user, so user types and personas must be defined carefully. Presence mappings determine whether an agent on a Teams call is offered contact centre work. The path a consultation call takes – over direct SIP connectivity such as a Teams trunk or across the public network – affects quality, cost and resilience. Directory scope, identity and single sign-on, recording obligations and emergency calling all need decisions. We document these in the high-level design, so your UC, telecoms and contact centre owners agree before configuration begins.

Telephony and collaboration touch every employee, so we treat them as a whole-business programme. We muster a multidisciplinary squad from our own bench: a Solution Architect who owns the communications design, an IT Systems, Telecoms & SIP Engineer for carriers, trunks, number ranges and networks, a Senior Business Consultant / Business Analyst who maps how departments communicate today, testers for systems integration and user acceptance, a Trainer for front and back office users, and Support Engineers who will run the service afterwards. Even where you see only one or two of us, the whole practice stands behind the design, and we take collective responsibility for the outcome.

For a communications programme the method leans heavily on telephony. Discovery audits the existing PBX, number ranges, extension plan, hunt groups, auto-attendants, carriers and sites, and assesses network readiness. The high-level design sets the platform and integration model; the low-level design or build book records every number, group, flow, site, trunk and presence mapping. Telephony testing proves carriers, numbers, inbound and outbound calling, group ring behaviour and failover, and systems integration testing proves the UC integration end to end. Transition brings a number porting plan, cut-over runbook and rollback plan, role-based training and hypercare, followed by SLA-based support.

We work transparently with your IT and telecoms functions and your carriers, because a communications design that ignores them tends to reinforce silos instead of breaking them down. Most PBX replacements run in waves, so for a period the legacy PBX and Genesys Cloud CX live side by side. We design that interim state explicitly: which number ranges and departments move in each wave, how calls and transfers pass between the two platforms, how extension dialling keeps working across the boundary, and how each wave can be rolled back until it is accepted. Emergency calling, call recording obligations and the retirement of old hunt groups, voicemail boxes and carrier circuits are planned as named tasks in the cut-over runbook, so nothing is left running, or switched off, by accident.