Sending SMS between virtual numbers
Sending SMS from one virtual number (e.g., Long Virtual Numbers, 10DLC, or short codes) to another virtual number is not universally supported across the telecommunications ecosystem. Because delivery depends entirely on downstream mobile carriers and third-party service providers, we cannot guarantee delivery for virtual-to-virtual SMS traffic.
Why does this happen?
Most mobile network operators and carriers route SMS traffic through specialized pathways designed either for P2P (Person-to-Person) or A2P (Application-to-Person) communication.
Carrier Filtering & Blocks: To combat spam and fraud, many carriers employ strict screening filters. Messages originating from a virtual number sent directly to another virtual number are often flagged as suspicious and blocked at the carrier level.
Regulatory Restrictions: Many regions globally have strict regulatory registrations that prohibit or limit certain types of numeric sender IDs and routing paths (e.g., restrictions on virtual numbers acting as standard mobile endpoints).
Best practices & recommendations
If your workflow relies on two-way virtual messaging, please keep these recommendations in mind to optimize your deliverability:
Use Physical Mobile Devices for Testing: When testing your virtual numbers, always send messages to a standard, physical mobile phone number instead of another virtual number.
Embed Opt-In and Contact Info: Since carriers strictly monitor sender identity, ensure your message content clearly identifies your organization and respects local carrier rules.
Rotate Sender IDs Wisely: Avoid sending highly repetitive templates from a single long code to prevent triggering aggressive carrier spam blocks.