Building the Next Chapter: The Strategy Behind v8.1

If a partner reads nothing else about this release, what’s the one thing they need to understand?

That this release isn’t five unrelated features that happened to ship at the same time. It is an answer to three questions we kept hearing from partners:

• How do we build more on top of PBXware instead of just deploying it?
• How do we get ahead of regulation instead of scrambling to catch up with it?
• How do we bring AI into daily use without a heavy lift?

If you had to pick one feature that matters most to a partner’s bottom line in this release, which is it?

It depends on the partner.

For a partner running their own trunks and origination, it’s the compliance pair, DNO and ECBN, because the FCC’s expanded Do-Not-Originate rule has already taken effect. That’s not a future risk. It’s a current one with real financial penalties attached.

For a partner with technical customers who have been asking for custom integrations, it’s the Developer Portal, because that unmet demand is sitting right there today.

If I had to force a single answer, I’d say the Developer Portal because it’s the one that compounds. Every integration a customer builds is another reason they don’t leave, and that value keeps growing long after the release date.

The Developer Portal is a bet that partners actually want to build rather than just deploy and support. What convinced you that bet is right?

The bet isn’t really that partners want to become software companies. It’s that they want to solve customer problems and grow their business.

We serve hundreds of different use cases across countless industries, and it’s impossible to build everything for everyone.

The way we see it, our job is to provide a strong platform and the tools to extend it. Our partners know the needs of their customers much better than we ever could.

By enabling partners to build on top of our platform, we help them create differentiated solutions that win more business. That’s how a platform scales.

What should a partner’s first 30 days with v8.1 actually look like?

Compliance comes first because it’s the one with a clock attached.

• Turn on DNO under Settings > DNO > Configuration.
• Confirm that the 30% Somos discount is applied if they choose it.
• Size an ECBN pool against the number of extensions without DIDs in each deployment.

That’s a week of work, not a project.

After that, get one technical person exploring the Developer Portal against a real customer request that’s already on the table. Use an actual customer need to prove the “minutes to first API call” claim.

MCP doesn’t need a 30-day plan. It’s already there the moment a customer is on gloCOM 8.1.

The SMS DID feature is worth a five-minute mention to any customer already juggling multiple business lines on one extension. It’s a fast, tangible win with almost no setup cost.