Before creating a service, the code looks for the one the account's A2P registration is bound to, falling back to any service already recorded on a live number. Only when neither exists is a new service created. Numbers then live in that service's sender pool.
Also called: messaging service · second number · number per rep · one campaign for the whole company
- 1Purchase resolves an existing Messaging Service from the A2P registration, then from the number inventory.
- 2A new service is created only if neither exists.
- 3The bought number is attached to the service.
- 4The inbound webhook is set on the SERVICE, not the number.
The comment states the cost of the old behaviour: 'This used to mint a NEW service for every purchase, which under a per-rep-number model would demand a separate campaign per rep — more registration fees, more carrier review, and not how 10DLC is meant to work.' Setting the webhook on the service rather than the number is deliberate too: 'A2P campaigns attach to the service, numbers can be swapped underneath it, and a per-number webhook would have to be re-applied every time.'
- One service per number implied one campaign per rep — extra fees and extra carrier review.
- Per-number webhooks had to be reapplied whenever numbers changed.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →