She Had One Quarter to Move Every Customer Off a Dying Client
MetaSwitch killed the MaxUC client, and every one of Sofia's sixty customers became a free agent on the same day.
Her whole base moved to a softphone with her name on it, and not one account walked.
Sofia runs a VoIP reseller. She resells hosted voice to maybe sixty small and mid-market businesses: law firms, clinics, a couple of logistics dispatch floors.
For years the softphone her customers used was MetaSwitch's MaxUC client. It came with the platform, it was fine, nobody thought about it.
Then MetaSwitch announced MaxUC was going end-of-life. Every one of Sofia's customers became a free agent on the same day.
We sat down with her to hear how that quarter went.
What did you do first?
I did the math on how many accounts I had sitting on MaxUC, and I did not like the number. Sixty-some customers, all told they had a deadline, all capable of calling literally anyone else in the meantime.
My first instinct was to ask my platform vendor what their replacement client was and start pushing that out. That felt like the safe move. Stay inside the family.
What was the breaking point?
The breaking point was realizing that "the safe move" was not safe at all. If I took the vendor's replacement client, I was just trading one dependency for another. Same problem, five years later, on someone else's schedule.
And in the meantime, my customers were getting emails. Not from me, from other resellers, all saying some version of "your softphone is dying, come to us instead." One of my larger accounts, a clinic group with four locations, told me straight: "We got a call from someone else about this before we heard from you."
That is the moment it stopped being abstract. I could lose accounts I had held for a decade to whoever sent the better email first.
How did that feel? And commercially?
Honestly, it felt like I did not own my own customer relationships. My brand was never really on the product. MetaSwitch's was, in the app itself, in the client the customer opened every day. So when MaxUC died, my customers' loyalty was never fully mine to lose or keep. It was the platform's.
Commercially it was worse. I was staring down a quarter where I might have to spend real money on migration support, re-provisioning, retraining, and still come out the other side having lost accounts, or having them associate the whole mess with me even though MetaSwitch made the call.
There was no version of standing still that ended well.
MaxUC went end-of-life
sixty-some customers off a dying client on the same day, all free to leave, all getting poaching emails
The 'safe' vendor client was a trap
taking the platform's replacement just traded one dependency for another, same problem in five years
Moved the base to a branded Cloud Softphone
reliability became the floor; White-label branding put her name on the app, not the platform's
Whole base migrated inside one quarter
not a single account lost to someone else's migration email
What changed?
I stopped treating this as a platform migration and started treating it as a branding decision. I moved my customer base onto a Cloud Softphone build that carries my brand, not my underlying platform's.
And the thing that actually made this survivable was that the softphone stopped being something I had to babysit. It just worked, the same way a faucet just works. You turn it, water comes out, you do not think about the pipes.
Once the app itself was reliable and out of my hands operationally, the migration stopped being a five-alarm fire and became a project with a checklist.
That reliability is not a nice-to-have. It is the floor everything else stands on. Without it, none of what I built next would have mattered.
How they used Acrobits
The self-service billing and usage portal went into a Web Tab. For larger accounts like the clinic group, who spend a lot of time on billing questions and usage disputes, Sofia built a portal and dropped it into the app as a web tab, a window inside the softphone that shows any web page. She wired it with single sign-on, so the customer opens the app already logged into their own account: no separate password, no second app. They see their own usage and billing history without calling support. That cut a meaningful chunk of routine billing calls immediately.
Ticketing wired through the IPC SDK puts a badge on the call screen. For accounts running dispatch or support desks, where every inbound call is potentially a ticket, Sofia connected the ticketing system through the IPC SDK, a bridge that lets a web tool reach into the phone's real features like notification badges. Now when a customer calls in, if they already have an open ticket, a badge shows right on the call screen before anyone answers. The agent knows the history before they say hello.
She built ahead of the request. The ticketing badge was not something a customer asked for directly. Sofia built it because she could see the shape of the request coming, the same way the billing portal came from listening to what customers kept calling about.
If you had to teach this to someone, what is the one idea?
Unified communications happens in the UI. Not in the platform, not in the switch, not in whatever back-end you are running underneath. In the screen the customer is actually looking at when they make a call.
Once I understood that, MaxUC going end-of-life stopped being a crisis about which vendor to pick next. It became a question of what I put on my customers' screens, which was always something I could control myself, with web tabs and the IPC SDK, without waiting on a platform roadmap.
What they needed
- My own brand on the app, not the platform's, so the customer relationship is mine and survives the next end-of-life
- A base that just works across every customer's phones, so reliability is the floor and the migration is a checklist, not a fire
- Customer tools inside the app on my own timeline, without waiting on a platform roadmap
- A real bridge to the phone: single sign-on and native call-screen badges, not a website bolted on
- Active-user billing so I pay only for the people who actually register and call
Technical detail
Features that did the work
White-label branding
the app carries the reseller's brand, not MetaSwitch's or Acrobits'. For bigger accounts, Open White Label gives them their own isolated branding inside the same app.
Web Tabs
any web tool, like the self-service billing and usage portal, renders as a native tab inside the softphone. Single sign-on passes the user's identity through, so it feels like one app, not a website bolted on.
IPC SDK
web content in those tabs reaches the phone's real features. The ticketing system fires a native badge on the call screen when an open ticket exists, before anyone answers.
Active-user billing
pay for the people who actually register and call in a period, not every seat ever provisioned. $0.12 per active user for own-brand-across-the-board; $0.42 per active user for Open White Label.
And the business?
I priced it two ways, depending on the account. For customers where I only needed my own brand across the board, that runs at $0.12 per active user, meaning I only pay for people who actually register and call in a given period, not every seat I ever provisioned.
For my bigger accounts, the ones that wanted their own isolated branding sitting inside the same app, that is Open White Label, at $0.42 per active user. Both numbers are small next to what an account is worth over its lifetime.
And here is the part that mattered most:
- I moved the entire base inside one quarter, before the MaxUC deadline hit.
- I did not lose a single account to someone else's migration email.
- The platform underneath can change again in five years and it will not touch my customer relationships, because those relationships now live in an app with my name on it, not the platform's.
The day you hear a client you depend on is going end-of-life, ask whose brand is on that screen.
That's whose customer it really is. Move them onto an app with your name on it, and the next platform shake-up won't touch the relationships you spent a decade building.