AWS sms-voice: Add phone pool guidance for delivery resilience
Summary
Adds a paragraph to the best practices page explaining how to use phone pools with multiple origination identities, automatic rerouting away from identities with delivery failures, and including mixed number types (e.g., short code plus toll-free) for broader coverage.
Security assessment
This change is about availability/delivery resilience and failover routing between origination identities; it documents no authentication, encryption, authorization, credential, or exposure controls, so it has no direct security impact.
Evidence
+You can further improve delivery resilience by configuring phone pools that contain multiple origination identities. The service monitors delivery receipts (DLRs) for each identity in a pool and automatically routes messages away from identities that are experiencing delivery failures.
Diff
diff --git a/sms-voice/latest/userguide/best-practices.md b/sms-voice/latest/userguide/best-practices.md index 9c2ce9f23..8ffddc37a 100644 --- a//sms-voice/latest/userguide/best-practices.md +++ b//sms-voice/latest/userguide/best-practices.md @@ -422,0 +423,2 @@ In some countries, you can also use multiple types of phone numbers for added re +You can further improve delivery resilience by configuring phone pools that contain multiple origination identities. The service monitors delivery receipts (DLRs) for each identity in a pool and automatically routes messages away from identities that are experiencing delivery failures. When the affected identity recovers, normal routing resumes without manual intervention. For the broadest coverage, include different number types in the same pool, such as a short code and a toll-free number. For more information about phone pools, see [Phone pools in AWS End User Messaging SMS](./phone-pool.html). +