Built With Partners. Tested by Their Fleets.
The pilot program is a working relationship. Real MSPs run their fleets on Controvo, tell us what breaks and what's missing, and watch the answers ship. This page is the history of that loop, with the numbers behind it.
Rigor You Can Count
We recorded, transcribed, and mined every partner conversation, then verified every ask against the product. This is what more than six months of that looks like.
74
recorded partner calls
76+ hours of demos, onboardings, and touchbases
1,024
pieces of feedback captured
every call transcribed and mined so nothing relied on memory
291
distinct asks tracked
deduplicated, ranked by demand, and checked against the shipped product
100s
of Slack conversations
every partner has a direct channel to the team
How the Feedback Loop Works
Three habits, kept for the whole program.
Every partner has a channel
Hundreds of Slack conversations, straight to the people who build the product. A bug report posted at breakfast has been fixed by dinner more than once.
Every call is mined
74 recorded video calls (demos, onboardings, touchbases) transcribed and combed for every request, pain point, and promise. That produced 1,024 findings that would otherwise live in somebody's notebook.
Every ask is tracked
The 291 distinct asks live in a ranked list, each one checked against the shipped product. When a partner asks "did that ever happen?", we answer with a release-notes link.
Ideas That Became Features
A sample of partner asks that shipped, with how many separate partner calls raised each one. The release notes tag them as they land.
19 calls
Call Flow Studio
Partners asked to see call routing instead of reading it. Auto-generated visual maps with in-map editing and call tracing became the most-praised capability in the program.
12 calls
Granular staff roles
Partners wanted finer-grained roles than the native admin model offers, so custom RBAC now controls exactly what each tech can see and do.
8 calls
Offline phone tracking
Asked in 2025, shipped with a last-seen column and last-known IP with geolocation. Finding a dead handset no longer starts with a truck roll.
8 calls
Compliance enforcement policies
Partners with medical and financial clients asked for recording and voicemail rules they could prove. Policies with audit mode answer it.
5 calls
License Manager
Expiry tracking and a renewal forecast, asked for in 2025 and covered by the shipped tool. It grew partner-tier analytics nobody asked for but everyone uses.
5 calls
AI voice prompts
Text-to-speech prompt generation with inline WAV conversion, applied straight to IVRs, queues, and ring groups, without hiring a voice talent or an audio engineer.
Week one
Custom email server support
One of the first pilot asks: alerts should come from the MSP's own domain, not ours. SMTP support with a test button shipped shortly after.
Partner request
Single outbound IP
A partner's 3CX consoles were IP-restricted, so Controvo's traffic now comes from one address they can allow-list once.
Partner request
Bulk member management
A partner managing 100+ queues and ring groups described hours of per-queue clicking for every new hire. Bulk add and remove shipped the same week.
The Part Partners Talk About Most: The Speed
The loop only matters if it's fast. A pilot partner asked for a heat map on Call Flow Studio on a Monday morning; it was in their tenant the next day. Another described hours of per-queue clicking for every new hire; bulk member management shipped the same week. When 3CX's certificate provider changed its infrastructure, the fix was in partners' hands within hours of the announcement email.
The cadence is easy to check against the public release notes, where partner requests are tagged as they ship.
And Yes, They Found Bugs
That was the point. Twenty different fleets means twenty different flavors of real-world 3CX: odd trunk configurations, ancient templates, systems stuck mid-migration. Partners hit edge cases no test environment reproduces, reported them in Slack, and watched the fixes land in the weekly release notes.
Every one of those bugs died in the pilot instead of in a paying customer's fleet. To us that is the useful meaning of "rigorously tested."
In their words
From the partners who built this with us
"So far, so amazing. We are loving the tool, and the updates you are doing blow me away."
"We're definitely moving forward after the Pilot is over. No question."
"God, you guys have a winner here. For people that do what I do every day, all day — this is a dream come true."
"I compiled a list of everything I'd want, and literally ticked off every single one before we even started."
"You guys are really changing the ability of providing 3CX for those who are doing it at scale and managing the systems, as opposed to the old model of just selling licenses. Fantastic!"
"We created the template functionality right away. Since then, I use them across all of our tenants. It saves me from creating the extension and then going back in to make adjustments — if I'm doing this for 10 or more people, it just kind of gets crazy."
"I've been providing SIP/VoIP based service for business clients since 2011. I've not seen a set of tools and resources like Controvo before now."
"We look at a lot of software, and most software is not that well thought out, to be perfectly honest. This looks like it really is. I'm pretty impressed."
The Loop Is Still Open. So Is the Pilot.
Until general availability on August 1, you can still join the program that built all of this. You run free until launch, get the same hands-on onboarding, and keep the Pilot Partner Lifetime Discount permanently. Your asks go into the same tracked list.