Five9 Is Retiring the Softphone for macOS: How to Move Your Mac Agents to WebRTC Before March 31, 2027

If any of your contact center agents work on a Mac, you have a deadline. Five9 has announced End of Life for the Five9 Softphone for macOS, effective March 31, 2027. After that date, Mac-based agents will need to log in using the browser-based Five9 WebRTC station.

The switch itself is simple. Getting your network, browsers, devices and people ready for it takes planning.

What's Changing?

  • End of Support: no further feature development or bug fixes, and no new macOS Softphone deployments.
  • End of Life, March 31, 2027: the macOS Softphone is no longer a supported Five9 client. Mac agents must select the WebRTC station at login.
  • Not affected: agents using the Five9 Softphone on Windows.

Why Is It Happening Now?

The trigger is Apple. The current macOS Softphone is an Intel application that runs on Apple Silicon Macs through Rosetta 2. Apple is ending general Rosetta 2 support in macOS 28, expected in Q3 2027, and once that update reaches agents' machines the Softphone won't run.

What WebRTC Changes for Your Team

  • No client software to package, deploy or test on agent machines
  • No reinstall and regression testing after every macOS update
  • Native Apple Silicon support, with no Rosetta 2 dependency
  • Faster onboarding: a supported browser, a headset and a login

The catch: browser-based voice depends heavily on your network and your browser standards.

Five Questions to Answer Before You Migrate

  1. Does your network allow WebRTC media? Firewalls, proxies and VPNs that block or reroute it cause one-way audio and dropped calls.
  2. Is one supported browser locked down across the fleet? Mixed versions and uncontrolled auto-updates break sessions mid-shift.
  3. Has every headset model been tested in-browser? Include mute, volume and call-control buttons.
  4. Have remote and VDI agents been tested separately? Home networks and virtual desktops each behave differently.
  5. Do you have a pilot group? Without one, your live queue becomes the test environment.

Not sure where you stand? Book a Five9 WebRTC Readiness Check →

A 90-Day Migration Plan

For most contact centers, a structured migration takes 8–12 weeks, so planning should start no later than January.

  • Weeks 1–2, Assess: inventory Mac agents, browsers, headsets and remote setups; audit network rules.
  • Weeks 3–4, Remediate: open required ports, standardize browsers, update device policies.
  • Weeks 5–6, Configure and pilot: enable WebRTC, confirm licensing with your Five9 TAM, move a pilot team.
  • Weeks 7–10, Roll out: migrate by team or site, with training and a support path.
  • Weeks 11–12, Decommission: remove the old Softphone and update documentation.

How Condado Helps

Your Five9 Technical Account Manager handles WebRTC licensing and commercial terms. The readiness, configuration, testing and rollout work usually lands on IT and contact center operations.

  • Readiness Check: we review your network, browsers, devices and remote setup with you and recommend where to focus.
  • Migration: we configure the WebRTC station, run the pilot and roll out by team.
  • CCaaS Managed Services: we keep your Five9 environment tuned, so the next platform change isn't your fire drill.

Book a Five9 WebRTC Readiness Check →

Explore Our CCaaS Managed Services →

Move Your Mac Agents on Your Schedule
Start with a 30-minute conversation with our Five9 experts.
Previous Post
Customer service representative wearing a headset while handling customer calls at her workstation.
November 3, 2026
AI Receptionist vs. Contact Center: What Home Services Need

Compares AI receptionists and contact center platforms to help home services companies choose the right solution for growth.

Read full Article
Next Post
Business professional reviewing financial data on computer screens in a modern office.
November 9, 2026
Contact Center Resilience: Lessons From Microsoft 365 Outage

The Microsoft 365 outage highlights contact center vulnerabilities and the importance of tested failover and disaster recovery plans.

Read full Article