IOSOR

IOSOR Learn

DID messaging readiness before production: profile, compliance, and catalog honesty

A rented, assigned DID is not a production SMS sender. Messaging profile, US 10DLC/TF verification, and catalog live vs in setup must align before an A2P blast.

A rented DID that shows assigned is not a production SMS sender. Assignment means the digits sit on your account and rent hits the prepaid wallet. Messaging readiness is another list: profile on that DID, US 10DLC or toll-free verification green when those gates apply, catalog live on the corridor you will blast, and an inbound path you actually own if you promised two-way. Teams that treat the Activated badge as A2P-ready learn from blocks, not from a status chip.

IOSOR rents numbers as just-in-time (JIT) purchase on a white-label prepaid wallet. Catalog live versus in setup is honest: a DID can be assigned while SMS on that number is still in setup. Near USD 1,000+ monthly, rent lines and failed A2P attempts enter commercial review. Buy path: JIT buying for virtual DIDs. Fail, refund, swap: DID order fail refund and swap. Local versus toll-free: local and toll-free rental reality.

Why assignment is not readiness

Assignment answers “whose number is this on the invoice.” Readiness answers “can we send production A2P from it today?” That is not the same row. A JIT buy can succeed, rent can start, and messaging can stay in setup. Voice-ready is not SMS-ready.

Status you see What it means What it does not mean
Assigned Digits on the account; rent booked Production A2P allowed
Messaging profile on Origin identity on this DID 10DLC / TF already green
Catalog live That corridor’s send path is open Every rented DID is blast-ready

Messaging profile on the rented DID

A messaging profile is the send identity bound to the DID: who originates, which webhook receives inbound, which campaign or use-case the traffic claims. A rented number without a profile is a billing object, not a sender. Confirm the profile hangs on this DID, not a sister test line. Client errors stay white-label — do not dump raw upstream codes on the buyer. If inbound is part of the job, the webhook must land at your consumer with idempotency before you call the number two-way.

US compliance gates before the blast

US A2P is gated. Local long codes typically need 10DLC brand and campaign registration plus retrievable opt-in. Toll-free needs verification before a production blast. OTP is not a loophole to skip registration.

Catalog live vs in setup on that number

Shop live means you can search and order. Messaging live on that assignment means the send path is actually open.

Red flags

  • Blast scheduled the hour the DID shows assigned
  • No messaging profile on the rented DID
  • US traffic without 10DLC or toll-free verification
  • Catalog in setup sold as production SMS
  • Two-way promised without inbound ownership
  • Client errors that name upstream brands
  • Rent charged while product treats assignment as A2P-ready

Start with IOSOR

Hang the messaging profile on this assigned DID, not a sister test line. If the corridor is US, record 10DLC or toll-free green before any A2P. Send five OTP fixtures — not a marketing blast. Export rent and SMS rows on the same number id so finance sees assigned is not ready.

IOSOR takeaway

Assignment books rent. Readiness is profile plus gate plus catalog live on that DID.

Do: prove OTP on this number before production A2P. Don’t: treat Activated as blast-ready, or sell in-setup SMS as live.

Was this guide helpful?

Related guides