Phone Routing Rules are particularly useful in scenarios where you need to bypass operator-specific restrictions or optimize message delivery. Here are some common use cases:
Operator Blocks Specific Numbers:
- If an operator (e.g., Operator A) blocks a specific phone number (e.g.,
9199999xxxxx) but another operator (e.g., Operator B) allows it, you can use a Phone Routing Rule to redirect messages for that number to Operator B. - Example: Operator A blocks
9199999xxxxxdue to DND settings, but Operator B supports delivery to DND numbers. Set Operator A as the Origin Vendor and Operator B as the New Vendor.
Optimizing Delivery Rates:
- If one vendor has better delivery success rates for a specific phone number or region, you can route messages to that vendor to improve reliability.
- Example: Operator B has a 98% delivery rate for numbers in India, while Operator A has only 85%. Route Indian numbers like
9199999xxxxxto Operator B for better performance.
User-Specific Routing Needs:
- Apply rules to a specific user if their messaging campaigns require unique routing logic, while leaving other users unaffected.
- Example: A user sending promotional messages to
9199999xxxxxneeds to use Operator B due to compliance requirements; set the rule for that user only.
Best Practices:
- Monitor delivery reports in your SMPPCenter dashboard to identify numbers frequently blocked by certain operators, then create rules to redirect those messages.
- Regularly review and update your Phone Routing Rules to adapt to changing operator policies or delivery performance.
Phone Routing Rules ensure your messages reach their destination, even in challenging scenarios. For assistance, contact our support team.