SMS works because people trust it. When a message arrives from a number they recognise, or from a business they have a relationship with, they read it. That trust has been built over decades, and it is not ours to squander. Building a product that makes SMS programmatic comes with a responsibility to ensure it is not turned into a spam vector.
Relayion is built for legitimate business communication. Appointment reminders, order updates, two-factor authentication, staff alerts. It is explicitly not a bulk messaging tool, a cold outreach platform, or a channel for unsolicited promotional messages. We enforce that distinction, not just state it.
What we look for
Abuse on SMS infrastructure tends to follow recognisable patterns. High outbound volume to numbers with no prior relationship. Sudden spikes from newly created accounts. Messages that contain patterns common in phishing and scam content. Accounts sending to large lists of unrelated recipients with no inbound replies. These patterns are detectable, and our systems monitor for them.
Accounts that trigger abuse signals are reviewed and, where the evidence is clear, deactivated. We do not wait for carriers to flag the problem. By the time a carrier has sufficient data to act, real people have already received harmful messages. Our goal is to intervene before that happens.
Why this matters for everyone on the platform
Relayion routes messages through Android devices with real consumer SIM cards. That is the architectural decision that makes the product distinctive. Messages originate from real numbers, not shared short codes. Carriers treat them accordingly. That advantage disappears if the platform develops a reputation for enabling abuse, because carriers respond to abuse by blocking or throttling traffic from known sources. One bad actor hurts every legitimate sender on the platform.
This is not only a values question. It is a product quality question. Keeping the platform clean is how we protect deliverability for the customers using it legitimately.
Our expectations of customers
Customers are responsible for ensuring their messaging complies with applicable laws and carrier policies in their jurisdiction. In the Philippines, that includes the Data Privacy Act and any relevant NTC guidelines. Internationally, it includes regulations like the TCPA in the United States and GDPR in Europe if messages reach recipients in those regions.
If you are unsure whether a specific use case is acceptable, reach us at hello@relayion.com before you build. We would rather answer a question early than deactivate an account after the fact.