SMS Route Rules and Acceptable Use
Understand Robo SMS sender identities, permitted route usage, responsible recipient handling and support for messaging-policy questions.
Use the route approved for your account
Pre-approved masks are marketing-only. Non-OTP transactional notifications require your own approved brand mask. OTP verification messages use Short Code only. Do not bypass these distinctions by changing a sender value in an API request.
Responsible recipient handling
Send marketing only to recipients who agreed to receive it. Do not use purchased, scraped or unconsented lists. Maintain permission records and a working opt-out process, and remove opted-out recipients from future marketing campaigns.
Prohibited content
Do not send fraudulent, deceptive, abusive or unlawful messages, impersonate another business, or distribute phishing links. Do not request passwords or complete payment credentials by SMS. Use sender identities you are authorized to use.
Message classification
Keep promotions separate from service notifications. Do not send OTPs on a masked route, marketing through Short Code or transactional alerts through a pre-approved marketing mask. Contact support if a message has mixed purposes.
Account and data protection
Protect login details and API credentials. Limit access to recipient lists and message records. Keep private credentials out of frontend code, shared screenshots and public logs.
Questions and complaints
Contact [email protected] with the affected message reference, timestamp and a description of the issue. Never include passwords or API keys. Read the Terms of Service, Privacy Policy and Refund Policy for the separate service and billing terms.