Send what arrives, on every channel.

A field reference for each communications channel WebSMSpanel runs — the regulatory regimes, sender rules, encoding gotchas, and provisioning timelines that decide whether a message or call gets through.

SMS Guidelines

SMS looks simple — type a message, hit send — but the rules underneath it are anything but. Every text crosses a chain of regulators, carriers, and consent frameworks that quietly decide whether it arrives, gets filtered, or earns you a fine. The guidelines on this page summarise what every team sending application-to-person (A2P) SMS through WebSMSpanel should know: how senders are identified, how messages are encoded, what content carriers reject, how to register in regulated markets, and how to honour opt-outs the way the law expects you to.

Voice Guidelines

A voice call still feels like the simplest thing on the network — pick up the phone, talk to someone — but underneath the surface, every A2P call passes through a stack of regulators, carrier filters, call-authentication frameworks, and consent rules that decide whether it rings, whether it is labelled as "Spam Likely", or whether it is silently dropped.