Automate WhatsApp without putting the number at risk.
Tools that hitch a ride on the phone app work until Meta catches them. This is the door Meta opens for this.
Conext goes in through Meta’s official API. WhatsApp, Instagram, and Messenger use that door. The number is yours: if you leave one day, you take it with you.
Your number, your Meta account.
WhatsApp Business is linked to your own account. The number is yours: if you leave one day, you take it with you. No cloned session, no phone left in a drawer on a charger.
A number on the API cannot also be in the WhatsApp app on a phone. If you handle it by hand today and you are not ready to cut that yet, you start with a spare number and move the main one when you are comfortable.
Meta signs. The CRM does not improvise.
The webhook is signed by Meta. If the payload is not one of our numbers, it is dropped. The CRM answers 200 immediately and processes after: if it were slow, Meta would retry and the same message would duplicate. The message id stops it from being processed twice.
All three Meta channels come in today: WhatsApp text, Instagram, and Messenger. Outbound WhatsApp attachments upload to Graph and then send; the copy that stays in the thread is ours, because Meta deletes theirs after 30 days. Inbound customer media is not downloaded yet.
In practice
- 1
You connect the number
Meta account, token, phone_number_id. It is stored encrypted in your space, not in a shared env file.
- 2
Events arrive
Meta signs, the CRM resolves the business by the number, and the pipeline runs.
- 3
Replies go out
Text or media through Graph. Without credentials, development simulates; production does not pretend.
Meta charges for conversations on your Meta account, at their rate. Conext does not add a markup. What you pay here is the software.
Want to see it with your own threads?
Essential includes one channel, 500 AI conversations per month, and one active agent.