Channel · We run it ourselves
Meta's official programmatic channel for businesses on WhatsApp, rated by how many conversations a number may start per day.
In this market WhatsApp is not a channel alongside email. It is where business is transacted, and the difference between an official integration and a bridge is whether the number survives its own success.
01
Sending capacity is a quality rating, not a purchase. The tiers run 250, 1,000, 10,000, 100,000 and unlimited business-initiated conversations in a rolling day, and a number climbs them by how recipients respond rather than by what the account pays.
02
An unofficial bridge works until it does not, and the failure mode is losing the number that the customer base has saved. Where a client already runs one we say plainly what it is risking.
03
We keep a low-level implementation as well, because some jobs — internal tooling, a migration, a channel a vendor will not provision — genuinely fall outside the official API. Holding both means the recommendation is not shaped by the only tool we have.
An entry that cannot point at something you can open, run or read does not compile. That is a property of the type, not a promise in a paragraph.
Invariant
Meta rates the number, and the rating falls on blocks and silence regardless of who caused them. A purchased contact list will cost a client the number, which in the UAE is also a TDRA consent violation before it is a deliverability problem — so a list nobody opted into is work we decline rather than price.