Confirm scope
Choose one agency template and record unsupported asks as decisions. Start with order updates, appointments, lead handoff, CRM sync, campaign replies, or support escalation.
Choose a templateTutorial path
Build the first client workflow in the right order.
Use this sequence when onboarding an agency project. It keeps the build small, auditable, and inside the current EZWhatsApp contract.
Recommended sequence
Create auth
Log in as owner/admin, create or rotate the line API token, and store it in the deployment secret manager.
Read auth docsVerify line health
Call /api/v1/health?wakeup=false. Do not send until lifecycle, effective send state, and sendable status make sense.
Send one idempotent message
Send a single test message with a deterministic idempotency key. Retry the same request and verify it does not duplicate the customer message.
Use exampleWire webhooks
Configure the webhook target, store delivery ids, and process inbound messages without moving source-of-truth ownership out of EZWhatsApp.
Read webhook guideHandoff to client
Show the client where replies appear, how team members claim or assign work, and what evidence proves the workflow is live.
Use checklistDo not start with these assumptions
Do not build against old `/messages` examples.
Current Channel API sends use /api/v1/messages/text and /api/v1/messages/media.
Do not treat campaigns as generic loops.
Campaigns belong to the scoped customer-admin campaign surface and need explicit product decisions for policy gaps.
Do not replace the workspace with CRM state.
External systems can sync context. EZWhatsApp remains the operational inbox and source of conversation truth.
Do not promise official WABA behavior.
EZWhatsApp is a linked-device workspace, not an official WhatsApp Business Platform product.