Bandwidth vs Respond.io

The release stream splits cleanly in two: one entry that adds a product line and a run of entries that remove reasons to open a support ticket. Identity Presentation, in beta since mid-August, is the product line — branded, authenticated caller identity rendered on the handset. Everything since has been console and self-service work: RCS test-number management, Voice API debug logs surfaced in Voice Insights, port-in FOC changes and cancellations up to ten minutes before the port, MOS scores in the app, and now 10DLC campaign registration moving out of API-only access into the Bandwidth App alongside brand sharing across accounts.

The registration surfaces are converging on a single console. 10DLC and RCS both have Registration Centers, both reached the app within a week of each other, and both took the same API-first, UI-second order — integrators served first, operators after. The reseller item is the more consequential half of this release: sharing brands natively across accounts treats the multi-account hierarchy as a first-class structure rather than something customers duplicate records to work around, which matters for the wholesale and reseller business that carrier-adjacent vendors depend on.

Expect the remaining registration and porting workflows to follow the same API-then-UI path into the Bandwidth App, and the RCS Registration Center to pick up the cross-account brand sharing that 10DLC just received. Whether Identity Presentation leaves beta is the open question these entries do not answer.