Skip to main content
An agency or parent organization often registers the 10DLC brand and campaign, the toll-free verification, or the short code, while a sub-organization does the sending. Number sharing lets the parent grant a sub-organization the use of one specific number, without moving anything and without exposing the registration behind it.

​
What a share is

A share is one phone number granted to one organization under yours, with a nickname you choose. Whatever sits behind the number rides along automatically: the 10DLC campaign and brand, the toll-free verification, or the short code profile. Nothing else is shared: not the brand, not the campaign, not the other numbers on them. The organization you share with sees the nickname and the digits. It never sees your brand name, campaign name, registration details, business profile, or provider identifiers. On its side the number simply appears under Provisioning > Shared With You, in the project form under Shared numbers, and as an owner it can upload contact lists, media, and opt-out lists to.

​
What stays with you

  • Billing. You keep paying the registration and monthly number fees. The sub-organization pays the per-message usage for what it sends, from its own balance, exactly as it would on its own numbers.
  • Control. The sub-organization cannot edit, release, or delete the number, cannot buy more numbers into your campaign or verification, and cannot share the number onward.
  • Your assets. Your contact lists, media, and opt-out lists never become visible to the sub-organization. It uploads its own under the nickname, or uses its organization-wide lists and media.

​
Opt-outs apply to the number

Carriers treat STOP per sending number, and so does the platform. When a contact replies STOP to a message sent from a shared number, that contact is opted out of the number for you and for every organization you share it with, whichever project the reply came in on. START reverses it everywhere. Each organization keeps its own Replied Opt-Outs and Tagged Opt-Outs lists for the share (labeled by the nickname), and every project sending from the number is suppressed by all of them. This is the one compliance implication of sharing, and the share dialog states it.

​
Sharing a number

  1. Open the number on Provisioning > 10DLC (campaign view), Provisioning > Toll Free, or Provisioning > Short Code.
  2. Choose Share, pick an organization under yours, and give the share a nickname. The nickname is what the sub-organization sees, and it must be unique among the numbers you share with that organization.
  3. The same dialog lists every organization the number is shared with, lets you rename a share, and lets you revoke one.
Sharing requires the provisioning.manage permission. Only organizations directly or indirectly under yours can be chosen.

​
Using a shared number

In the project form a Sender choice appears once your organization has at least one shared number: My numbers or Shared numbers. Pick the shared number by its nickname; the channel and campaign or verification are filled in from the share. A project uses either your own numbers or shared numbers, never a mix, and every shared number on one project must come from the same campaign or verification. Projects on a shared number show the nickname where your own projects show the brand and campaign, and carry a Shared badge.

​
Revoking a share

Revoking a share, or releasing the number, immediately pauses every scheduled or running project the sub-organization has on that number, with the reason shown on the project. Drafts keep their settings until edited. The sub-organization is notified, picks a different number, and starts the project again; a revoked number cannot be reselected. Its opt-out lists for the share are kept.

​
On the API

GET /v1/phone-numbers includes shared numbers for the organizations the key can access, with shared: true and nickname; on those rows the owner’s names and brand_id are null. Projects created through the API on shared numbers pass the share’s campaign_id (or toll_free_verification_id) with the shared phone_number_ids, and their brand_name and campaign_name read back as the nickname.