Preparing WhatsApp delivery for your clients

3 min read

A receipt belongs in email. An opted-in appointment reminder may also belong on WhatsApp. The useful question is whether the customer expects that message from that business, and whether you can tell what happened after sending it.

SagePigeon’s email API and form integrations are available today. WhatsApp is in setup preview. The API and connection flow are implemented, but production delivery needs Meta approval, a registered sender and enabled onboarding. Creating a workspace does not activate WhatsApp.

The number belongs to the client

Each client connects its own WhatsApp Business Account and sender. Its credentials, message records and opt-out list stay within that client’s scope. The business identity is the one configured for that sender; using SagePigeon does not turn every client’s messages into SagePigeon messages.

An administrator starts the connection from the client’s settings when onboarding is enabled. This flow supports standard Cloud API numbers. Keeping the same number active in the WhatsApp Business app through coexistence is not supported by this implementation.

Prepare these before a first send

  • A Business Account and sender eligible for the configured Meta onboarding flow.
  • An approved template with the exact parameter count your application will send. Customer connections currently import text body templates, without media, headers or buttons.
  • The recipient’s number including country code and a record of their consent to receive WhatsApp messages from that business.
  • A server-side API key with writes, scoped to the intended client.

A phone number collected for an email receipt is not by itself consent to WhatsApp. The API requires consentAt; your application supplies the real time consent was recorded. It should not substitute the current time for a missing consent record.

Send once, then follow the status

This is an illustrative request, not a ready-to-send template. Replace every placeholder with your own enabled client and approved template, and use only a consenting recipient.

JSON
{
  "clientId": "YOUR_CLIENT_ID",
  "to": "+12025550123",
  "template": "approved_reminder",
  "parameters": ["Jo", "Friday at 10:00"],
  "idempotencyKey": "reminder-booking-8812",
  "consentAt": "2026-11-18T09:00:00.000Z"
}

Send it to POST /api/v1/whatsapp/messages with your key in x-api-key. Keep the returned messageId. Query GET /api/v1/whatsapp/messages/{messageId}?clientId=YOUR_CLIENT_ID to read later status updates.

A 202 response does not mean the message arrived. Signed provider callbacks can move the record through sent, delivered and read, or report a failure. A timeout can leave it unknown even if the provider accepted it. Reuse the same idempotency key and identical payload; creating a new key may send a duplicate. There is no automatic retry queue.

Decide how email fits

SagePigeon does not automatically convert a failed WhatsApp send into email. Keep essential email in your existing workflow and decide explicitly when another channel is appropriate. Use a separate email idempotency key for the same business event so a retry does not produce another receipt.

The email template guide explains versioned templates, sender identity and delivery records. WhatsApp currently has status lookup through its API; it does not have a shared conversation inbox.

Allow for separate usage and opt-outs

WhatsApp usage is separate from the email and form allowances on the pricing page. A configured daily sending cap can refuse a send with 429; an unavailable sender returns 503. A recipient who replies STOP, UNSUBSCRIBE, CANCEL, END or QUIT is suppressed for that client. Your application must respect this refusal rather than switching keys or senders to bypass it.

Start with the delivery path you can use today.

Create a workspace for forms, add email on Pro or Scale, and review the WhatsApp setup reference before planning production messaging.