Unified communications (UC) is the practice of bringing an organization’s real-time and near-real-time communication tools together so they work as one: phone calls, video and audio meetings, team messaging, voicemail and presence (showing whether someone is available). Instead of separate systems with separate logins and directories, users move between a chat, a call and a meeting from one interface, and administrators manage them in one place. UC describes the capability set, not how it is delivered; it can run on systems you own or be bought as a cloud service.
At a glance
- UC combines calling, meetings, messaging, voicemail and presence so they share users, directories and a common interface.
- It can be delivered on premises, in your own cloud environment, as a cloud service (UCaaS), or as a mix.
- Calling within a UC platform still needs a connection to the public phone network to reach outside numbers.
- Integration depth varies by vendor: some build everything on one platform, others connect separate products.
- Network quality, emergency calling and licensing tend to decide whether a UC rollout succeeds.
What problem it solves
Many organizations grew their communications tools one at a time: a PBX for calls, a conferencing service for meetings, a chat app chosen by one team, and voicemail on yet another system. Each has its own directory, admin console, contract and support path. Users juggle several apps and can’t easily tell whether a colleague is free, and IT pays for overlapping features.
UC brings these into one experience. A user can see that a colleague is available, start a chat, escalate to a call, add video and share a screen without switching tools. Administrators manage users, numbers and policies in fewer places, and the business can reduce the number of vendors it pays.
How it works
Core capabilities. A UC platform typically includes:
- Calling. Extensions, direct numbers, transfers and call handling, usually delivered with Voice over IP.
- Meetings. Audio and video conferencing with screen sharing.
- Messaging. One-to-one and group chat, often with file sharing.
- Voicemail. Often with transcription or delivery to email, building on ideas from unified messaging.
- Presence. Status that shows who is available, busy or in a meeting.
Delivery models. UC can be built around an on-premises PBX with added meeting and messaging servers, run in your own data center or cloud tenant, or bought as Unified Communications as a Service (UCaaS) where the provider runs the platform. Some organizations combine models, for example keeping a phone system on site while using a cloud meeting and chat service.
Clients. Users reach UC through desktop and mobile apps, softphones, browsers, IP desk phones and meeting room systems.
Phone network connection. To call ordinary numbers, the platform connects to the public phone network through the vendor’s own calling service, a carrier’s SIP trunks, or a hybrid.
Integrations. Many UC platforms connect with calendars, CRM, help desk and contact center software, though the depth and cost of these integrations vary.
When it matters for buyers
- When an on-premises phone system reaches end of support and you are deciding what replaces it.
- When meeting, chat and phone contracts renew at different times, which is a chance to consolidate.
- When the workforce is hybrid and people need the same tools at home, in the office and on mobile.
- After a merger, when two organizations bring different communication stacks.
- When users have already adopted a meetings-and-chat tool and the question is whether to add calling to it.
Questions to ask vendors
- Which capabilities are built on one platform, and which are separate products connected by integration?
- How do you connect to the public phone network, and can we bring our own carrier?
- What licensing tiers include calling, meetings, recording and admin features, and what costs extra?
- How do you handle 911 calling and location for office, remote and mobile users?
- What network requirements do you have for voice and video quality, and how do you report on call quality?
- Which integrations (calendar, CRM, contact center) are included, and which need extra licenses or partners?
- What does migration look like, and can our current phone system stay connected during the transition?
How it differs from UCaaS
UC is the capability: integrated calling, meetings, messaging and presence. UCaaS is a delivery model for that capability, where a provider runs the platform in its cloud and charges a recurring fee, usually per user. An organization can have UC without UCaaS by running the systems itself, and many products sold as UCaaS emphasize some UC capabilities more than others. Collaboration tools overlap with UC but extend into document editing, project tracking and whiteboards.
For guidance on comparing cloud-delivered options, see our Unified Communications as a Service solution page.