Skip to main content

Customer-owned outbound number pools

Approved scope from the user: the entire outbound number-pool feature is BYOC-only. Customer-owned numbers retain geographic preference, up to three caller-switching attempts per sequence call step, and optional automatic replacement. Automatic purchase/release supports the customer’s independent Twilio account only. OpenCX-hosted numbers retain the existing single-number/single-call-per-step behavior, with no pools or replacement. No production configuration changes or real calls/purchases/releases are part of implementation. Each pool binds to one explicit non-hosted, workspace-owned outbound SIP trunk. Only verified non-hosted numbers from the same workspace are eligible. Calling must fail closed when that binding is missing or invalid; never fall back to hosted/global trunks. Non-pool single-number and explicit-trunk paths remain unchanged. For replacement, customers supply their independent account SID, auth token and carrier trunk SID. Verify active account ownership and matching customer trunk before saving encrypted credentials. Never expose credentials in responses or logs. Reject the platform account and platform-owned subaccounts. Account/trunk identity cannot change during pending replacement; secret refresh for the same identity is supported. Provider credentials and verified trunk linkage are required before enabling replacement, which remains off by default. Replacement keeps the country/known US state and number type; purchase and release occur exclusively in that customer account. Recovery/cancellation must use that same account. Never store a customer-purchased number as platform-hosted. Pools remain on Settings > Phone Numbers and remain assigned to agents; sequences still select the agent. Hosted numbers remain visible/manageable through their existing UI but are not eligible for pools. Responsibility acknowledgment explains customer operation, applicable calling rules, charges and released-number consequences without claiming guaranteed compliance or zero platform liability.