What Meta provides and what a platform adds.
Meta provides the Cloud API, business assets, senders, templates, webhooks, media, quality state, and messaging policy. Waaru provides the current product interface for contacts, templates, deterministic workflows, broadcasts, and a shared inbox. It does not replace Meta's rules or account decisions.
How onboarding works.
An eligible business connects or creates its Meta business assets and WhatsApp Business Account, registers a sender, grants permissions, configures webhooks, and tests inbound and outbound traffic. Business verification, display-name review, template approval, and production limits are separate states and can affect timing.
How message pricing should be budgeted.
Separate Meta's delivered template-message charges from the software platform cost. Rates depend on category and recipient country. Capture Meta's current downloadable rate card and the provider's written terms on the same date. Waaru is free during the current MVP and keeps Meta message charges separate from the platform fee.
What the current deterministic workflow layer does.
The V2 Logic Flow contract registers 27 node types and supports versioned publishing with limits of 200 nodes and 400 edges. A workflow can send structured messages, collect replies, branch, wait, call approved interfaces, use WhatsApp Flow forms, and hand a conversation to a person. It is not an AI agent.
How to evaluate migration.
Confirm ownership and state for the Meta business portfolio, WABA, sender, templates, contacts, consent evidence, chat exports, quality, and provider permissions. Build a rollback and validation checklist before changing production webhooks or traffic.
What not to automate blindly.
Do not guess consent, widen opt-out scope, send outside an eligible service window, ignore quality state, or use an unverified connector for a payment or booking decision. Where state is unsafe or unknown, the current product is designed to fail closed.