Infrastructure for the number your business already has.
Cosend exists because the choice between “keep the app” and “get an API” was always a false one. Coexistence ended it. We build everything that should have come after.
Why this exists
For years, putting a WhatsApp number on an API meant taking it off the phone. Every business with a counter, a workshop or a delivery team had the same answer to that, and it was no — because the number is not an integration detail, it is where the customers are, and the person answering it is holding it.
Coexistence changed the constraint: one number can now serve the WhatsApp Business app and the Cloud API at the same time. What it did not change is that everything built on top of the API still assumes the number moved. So the tooling either treats the phone as a problem, or ignores it and gets the conversation wrong.
Cosend is built the other way round. The phone is the primary surface and the API is additive. When someone on the team answers from the app, the inbox knows, the automation that was about to follow up cancels itself, and the history is one thread rather than two.
Principles
Four, and each one is a decision that cost something rather than a value that cost nothing.
Never hide the payload
Plain language on the surface and the raw truth one click under it. Every run is inspectable down to the payload, every error carries a request ID, and the coverage table says which paths we refuse and why. A product that only shows you the summary is a product that has decided what you are allowed to debug.
No lock-in, structurally
Your WhatsApp Business Account, your number, your templates. Direct-delivery mode means you can use us and have us store nothing. Disconnecting happens in the WhatsApp Business app’s own settings — Meta’s screen, not a retention flow of ours — and the app keeps working afterwards.
No markup on messages
Meta bills your account directly, at Meta’s rates, and we never see it. That is a pricing decision with a consequence we like: our incentive is the platform being worth paying for, rather than your volume going up.
Boring reliability
Infrastructure earns trust by being dull. Hairline borders, exact numbers, an availability target we can hit rather than one that looks good, and an alert before a failure rather than an apology after one.
The short version
True North Tech Group LLC is registered in Wyoming, USA. The product runs on Meta's official Cloud API, with the database and the API both in Frankfurt. We think the WhatsApp number a business has had for years is an asset, and not something a vendor should get to hold.
We are small and pre-launch, and this page will say so until it does not. There are no customer logos on this site, no case studies and no testimonials, because there are no customers yet — and a launch site that claims social proof it does not have is a lie the first customer can check.
[email protected] reaches a person. Security · Sub-processors · Changelog