💬 Shared WhatsApp Inbox on the new PlatformMore
1msg official logo

Account re-verification notice via WhatsApp API

The scenario sends the account holder a personalised WhatsApp template when a periodic account recheck is scheduled or starts.

Use case overview

The scenario sends the account holder a personalised WhatsApp template when a periodic account recheck is scheduled or starts. The message includes the customer name, account or process context, and the required next step or deadline. A static URL button opens the verification portal or account review page.

Template example

Hello, {{1}}! Your {{2}} is scheduled for a periodic account recheck. Next step: {{3}} If you have questions — we are here to help.

Complete review
  • {{1}}
    customer name
  • {{2}}
    account or process context (e.g. merchant account, partner profile, business wallet)
  • {{3}}
    next step or deadline (e.g. confirm business details in the portal by April 30)
  • “Complete review”
    button — fixed in the Meta template
WhatsApp Business API for account recheck notification

When to use it

Reach for this scenario when compliance or account management schedules a periodic re-verification — KYC refresh, merchant review, or partner account audit — and the account holder still has no open WhatsApp chat, so only an approved template can warn them before access is restricted. It fits fintech and marketplaces with recurring merchant checks, B2B SaaS teams notifying admins about scheduled account reviews, and integrators wiring recheck schedules from CRM, risk engines, or onboarding platforms via webhook.

Fewer surprise account lockouts
Three body variables carry the customer name, account or process context, and the required next step or deadline into WhatsApp, so the recheck notice lands before access is restricted instead of after a failed login or support escalation.
Recheck without a back-and-forth
The static URL button opens the verification portal fixed in the Meta template, so the account holder can complete the review without replying in WhatsApp.
No manual outreach at scale
Compliance or account management fires the template when it schedules a periodic recheck and resolves phone and account fields automatically — nobody retypes recheck warnings across merchant or partner accounts.
Reach holders without an open chat
An approved template is the only first message allowed when there is no open conversation, so the recheck warning can still go out before the review window closes.
Compliance and CRM follow-up
Delivery result is logged after send, so compliance or CRM can track who received the recheck notice before access changes.

Workflow

  1. Trigger

    Compliance or account management schedules a periodic account recheck and fires an event.

    event · triggered

  2. Capture event

    The system resolves the account holder phone number and recheck fields.

    phone: "+…"

  3. Build & send

    A personalised template message is built with three body variables and a static URL button.

    POST /sendTemplate

  4. Delivered

    The account holder receives the WhatsApp notification with recheck context and next step.

    delivered

  5. Status tracked

    Delivery result is logged for compliance or CRM follow-up.

    status: "read"

WhatsApp Business API for account recheck notification

Technical implementation

Prerequisites

  1. 1MSG API Key · How to get API Key
  2. WhatsApp Business account · How to Connect WABA
  3. WhatsApp Template · How to Approve WABA Template
  4. Customer opt-in · How to Manage Customers Consent

Code examples

#!/usr/bin/env bash
set -euo pipefail

# === Configuration (replace "___" placeholders) ===

API_BASE_URL="https://api.1msg.io"        # production 1MSG API base URL
CHANNEL_ID="___"                           # channel ID from 1MSG dashboard
API_TOKEN="___"                            # channel JWT token (Bearer)

TEMPLATE_NAME="___"                        # approved template name
TEMPLATE_NAMESPACE="___"                   # template namespace (required — send fails without it)
TEMPLATE_LANGUAGE="___"                    # template language code, e.g. "en"



# === Test data ===
TEST_PHONE="___"                 # client phone in international format
TEST_CUSTOMERNAME="___"         # {{1}} customer name
TEST_PROCESS="___"         # {{2}} process name
TEST_NEXTSTEP="___"         # {{3}} next step

PHONE_NORM="$(printf '%s' "$TEST_PHONE" | tr -cd '0-9')"

for pair in "CHANNEL_ID=$CHANNEL_ID" "API_TOKEN=$API_TOKEN" \
            "TEMPLATE_NAME=$TEMPLATE_NAME" "TEMPLATE_NAMESPACE=$TEMPLATE_NAMESPACE" \
            "TEMPLATE_LANGUAGE=$TEMPLATE_LANGUAGE" "TEST_PHONE=$TEST_PHONE" \
            "TEST_CUSTOMERNAME=$TEST_CUSTOMERNAME" \
            "TEST_PROCESS=$TEST_PROCESS" \
            "TEST_NEXTSTEP=$TEST_NEXTSTEP"; do
    val="${pair#*=}"
    if [ -z "$val" ] || [ "$val" = "___" ]; then
        echo "Missing configuration value: ${pair%%=*}" >&2
        exit 1
    fi
done

if [ -z "$PHONE_NORM" ]; then
    echo "Error: phone number has no digits after normalization" >&2
    exit 1
fi

URL="${API_BASE_URL%/}/${CHANNEL_ID}/sendTemplate"

# params carries body ONLY. Button text is fixed in the Meta template — no button param.

# {{1}} customer name → ${TEST_CUSTOMERNAME}
# {{2}} process name → ${TEST_PROCESS}
# {{3}} next step → ${TEST_NEXTSTEP}
read -r -d '' PAYLOAD <<JSON || true
{
  "phone": "${PHONE_NORM}",
  "template": "${TEMPLATE_NAME}",
  "namespace": "${TEMPLATE_NAMESPACE}",
  "language": { "policy": "deterministic", "code": "${TEMPLATE_LANGUAGE}" },
  "params": [
    {
      "type": "body",
      "parameters": [
        { "type": "text", "text": "${TEST_CUSTOMERNAME}" },
        { "type": "text", "text": "${TEST_PROCESS}" },
        { "type": "text", "text": "${TEST_NEXTSTEP}" }
      ]
    }

  ]
}
JSON

RESPONSE="$(curl -s -w '\n%{http_code}' -X POST "$URL" \
    -H "Content-Type: application/json" \
    -H "Authorization: Bearer ${API_TOKEN}" \
    -d "$PAYLOAD")"

HTTP_CODE="$(printf '%s' "$RESPONSE" | tail -n1)"
BODY="$(printf '%s' "$RESPONSE" | sed '$d')"

case "$BODY" in
    *'"sent":true'*) ok=1 ;;
    *) ok=0 ;;
esac

if [ "$HTTP_CODE" -ge 200 ] && [ "$HTTP_CODE" -lt 300 ] && [ "$ok" -eq 1 ]; then
    echo "Message sent to client."
    echo "API response: $BODY"
else
    echo "Send failed. HTTP status: $HTTP_CODE" >&2
    echo "$BODY" >&2
    exit 1
fi

Response and delivery status

HTTP 2xx and JSON "sent": true mean 1MSG accepted the message for sending — not that it already reached the customer's phone. Save the id field (looks like wamid.…) to correlate delivery callbacks.

200 OKResponse
{
  "sent": true,
  "message": "Sent to [email protected]",
  "description": "Message has been sent to the provider",
  "id": "wamid.HBgLMzgwNjM5..."
}
  • sent

    Accepted for sending — not yet on the customer's phone

  • id

    Store it; delivery callbacks and hookInfo are keyed on this

Delivery statuses and webhooks →

Common errors

StatusAPI responseCauseFix
200Message was not sent: template is not definednamespace, template or language is missing from the request body.Send all three. Take namespace and the exact template name from GET /templates; language is an object: {"policy": "deterministic", "code": "en"}.
200template name (…) does not exist in <language>The template is approved in a different language than the one requested.Use the exact language code the template was approved in (for example es_MX is not the same as es). Check it in GET /templates.
200Message was not sent: provide chatId, phone, bsuid, or usernameNo recipient the channel could resolve.Pass exactly one recipient: phone (country code plus number, digits only), chatId (for example [email protected]) or bsuid.

All error codes →

Common questions

Related

Build for WhatsApp in hours
without infrastructure hassle