A2P 10DLC

Bandwidth vs Outright Vanity Numbers

29 min read

Bandwidth (NASDAQ: BAND) is a Tier-1 US wholesale voice carrier that also sells a CPaaS layer on top of its own network. Many other CPaaS providers route their US calls through Bandwidth's underlying carrier infrastructure. Outright vanity is a recall asset bought once and kept forever. The mental model that ends most "Bandwidth vs vanity" confusion in two sentences: Bandwidth owns the US carrier network underneath the call; you should own the number that rides on it. Two assets, owned individually, working in the same enterprise voice stack.

Here is how to make the call in roughly two minutes:

  1. Are you running enterprise voice volumes — contact center, healthcare clinical line, retail multi-store, financial-services compliance — and need direct-carrier economics with strong 911 and STIR/SHAKEN posture? Bandwidth is the natural answer. They are the carrier under the carrier. Skip to the porting, E911, and attestation sections below.
  2. Are you a business owner who wants a memorable phone number on a billboard, truck wrap, business card, or storefront window? Buy outright from Digit Exclusive. The number is a recall asset. From $200–$250 one-time, no subscription, no recurring fees, no SIP trunk required.
  3. Are you an enterprise voice architect who needs both a public-facing main line AND high-volume programmable voice with E911 compliance for the product? You need both. Buy a vanity outright for the published main line. Use Bandwidth for the programmable voice, SIP trunking, 911 dynamic location handling, and A2P 10DLC messaging. The two layers are complementary; Bandwidth itself is built around BYO-number flows and bulk port-ins.
  4. Are you currently running a Bandwidth-issued DID as your main published line and feel like the recall is not landing? Buy a vanity outright, port it into Bandwidth, and route it through your existing SIP trunk and call flows. Standard FCC LNP applies — your existing Bandwidth integration keeps working, with a memorable number on the front.
  5. Are you trying to decide which one to "replace" with the other? Stop. They are not competing answers. Bandwidth is the carrier-network layer. Vanity is the brand-recall layer. The honest question is which jobs go to which layer.

The rest of this article is the honest comparison table, an explainer on why Bandwidth being a Tier-1 carrier actually matters for enterprise buyers, the porting mechanics under 47 CFR Part 52, the E911 dynamic-location story under Kari's Law and RAY BAUM'S Act, the buyer profiles where each tool genuinely wins, and a "yes both" middle section where most enterprise voice buyers actually land. We sell vanity numbers From $200–$250, one-time. Bandwidth publishes pay-per-use voice and messaging at roughly $0.35 per local DID per month, $0.0035 per outbound voice minute, $0.0025 per SMS segment, with volume discounts that kick in fast at enterprise scale. Two different price models, two different layers, frequently the same buyer running both at once.

The Three-Column Comparison Most Articles Skip

Most articles comparing Bandwidth to "buying a vanity number" frame it as either/or. It is not. The honest comparison is three columns wide: Bandwidth programmable DID, Outright vanity from Digit Exclusive, and Hybrid: outright vanity ported into Bandwidth for programmability. The hybrid is what mature enterprises, contact centers, healthcare networks, and multi-location retailers actually run.

Dimension Bandwidth programmable DID Outright (Digit Exclusive only) Hybrid: Outright + port to Bandwidth
Setup cost ~$0.35/month per local DID, no upfront, volume tiers From $200–$250 one-time From $200–$250 one-time + Bandwidth port-in (typically free for simple US local at volume)
Voice usage cost ~$0.0035 per minute outbound, similar inbound, contracted lower at volume None at the number layer; depends on your downstream carrier Same as Bandwidth column once ported in
SMS cost (A2P 10DLC) ~$0.0025 per outbound segment, plus TCR brand and campaign fees Not the job of the outright number itself Same as Bandwidth column once ported in
Year-1 cost (1 number, light use) ~$4.20 carrier + variable usage $250 to $600 typical, paid once $250 to $600 + Bandwidth carrier + usage
Ongoing year cost ~$4.20 + per-minute and per-segment usage $0. Already paid. ~$4.20 + Bandwidth usage (number is yours)
Network position Tier-1 US wholesale voice carrier. Owns the underlying network. Standard PSTN inheritance from upstream regulated carrier Tier-1 carrier underneath your owned number
STIR/SHAKEN attestation Native A-attestation for properly registered traffic. Bandwidth signs at the carrier of record level. Inherited from upstream carrier; varies Strong A-attestation via Bandwidth's signing chain
911 / E911 handling Direct integration with national 911 ALI databases. Dynamic location for MLTS under Kari's Law and RAY BAUM'S Act. Inherited from your downstream carrier; not the job of the recall asset Direct E911 once ported into Bandwidth; vanity layer remains separate concern
Programmability (SIP trunking, REST APIs, webhooks) First-class. Voice, Messaging, Phone Number Lookup, Numbers Dashboard. Less polished SDK story than Twilio. None. It is just a phone number. Pair with whatever you like. Same as Bandwidth column once ported in.
Vanity selection Whatever Bandwidth's own DID inventory and upstream pools hold. Premium repeating-digit, AABB, ABAB, mirror, word-spell selection mostly absent at retail. Premium recall: pattern, area-code, repeating-digit, word-spell selection. Premium recall + Tier-1 carrier underneath in one stack.
Port-in allowed? Yes. Bandwidth supports bulk LNP via Numbers Dashboard or Numbers API; designed for thousands-DID enterprise migrations. Number ships portable from purchase. Yes. Standard LOA + carrier verification document.
Port-out allowed if you leave? Yes. Standard FCC LNP applies; Bandwidth releases the number to the receiving carrier. Always. The number is yours from purchase. Always. Leave Bandwidth and take the number elsewhere.
Best fit Enterprise voice volumes, contact centers, MLTS E911 compliance, software vendors who need direct-carrier economics rather than CPaaS markup. Memorable, brand-bearing main line. Permanent ownership. Most mature enterprise voice stacks running both layers correctly.

Read the table once. Notice the three columns are answering three different questions, not the same question with different answers. Bandwidth's column answers "what carrier carries my voice traffic at scale and how much does it cost per minute." The outright column answers "what number is published on my building, my truck, my email signature, my Yelp profile." The hybrid column is most enterprise voice architects' real answer, and it is a sum, not a choice.

Why Bandwidth Owning the Carrier Network Is Their Real Wedge

Most CPaaS providers — Twilio, Plivo, Sinch, MessageBird, much of Vonage's API tier — are resellers of underlying voice carriers. They put a beautiful API in front, route the call through one or more wholesale carriers underneath, and charge you a markup over the underlying carrier's per-minute rate. Bandwidth sits one layer below that. Bandwidth IS one of the underlying carriers. Twilio well-documentedly relies on Bandwidth as a primary US voice carrier under the hood. Dialpad-class UCaaS and many contact-center platforms route US PSTN traffic through Bandwidth at the carrier layer.

For a buyer running enterprise voice volumes, that one-layer-down position is the wedge:

Direct-carrier economics

Per-minute rates compound fast. A 500-seat contact center placing four hours of outbound voice per agent per day moves roughly 240,000 minutes a day, 60 million minutes a year. The difference between $0.005 a minute and $0.0035 a minute is $90,000 a year on that single line item. At 5,000 seats that becomes $900,000. CPaaS markup is real; eliminating one resale layer is the structural cost wedge that drives enterprise voice buyers down to Bandwidth from Twilio and Plivo. The number itself, the recall asset on your customers' lock-screen and your billboard — that economics question is unrelated. Buy that outright once.

STIR/SHAKEN A-attestation

Under FCC call-authentication rules, US carriers attest to the legitimacy of outbound calls at three levels — A (full attestation, the carrier vouches the originator owns the number), B (partial), or C (gateway). A-attestation is what reduces the chance your outbound call gets flagged as Spam Risk by terminating carriers and analytics platforms (TNS, First Orion, Hiya). Because Bandwidth is the carrier of record for numbers it provisions and ports, Bandwidth signs A-attestation natively for properly registered traffic, with no second-hop attestation downgrades. CPaaS providers further up the stack often hand calls to Bandwidth for the actual signing, which works, but at the carrier-of-record layer Bandwidth controls the attestation chain directly.

911 and E911 dynamic location

This is the section that closes most regulated enterprises on Bandwidth. Kari's Law and RAY BAUM'S Act require multi-line telephone systems (MLTS) to (a) support direct 911 dialing without a prefix and (b) deliver dispatchable location to the public-safety answering point (PSAP). Bandwidth has deep direct integration with the national ALI (Automatic Location Identification) databases and offers dynamic location updating for soft phones, multi-floor offices, multi-campus environments. For a hospital running clinical lines, a multi-tenant office building, a school district, a Fortune 500 with hot-desking — this is not optional, and a CPaaS routing through Bandwidth as opposed to being Bandwidth introduces a layer the regulator looks at twice.

Direct enterprise support

Bandwidth's customer roster is enterprise-heavy. Their named-account model, NOC, and incident playbooks are built for that audience. CPaaS support is more email-and-ticket; Bandwidth support escalates faster for accounts at SLA scale. None of this matters to a solo founder. All of it matters to a 10,000-seat contact center.

None of this turns Bandwidth into a vanity-number provider. Their DID inventory is exactly that — inventory, sourced from their own number blocks and upstream pools, with selection optimized for "we have an LRN-compliant DID in this rate center" not "we have a memorable AABB pattern in 404." For premium recall — the kind of number that sticks on a billboard — you go to a curated outright seller. Outright purchase answers the recall question; Bandwidth answers the carrier question; the two layers stack cleanly.

Five Jobs Bandwidth Wins Outright, Five Jobs Outright Vanity Wins Outright

Honest comparison means saying when the other tool is the right tool. We sell vanity numbers. We will tell you the five jobs Bandwidth genuinely owns, with no caveat.

Five jobs Bandwidth wins outright

  1. Enterprise outbound voice at scale. 500-seat-and-up contact centers, sales floors, healthcare clinical-line operations. The per-minute math at Bandwidth's direct-carrier rates beats any CPaaS reseller, period.
  2. MLTS E911 compliance. Multi-floor offices, hospitals, school districts, multi-tenant buildings under Kari's Law and RAY BAUM'S Act. Direct ALI integration and dynamic-location handling is structurally cleaner one layer down.
  3. Bulk port-ins. Migrating 5,000, 25,000, 100,000 DIDs off a legacy carrier? Bandwidth's Numbers Dashboard and Numbers API are built for this; they handle it as a routine engagement, not an exception.
  4. Software vendors who need direct-carrier economics. If your product margin on each customer call is being eaten by CPaaS markup, going down to Bandwidth as the carrier of record is the structural fix.
  5. Carrier-grade STIR/SHAKEN A-attestation control. Brands managing outbound contact reputation at scale want signing control at the carrier of record, not handed up the stack.

Five jobs outright vanity wins outright

  1. Premium recall on published surfaces. Billboards, truck wraps, business cards, storefront windows, branded merchandise. The number that humans memorize and dial without looking it up is a curated asset, not a randomly assigned DID.
  2. Permanent ownership without recurring billing. Outright purchase from Digit Exclusive means you own the number from From $200–$250, one time, kept forever. No CPaaS bill, no carrier rental fee, no platform-bound risk.
  3. Brand-bearing main lines for non-technical businesses. Real estate brokers, contractors, restaurants, attorneys, dentists, salons, studios. The published main line is a brand asset; outright purchase is the natural fit, then route through whatever normal carrier the business already uses.
  4. Personal vanity ownership. Creators, side hustlers, sports fans, gift recipients, anyone who wants a memorable number on a personal SIM. Personal vanity inventory covers exactly this use case; Bandwidth is overkill for a single-line personal number.
  5. Decoupling the recall asset from the carrier vendor. Whatever carrier you run today, whatever you switch to in three years, the number on the billboard does not change. Outright ownership decouples brand-recall from carrier vendor relationships.

Notice neither list contains "Bandwidth is bad at recall" or "outright vanity is bad at SIP trunking." Both statements would be technically true and rhetorically useless. The right framing is: Bandwidth and outright vanity solve different problems. Most enterprise voice buyers have both problems.

The Hybrid Stack: Outright Vanity Ported Into Bandwidth

Here is what most mature enterprise voice architects actually run. The pattern has three steps and three buyer archetypes worth walking through, because the pattern looks different at a hospital network versus a SaaS contact center versus a national franchise.

The three-step pattern

  1. Buy the vanity outright. Pick the number from curated inventory — pattern, area code, repeating digits, word-spell, whatever the brand wants. Pay once, From $200–$250. The number ships portable; you become the subscriber of record on a regulated common carrier from purchase.
  2. Submit a port-in to Bandwidth. Open a port request through Bandwidth Numbers Dashboard or Numbers API. Sign Bandwidth's Letter of Authorization, attach the carrier verification document from Digit Exclusive's seller-side carrier, set the port date. Bandwidth handles the LNP exchange under FCC number-portability rules. Simple US local ports complete in roughly 2 to 10 business days.
  3. Cut the SIP trunk over. Configure your contact center, PBX, or programmable voice app against Bandwidth's SIP trunking. Set up STIR/SHAKEN attestation, register A2P 10DLC for messaging, configure E911 dispatchable-location records. Your published vanity number now rides Bandwidth's Tier-1 network, attests A natively, and you own the recall asset permanently.

Hybrid archetype 1: hospital network

A 12-hospital regional health system runs a vanity main line on every campus — easy-to-recall numbers patients can dial under stress without looking them up. They port those vanities into Bandwidth as the carrier of record. Bandwidth handles E911 dynamic location for clinical staff who roam between buildings. Vanity layer is recall and patient-experience; Bandwidth layer is carrier compliance and 911 routing. Two layers, owned individually.

Hybrid archetype 2: SaaS contact center

A B2B SaaS company runs a 200-seat outbound sales operation plus a 50-seat support desk. Their published main line is a vanity number on the homepage and on every sales rep's email signature. They port the vanity into Bandwidth, run sales-dial outbound through Bandwidth's voice API at $0.0035 a minute, sign STIR/SHAKEN A natively, and avoid the CPaaS markup that would have added six figures a year at their volume. Recall layer is brand; Bandwidth layer is unit economics.

Hybrid archetype 3: multi-location franchise

A national franchise with 800 locations runs one vanity main line per metro that routes geographically to the nearest store. Vanity numbers are bought outright, ported into Bandwidth, and routed through a Bandwidth voice API contact-center router. New locations get added by porting in additional outright vanities and adding routing rules. Recall layer is brand uniformity; Bandwidth layer is geographic-routing scale.

None of these stacks are exotic. All three are common engineering patterns at enterprises currently running on Bandwidth. The reason most articles miss them is that the articles are written by content marketers paid to compare two products as if they competed. Bandwidth and outright vanity do not compete. They stack.

Where Bandwidth Genuinely Falls Short, Honest Read

Five honest weaknesses in Bandwidth that a buyer should know before signing:

Developer-experience polish lags Twilio

Bandwidth's APIs work. The documentation has improved meaningfully over the last few years. But for a developer comparing the unboxing experience side-by-side with Twilio, Bandwidth feels more enterprise-ops and less developer-first. The SDK story is thinner. The integration catalog is smaller. If a small team wants to build a voice app in a weekend, Twilio is the faster on-ramp; Bandwidth pays off at scale, not at hello-world.

Smaller integrations and ecosystem catalog

Twilio Studio, Twilio Flex, the wide ecosystem of Twilio-integrated SaaS — Bandwidth's analog is meaningfully thinner. If your stack assumes "this contact-center platform integrates with Twilio out of the box," check Bandwidth integration support before assuming parity. Often supported, sometimes not, sometimes via a partner connector rather than first-party.

Vanity-number selection is generic

This is structural to being a wholesale carrier rather than a vanity retailer. Bandwidth provisions DIDs from inventory; you take what is in the rate center. Premium repeating-digit, AABB, ABAB, mirror, ascending, word-spell — those patterns are rare to absent in standard provisioning. For curated recall inventory, you go to a vanity retailer and port in. Bandwidth is the carrier; the vanity is bought elsewhere.

Self-serve experience assumes technical setup

A non-technical small-business owner is not the Bandwidth buyer profile. Account onboarding assumes you know SIP, LOA flow, A2P 10DLC concepts, E911 record format. There is no equivalent of a polished UCaaS dashboard like RingCentral or Dialpad. For non-technical SMBs, an outright vanity routed through a normal carrier is the right pattern; Bandwidth is overkill.

Pricing requires volume to fully unlock

Published rates are competitive at any volume. The really aggressive pricing — the per-minute rates that beat Twilio and Plivo by meaningful margins — kicks in with negotiated enterprise contracts. A small-volume buyer pays close to list and sees less of the structural advantage. Bandwidth becomes a no-brainer at high volume; at low volume the developer experience often outweighs the rate savings.

None of these weaknesses are dealbreakers for the right buyer. All of them are reasons a 50-seat startup might prefer Twilio while a 5,000-seat enterprise prefers Bandwidth. Pick by buyer profile, not by partisan loyalty to either brand.

Buyer Profiles: Which Tool Lines Up With Who You Actually Are

Five buyer profiles seen often, calibrated to the enterprise-voice audience Bandwidth competes for, and the recall-asset audience outright vanity serves.

Profile 1: enterprise voice architect at a 1,000+ seat contact center

You evaluate carriers on per-minute economics, A-attestation control, ALI/E911 integration depth, NOC responsiveness, and bulk port-in maturity. Bandwidth is your default. The recall layer — the published main line on your customer-facing surfaces — is a separate decision. Buy the vanity outright, port it into Bandwidth, route it through your existing trunk groups. Two layers, owned individually.

Profile 2: SaaS founder building a voice product

You weigh Twilio's developer polish against Bandwidth's direct-carrier economics. At < 1M minutes a year, Twilio's SDK ergonomics typically win. At > 10M minutes a year, Bandwidth's per-minute math typically wins. At the in-between, hybrid stacks running Twilio on top of Bandwidth as the underlying voice carrier are common. The vanity number you publish on the homepage is not in the trade-off; it is bought outright separately.

Profile 3: regulated enterprise compliance-driven buyer

Healthcare network, financial-services firm, school district, multi-tenant commercial real estate. Kari's Law and RAY BAUM'S Act compliance is non-optional; ALI/E911 record correctness is audited. You want the carrier of record one layer down for cleaner attestation and dispatchable-location handling. Bandwidth is structural fit. The vanity main line, if any, is bought outright; the carrier compliance is Bandwidth's job.

Profile 4: telephony reseller / MSP

You sell voice services to your own SMB customers. Bandwidth is one of the wholesale carriers you can build on top of, alongside Inteliquent, Peerless, Sinch Voice. You aggregate, mark up, resell. For your own customers' brand-bearing main lines, outright vanity is the right recall layer. Buy outright, port into Bandwidth (or whichever wholesale carrier you build on), resell as a managed service. The recall asset belongs to the customer; the carrier service belongs to you.

Profile 5: SMB owner pitched Bandwidth by an IT consultant

An IT consultant or VAR mentioned Bandwidth as the answer to your business phone problem. Honest read: probably not, unless you are at meaningful enterprise scale or have specific E911-MLTS compliance constraints. For a single-location small business, an outright vanity number routed through any normal mobile carrier (Verizon, AT&T, T-Mobile) or hosted PBX (RingCentral, Dialpad, 8x8) is faster, simpler, and cheaper for your volume. Bandwidth becomes the right answer when your volume or compliance posture justifies the engineering investment.

Porting a Vanity Number Into Bandwidth: The Mechanics

The hybrid pattern depends on Local Number Portability working cleanly. Under 47 CFR Part 52, US wireline and wireless customers have the right to keep their phone number when changing carriers. Bandwidth honors LNP for both port-in and port-out as a matter of regulatory baseline; their bulk-port operations are a key strength.

Step 1: buy outright

Pick the number from Digit Exclusive inventory, complete the From $200–$250 one-time purchase. You are now the subscriber of record on the seller-side regulated carrier. The number is portable from purchase; nothing on our end blocks LNP.

Step 2: open a port request in Bandwidth

Through Numbers Dashboard or the Numbers API, submit a port-in request. Required artifacts: Letter of Authorization signed by the new subscriber, carrier verification document (CSR — customer service record) from the seller-side carrier confirming subscriber name, billing address, and current carrier. Bandwidth's port-ops team validates and submits to NPAC. Simple US local ports complete in 2 to 10 business days. Toll-free ports run on RespOrg, which is a different process and cluster — Bandwidth handles both, but the workflows differ.

Step 3: configure routing

Once the port completes, configure SIP trunk endpoints, A2P 10DLC brand and campaign registration if SMS is in scope, E911 dispatchable-location records, and STIR/SHAKEN attestation policy. The vanity number is now riding Bandwidth's Tier-1 carrier network with full programmability and compliance posture. Total elapsed time from purchase to live: typically 2 to 3 weeks for the port plus a few days for configuration.

Step 4: validate

Place test calls. Verify ALI lookup returns the correct dispatchable location. Verify outbound calls sign A-attestation. Verify SMS A2P 10DLC delivers. Verify port-out works in reverse, in case you ever leave Bandwidth — sanity test that your continuity plan is real, not theoretical.

For carriers other than Bandwidth, equivalent porting how-tos cover Verizon, Google Voice, and other consumer-facing carriers when the vanity is destined for a non-enterprise stack.

Bandwidth vs the CPaaS Resellers Above It

For technical buyers comparing CPaaS options, the practical question is often "Bandwidth versus Twilio versus Telnyx versus Plivo." Honest read on each:

vs Twilio

Twilio wins on developer polish, SDK breadth, integrations catalog, no-code tooling like Studio and Flex. Bandwidth wins on direct-carrier economics at scale, A-attestation control at the carrier of record layer, E911 depth, and bulk-port maturity. Many enterprises run Twilio on top of Bandwidth as the underlying voice carrier — getting Twilio's developer experience with Bandwidth's underlying network. See the dedicated Twilio comparison for the recall-vs-CPaaS framing.

vs Telnyx

Telnyx also owns infrastructure — a private global IP backbone — and competes with Bandwidth on the network-ownership argument. Difference: Telnyx is more developer-direct in tone and product surface; Bandwidth is more enterprise-direct. Telnyx skews toward technical SaaS founders and contact-center engineers; Bandwidth skews toward enterprise voice architects and regulated buyers. Both beat the resell-only CPaaS layer on per-unit economics; pick on buyer profile.

vs Plivo

Plivo competes on cost-leadership-versus-Twilio, similar pitch to Bandwidth but at the developer-API layer rather than the wholesale-carrier layer. Plivo for smaller-volume cost-engineering buyers. Bandwidth for larger-volume enterprise buyers who need carrier-of-record control. Different audiences, different sizing.

vs Dialpad / RingCentral / Vonage UCaaS

Different category. Dialpad, RingCentral, Vonage Business, 8x8 are UCaaS — fully managed business phone systems. They compete with each other; they do not compete with Bandwidth, which sits underneath UCaaS as a possible carrier provider. UCaaS is for non-technical SMBs that want a turnkey phone system. Bandwidth is for technical teams building voice infrastructure.

The vanity number layer is the same across all of these comparisons. You buy outright once, From $200–$250, and route it through whichever stack matches your team's technical posture and volume. Whether the underlying carrier is Bandwidth, whether the API layer is Twilio or Telnyx or Plivo, whether the UCaaS skin is Dialpad or RingCentral — the recall asset on your billboard does not change.

Related vanity-number buyer guides

Use these related guides to compare one-time purchase options, carrier transfer fit, and memorable local number patterns:

More related vanity-number resources

Related vanity-number resources

Related vanity-number resources

Frequently Asked Questions About Bandwidth and Vanity Numbers

Is Bandwidth a vanity-number provider?

No. Bandwidth is a Tier-1 US wholesale voice carrier with a CPaaS layer on top of its own network. They provision DIDs from their inventory and from upstream carrier pools, optimized for "we have a compliant DID in this rate center" rather than "we have a memorable AABB pattern in 404." Vanity selection on Bandwidth reflects whatever inventory holds at provisioning time; premium repeating-digit, AABB, ABAB, ascending, mirror, and word-spell patterns are not the curated product. Curated vanity inventory lives at outright sellers like Digit Exclusive, RingBoost, NumberBarn, PhoneNumberGuy, and 800.com.

Can I port a vanity number I bought outright into Bandwidth?

Yes. Bandwidth supports number porting under standard FCC LNP rules and is genuinely strong at it — bulk ports of thousands of DIDs are routine engagements for them. You buy the vanity outright from Digit Exclusive, submit a port-in request through Numbers Dashboard or the Numbers API, sign Bandwidth's Letter of Authorization, provide the carrier verification document (CSR) from the seller-side carrier, and the port completes in roughly 2 to 10 business days for simple US local ports. The hybrid pattern — outright vanity ported into Bandwidth for programmable voice and SIP trunking — is supported and common for enterprise voice buyers.

Can I port a Bandwidth number out if I leave?

Yes. Bandwidth honors port-out requests under FCC LNP. The receiving carrier initiates the port, you sign the LOA, Bandwidth releases the number. There is no carrier-layer lock-in; the only lock-in is in the integration code you write against Bandwidth's APIs and SIP infrastructure, which is a software-engineering concern, not a carrier-rights concern. Outright purchase from Digit Exclusive eliminates carrier-layer lock-in entirely; the number is yours from purchase regardless of which carrier carries the call.

What does Bandwidth actually charge for a phone number?

Roughly $0.35 per month per US local DID at retail rates, with voice usage around $0.0035 per minute outbound and SMS around $0.0025 per segment for outbound A2P. Toll-free DIDs run higher. These are typical published rates and shift with usage tier and contract — Bandwidth's enterprise pricing kicks in below those numbers at meaningful volume. The number itself remains a recurring rental at the carrier layer, just at lower per-unit cost than CPaaS resellers above Bandwidth in the stack. An outright vanity from Digit Exclusive is a one-time From $200–$250 purchase at the recall layer, separate from the carrier-rental decision.

Is Bandwidth's STIR/SHAKEN attestation actually different from a CPaaS provider's?

Yes, in two practical ways. First, Bandwidth signs at the carrier of record level for numbers it provisions, which means A-attestation is native rather than handed up the stack. Second, Bandwidth has direct visibility into the originating-customer registration, so attestation policy can be enforced one layer down where many CPaaS providers depend on Bandwidth (or another wholesale carrier) to actually sign the call. For brands managing outbound contact reputation under FCC robocall-mitigation rules, signing control at the carrier of record is structurally cleaner. The vanity number itself is irrelevant to attestation; signing belongs to the carrier.

What is the difference between Bandwidth and a CPaaS like Twilio?

Bandwidth is a Tier-1 US wholesale voice carrier that also operates a CPaaS layer. Twilio is a CPaaS provider that historically routes much of its US voice traffic through wholesale carriers including Bandwidth. The practical difference: Bandwidth controls the underlying carrier infrastructure (network, attestation, ALI/E911 integration, port operations) and prices per-unit closer to the network floor. Twilio controls the developer-experience layer (SDKs, Studio, Flex, integrations) and prices with a markup over its underlying carrier costs. Enterprise buyers at meaningful volume often run Twilio on top of Bandwidth — Twilio for developer ergonomics, Bandwidth for carrier-of-record economics. The vanity number you publish lives at a third layer, bought outright once, separate from either decision.

Does Bandwidth support A2P 10DLC for SMS?

Yes. Bandwidth handles A2P 10DLC brand and campaign registration as part of its messaging product. This is required for legitimate US business SMS at any meaningful volume under TCR (The Campaign Registry). An outright vanity number is irrelevant to A2P 10DLC; the registration belongs to the underlying programmable carrier and the messaging brand. If you are running transactional SMS, two-factor codes, or marketing SMS at scale on Bandwidth, you handle 10DLC at Bandwidth; the vanity layer is a separate question entirely.

Can I run a SIP trunk to my PBX with a vanity number from Digit Exclusive?

Yes. Buy the outright vanity, then port it into Bandwidth (or Telnyx, or another SIP-trunking carrier of your choice). Configure a SIP trunk from Bandwidth to your PBX — Asterisk, FreePBX, FreeSWITCH, 3CX, Cisco CUCM, Avaya — using the credentials and IP-auth method Bandwidth publishes. The outright purchase decouples the number-ownership question from the PBX-and-trunking decision. You own the number; you choose the SIP carrier separately; you choose the PBX separately. Three independent decisions instead of one bundled rental.

What happens to my Bandwidth number if I stop paying Bandwidth?

The number returns to Bandwidth's pool after a grace period and is eventually re-assigned. This is standard for rented numbers across all carriers — Twilio, Telnyx, Plivo, RingCentral, Vonage, and traditional carriers behave the same way. The implication: if the number is brand-bearing, do not let billing lapse, and consider porting to your own carrier of record before any payment risk. Outright purchase from Digit Exclusive eliminates the lapse-risk failure mode entirely. Owning the number means a vendor change, a billing dispute, or a service outage at the CPaaS or carrier layer never threatens the asset on your billboard.

Is Bandwidth a good choice for my business's main published phone number?

Usually only if you are operating at enterprise scale or have specific E911-MLTS compliance constraints. Bandwidth is built for enterprise voice infrastructure, contact-center engineering, regulated multi-line systems, and software vendors who need direct-carrier economics — not for brand-recall front-of-house phone lines at SMBs. The vanity selection is generic, the product surface is technical, and the recurring billing model attaches your published main line to a carrier API. For a technical company already operating at enterprise volume, porting an outright vanity into Bandwidth as the published main line is a clean pattern. For everyone else, buy the vanity outright and route it through a normal carrier or hosted PBX.

Where do I start if I am still not sure which I need?

If your answer involves the words SIP trunk, contact center, A2P 10DLC, MLTS, E911 dispatchable location, STIR/SHAKEN attestation, bulk port-in, or per-minute economics at scale, you need Bandwidth (or a peer such as Telnyx, Twilio, Plivo, or Inteliquent). If your answer involves the words billboard, truck wrap, business card, yard sign, storefront, email signature, or memorable, you need outright vanity from Digit Exclusive. If both sets of words apply, you need both — buy the vanity outright, port it into Bandwidth, run the carrier layer underneath. Two layers, owned individually. The five-year cost-comparison usually closes the recall-layer decision before the carrier-layer decision is even on the table.

For the broader buyer reference covering the outright-purchase model versus Bandwidth or any other hosted-PBX subscription, see buy a phone number outright — five-step purchase flow, side-by-side cost table, FCC LNP FAQ.

For the dedicated pricing-research breakdown — tier-by-tier prices ($200–$250 entry, $500-$2,500 mid, $10,000-$25,exclusive) and the five-year cumulative-cost math versus monthly subscription rentals — see how much does a vanity phone number cost.

Related number browsing: repeating digits

The US phone number marketplace landscape

This article touched on the marketplace model for buying US phone numbers. For the complete picture — how the marketplace model works under FCC NANP and LNP rules, side-by-side comparison of the seven established US marketplaces (Digit Exclusive, RingBoost, NumberBarn, PhoneNumberGuy, PhoneNumberExpert, 800.com, PhoneNumberWorld), pricing comparison vs VoIP subscription providers over 5 years — see our phone number marketplace guide. It includes the legal framework, the 4-step buying workflow, and the 5-year cost math that consistently favors outright purchase over subscription for any number used 18+ months.

Subscription vs outright purchase: If you are weighing recurring subscriptions against a one-time purchase, our Google Voice alternatives for business comparison covers real 2026 pricing, A2P 10DLC failures, and Workspace-bundle traps for owned-number alternatives.

Ready to buy? Start here

Every guide ends at the same place: real one-of-one US numbers, sold outright, ported to your carrier under FCC §52. Pick your starting point below.