The CPaaS Company
Insights
Independent, source-cited writing on cloud communications — original research alongside the best work published elsewhere.
8 pieces
Consent is a data model, not a checkbox
A boolean cannot answer the question a regulator asks, and cannot answer the question your own send path needs answered either.
10DLC registration without tears
US carriers block unregistered A2P traffic outright. The process is two layers, it takes longer than your launch date assumes, and most rejections are avoidable.
Getting messages into the Gulf: sender IDs, licensed aggregators and the AD- prefix
Regional A2P delivery is a licensing question before it is a technical one, and a global platform does not inherit local standing.
Telling people they are talking to a machine
From 2 August 2026 this is a legal requirement in the EU, with specific rules about how it must be presented. It is also, independently, the thing that makes automated support tolerable.
A consent architecture that survives an audit and a vendor migration
A schema, a set of invariants, and the three queries every send path and every regulator eventually asks.
The gap nobody fills: service-to-service identity
Every platform in this category issues credentials to humans and to applications. Almost none can express 'system A is acting on behalf of customer B, with these permissions, until this moment'.
The real cost of an unofficial transport
Unofficial protocol implementations are cheaper, faster to launch and genuinely useful. They also transfer a risk to your customers that you should be pricing.
Article 50 for messaging teams: what the AI Act's transparency rules require
A reading of the transparency obligations that took effect on 2 August 2026, focused specifically on automated conversations rather than AI in general.