A2P is a process, not a sending channel
A2P stands for application-to-person: a system sends messages to people automatically. Think of one-time login codes, appointment reminders from medical practices, delivery notifications, service outage alerts to customers, or alerting emergency staff. Such messages are rarely marketing. They are part of a business process, and if they do not arrive, the process stops.
That is why choosing a platform is about more than comparing the price per SMS. What matters is whether delivery, traceability, data protection and operations fit together, especially in banking, insurance, healthcare, public administration or logistics.
Start your selection with the message flow, not with the product catalogue.
The must-have criteria
| Criterion | Why it matters | What to ask |
|---|---|---|
| Data location and security | Phone numbers and content are personal data | Where is data stored and processed? Which certifications, such as ISO/IEC 27001, are in place? |
| Channels | Not every audience is best reached by SMS | Which channels run through the same platform, for example SMS, WhatsApp Business, email, voice or push? |
| Availability | Critical messages must go out even at peak load | What availability is guaranteed in the contract? Are there redundant connections to the mobile networks? |
| Integration | IT must connect existing systems | Which APIs and interfaces exist? Is there a portal business teams can use without coding? |
| Traceability | Audits and complaints require evidence | Are there delivery reports, logs and export options? How long are they kept? |
| Support | Outages cannot wait until Monday | Who is reachable when, in which language and with what response times? |
The lowest sending price is rarely the cheapest solution. It gets expensive when delivery monitoring, compliance evidence or support have to be built later, or when nobody competent responds during an outage.
The legal framework in Switzerland
The revised Federal Act on Data Protection (nFADP, nDSG in German) has applied since 1 September 2023. When you commission a platform to send messages, this is usually processing on your behalf. You remain responsible and need a contract covering security, sub-processors and deletion. If data is transferred abroad, the destination must offer adequate protection or additional safeguards are required.
For promotional messages, the Unfair Competition Act (UWG) also applies: mass advertising by SMS or email generally requires prior consent, the sender must be identifiable and opting out must be easy. Supervised institutions such as banks and insurers must also follow FINMA’s outsourcing requirements, and healthcare providers are bound by professional secrecy.
Note
This overview is not legal advice. Have your data flows and contracts reviewed by your data protection officer or a specialist before rollout.
Selection in five steps
- Sharpen the use cases: one-time codes, reminders, alerts, service messages and campaigns have different needs in terms of speed, channel and consent.
- Set the must-haves: define data location, certifications, availability and support model before you request quotes.
- Check channels and integrations: decide whether SMS is enough or whether, for example, WhatsApp Business is needed, where message templates must be approved by the channel operator.
- Test operations: a pilot with real messages reveals delivery rates, latency and monitoring, ideally under load as well.
- Settle governance: define roles, approvals, sender IDs, logs and escalation paths before rollout.
Many projects fail on the assumption that one channel fits every case. A one-time code works reliably by SMS, while a detailed service conversation is better suited to a messenger or email. A platform that runs several channels from a single operation reduces later compromises.
Build it yourself or use a specialised platform?
| Question | Build in-house | Specialised platform |
|---|---|---|
| Compliance and operations | High internal effort for security, availability and evidence | Evidence and certifications ideally already exist and can be verified |
| Channels | Often SMS only at first, other channels costly to add | Several channels through one interface |
| Scaling | Load tests, monitoring and failure scenarios built yourself | Experience with high volumes, but secure it contractually |
| Dependency | Full control, but know-how concentrated in few people | Vendor dependency, so agree on exit and data export |
Building in-house can make sense if messaging is core to your product and you are prepared to run security, scaling and support as a product of its own. For most companies, a specialised provider is the more robust route. Typical mistakes are separating technology from operations, missing delivery monitoring, and compliance documentation that is only found lacking during an audit. Several providers offer such platforms in Switzerland, among them F24 Schweiz AG with eCall, which according to the provider uses Swiss data centres. Obtain at least two or three quotes and compare them against your must-have criteria.
Frequently asked questions
How can I tell whether a platform is suitable for regulated data?
Is SMS still enough for A2P today?
How important are volume tests before go-live?
Is a Swiss platform mandatory?
Do service texts require consent?
If you check availability, security and scaling first and discuss unit prices only afterwards, you end up with A2P communication that holds up in daily operations.