​

Sender Pools

​

When to use a pool

• High-volume sending — spread messages across several numbers so throughput and carrier reputation aren’t concentrated on one sender.
• Conversation continuity — a support or marketing thread should always reply from the same number the contact already has in their inbox (sticky).
• Local presence — a recipient in France should see a French number, a recipient in Brazil a Brazilian one (geomatch).
• Deliverability rotation — swap out numbers whose reputation has degraded without changing anything in your send code.

​

Configure in the dashboard

• Create a pool — click Create pool. In the panel that opens, name the pool, pick a strategy (the radio options describe each one’s behavior in one line before you commit), and select the sending DIDs. The selector contains your tenant’s numbers that aren’t already in another pool — a given sender can belong to only one pool, so a new pool stocks only untouched numbers, and alphanumeric sender IDs and short codes you add via the API still carry over when you edit later. A one-click Use all verified inventory action stocks the pool with every eligible sender at once.
• Edit members — click Edit on a pool row to change the name, strategy, or membership. Members a different pool owns are excluded from the selector, so two pools can never claim the same sender.
• Inspect a pool — expand a row’s Preview panel. It ships three analytics blocks:
  • Member health & rotation alerts — each member’s deliverability score with a health tier, plus a banner when degraded members are queued for auto-rotation, so you see the same signal the rotation scheduler acts on.
  • Verified inbound inventory — which members count as send-eligible numbers of yours, with the exact gate a member fails (number not in your inventory, not active, or missing the inbound SMS route) so you can fix the row instead of rotating through nothing.
  • Preview — run the sender a given recipient would get. Note the console warns that previewing a sticky pool commits that assignment — use the preview endpoint below from the API when you need a strictly read-only check.

​

Creating a pool via the API

curl -X POST https://api.orbit.devotel.io/api/v1/messaging/sender-pools \
  -H "X-API-Key: dv_live_sk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "label": "US marketing rotation",
    "sender_dids": ["+14155550100", "+14155550101", "+14155550102"],
    "strategy": "sticky"
  }'

​

Selection strategies

​

Previewing a selection

curl "https://api.orbit.devotel.io/api/v1/messaging/sender-pools/pool_abc123/preview?recipient_phone=%2B33612345678" \
  -H "X-API-Key: dv_live_sk_your_key_here"

​

Deliverability health

​

Endpoints

​

See also

• Messaging credentials & services — attaching a pool as a messaging service’s sending identity
• Fix an empty sender pool — what to do when a send returns 422 SENDER_POOL_EMPTY
• SMPP — an alternative way to submit the sends a pool routes