Summary

  • A Salesforce administrator creating a managed voice trunk can select a carrier, choose a media region and then complete a number association in Bandwidth. That documented hand-off is a useful picture of what “native” does—and does not—mean.
  • Bandwidth announced on 15 September that it was Salesforce’s first certified carrier for a global Contact Center rollout. Its product page, checked on 30 September, says 25-plus-country coverage is coming in October 2026. That is a roadmap, not evidence of a live global customer base.
  • The buyer may get a more consistent agent workflow without surrendering every carrier decision to Salesforce. Number ownership, porting, outbound caller attestation and parts of emergency-service setup still sit at the provider boundary.

The tell is not the AI agent on a Salesforce screen. It is the step after the administrator has created the voice connection: the Salesforce guide says that, in its managed-trunk workflow, the carrier defaults to Bandwidth; the administrator chooses a Salesforce media region and submits an organisation ID; then the administrator signs into Bandwidth and associates that ID with a phone number. The screen is unified. The account and the number are not necessarily in the same system.

That distinction is becoming commercially important as customer-service software absorbs more call handling. Salesforce’s pitch is that an agent can see CRM context, voice and AI inside one service environment. A carrier’s pitch is different: it can connect that environment to the public telephone network, supply or port numbers, route calls and manage country-specific telephony tasks. The partnership is valuable precisely because those jobs are related but not identical.

The September announcement marked an expansion of an existing collaboration. Bandwidth called itself the first certified carrier supporting the global rollout of Salesforce’s native Contact Center and said the offer would extend to more than 25 countries across Europe, the United Kingdom, Australia and New Zealand “this fall.” The current Bandwidth integration page gives a narrower date: coverage in 25-plus countries is “coming in October 2026.” On 30 September, the published language is still future-tense. Neither source names a live customer, reports calls already handled in those markets or publishes a country-by-country number and service matrix.

The two country counts in the announcement should not be collapsed. Bandwidth’s company description says its broader Communications Cloud reaches about 70 countries and 90% of global GDP. The Salesforce product page says 25-plus countries are coming in October. A network footprint is not an integration footprint; a country in a corporate coverage statement is not proof that a particular Salesforce customer can order the phone number, outbound service and emergency calling it needs there.

Salesforce’s own product documents show why the boundary exists. A June 22 customer FAQ described native telephony as Salesforce directly owning the voice media stream and selling minutes and numbers. At that time, direct telephony was available in the United States and Canada; Salesforce said its voice-resale licensing was limited to those markets. A later international route through Bring Your Own Carrier (BYOC) does not mean the same thing as extending that direct resale model to every country. It lets the contact-center workflow and the carrier network meet through a managed connection.

In Salesforce’s BYOC guide, that connection can preserve a customer’s existing carrier relationship, commercial terms, service-level agreements and phone numbers. This is not merely a technical convenience. A customer has already printed its number on packaging, placed it in advertising and taught callers to trust it. Replacing it can create work well beyond moving a switch: customers may need to update suppliers, escalation plans and emergency-location records. Keeping the number can therefore be more valuable than the claim that a cloud contact center is “global.”

The same guide spells out what the interface does not absorb. For BYOC outbound calls, Salesforce says caller-attestation responsibility belongs to the carrier. Additional emergency-service setup and accurate location information also require the carrier; Salesforce routes the emergency call, but the carrier must arrange the number and location so the call reaches the right dispatcher. Salesforce warns that emergency-service settings associated with Salesforce-managed numbers do not simply follow a customer that switches to BYOC numbers. These are operating responsibilities, not a footnote to an AI feature.

Bandwidth is trying to make the carrier path easier to buy. Its product page markets a pre-built integration, a choice between customer-managed and Bandwidth-managed session border controller infrastructure, number configuration and porting before contact-center migration. The company presents one carrier, one integration and one support team as a way to reduce the work of coordinating several vendors. Those are commercial claims; the reviewed page does not supply a named rollout, independent uptime result for this integration, migration scorecard or pricing comparison.

That creates a plausible distribution advantage, not proof of a financial windfall. Salesforce can keep the case record, agent workflow and software relationship inside its service product while relying on an external carrier for part of the voice path. Bandwidth can be introduced at the point where numbers and trunks are configured, potentially making its network and orchestration harder to separate from a customer’s contact-center migration. But “first certified” does not mean exclusive, and neither company has disclosed a revenue share, contract minimum, expected call volume or incremental revenue from the September expansion.

The buyer’s trade is equally concrete. A company that wants to preserve its number, current carrier terms and local coverage can use BYOC rather than treating Salesforce’s direct calling plan as universal. A company that chooses Bandwidth’s offer may exchange multiple provider relationships or an in-house session border controller for one managed path and porting process. The right comparison is not native versus old. It is the cost of integration and migration against the value of number continuity, local coverage and clear accountability when a call fails.

The market should therefore read the partnership as a carrier-layer product attached to a native CRM workflow. Salesforce is not removing the telephone network from the contact center; Bandwidth is packaging a way through it. The global thesis becomes stronger only when the October markets are actually available, customer numbers are live, call types and emergency responsibilities are clear, and a customer can report that migration was simpler without losing control of its carrier relationship.

Sources