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

Offer deadline reminder via WhatsApp API

The scenario sends a personalised WhatsApp marketing template as the second touch of a promotion that is already running and about to close.

Use case overview

The scenario sends a personalised WhatsApp marketing template as the second touch of a promotion that is already running and about to close. The message includes the customer name, the offer they were already told about, the closing deadline, and a last-chance urgency line. A static URL button opens the same offer landing page from the first broadcast.

Template example

Hello {{1}}! A quick reminder: the offer on {{2}} ends {{3}}. {{4}} Tap the button below to claim it before time runs out.

Claim before deadline
  • {{1}}
    customer name
  • {{2}}
    promotion or product the contact was already told about in the first broadcast
  • {{3}}
    offer closing deadline (date or time)
  • {{4}}
    last-chance urgency line (e.g. hours left, final reminder)
  • “Claim before deadline”
    button — fixed in the Meta template
WhatsApp Business API for limited-time offer deadline reminder

When to use it

Use this scenario when a limited-time promotion is already live, contacts received the first announcement, and the closing deadline is approaching but many have not converted — not when you are launching the offer for the first time. It fits flash-sale final-hour nudges, SaaS upgrade windows about to expire, and agencies running a second touch to non-responders from an earlier promo broadcast. It is not for cold outreach, generic seasonal launches, or utility payment or action reminders unrelated to a marketing deadline.

Convert contacts who already saw the offer
The reminder targets non-converters from the first broadcast, so the send goes to people who already know the promotion instead of reopening a cold marketing push.
Deadline framing that creates urgency
Four body variables carry the contact name, the offer they were told about, the closing deadline, and a last-chance line, so the message reads as a time-sensitive follow-up rather than a repeat announcement.
One tap back to the same offer page
A static URL button fixed in the Meta template reopens the promotion landing page, so the contact can act before the window closes without waiting inside the 24-hour reply window.
Less manual last-chance follow-up
CRM flags non-converters as the deadline nears and the template goes out on that trigger — no rep rebuilds the list or retypes urgency copy for each contact.
Final-hour conversion tracking
Delivery results are logged for the reminder cohort, so marketing can compare last-chance sends against conversions before the promotion closes.

Workflow

  1. Trigger

    CRM or marketing automation flags non-converters from the first promotional broadcast as the deadline nears.

    event · triggered

  2. Capture event

    The system resolves phone numbers and deadline personalisation fields for each contact.

    phone: "+…"

  3. Build & send

    A personalised deadline reminder template is built with four body variables and a static URL button.

    POST /sendTemplate

  4. Delivered

    Each targeted contact receives the WhatsApp last-chance reminder message.

    delivered

  5. Status tracked

    Delivery results are logged for final-hour campaign conversion tracking.

    status: "read"

WhatsApp Business API for limited-time offer deadline reminder

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_PRODUCTORSERVICENAME="___"         # {{2}} product or service name
TEST_DATE="___"         # {{3}} date or time
TEST_ADDITIONALINFO="___"         # {{4}} additional info

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_PRODUCTORSERVICENAME=$TEST_PRODUCTORSERVICENAME" \
            "TEST_DATE=$TEST_DATE" \
            "TEST_ADDITIONALINFO=$TEST_ADDITIONALINFO"; 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}} product or service name → ${TEST_PRODUCTORSERVICENAME}
# {{3}} date or time → ${TEST_DATE}
# {{4}} additional info → ${TEST_ADDITIONALINFO}
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_PRODUCTORSERVICENAME}" },
        { "type": "text", "text": "${TEST_DATE}" },
        { "type": "text", "text": "${TEST_ADDITIONALINFO}" }
      ]
    }

  ]
}
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

Marketing Campaigns
Post-visit follow-up offer via WhatsApp API
The scenario sends a personalised WhatsApp marketing template shortly after an in-person visit, showroom trip, consultation, or phone contact.
Marketing Campaigns
Product launch announcement via WhatsApp API
The scenario sends a personalised WhatsApp marketing template when a single named product, service line, tariff, or feature goes live.
Marketing Campaigns
Personal product picks via WhatsApp API template
The scenario sends a personalised WhatsApp marketing template when a recommendation engine or merchandiser prepares a curated selection of several items for a contact.
Marketing Campaigns
Segmented personal offers via WhatsApp API
The scenario sends a personalised WhatsApp marketing template when CRM splits an opted-in base into audience segments and assigns tailored offer terms to each.
Marketing Campaigns
Send content (guides, articles) via WhatsApp API
The scenario sends a personalised WhatsApp marketing template when the business publishes educational or entertaining content for opted-in contacts.
Marketing Campaigns
Company news broadcast via WhatsApp API template
The scenario sends a personalised WhatsApp template when the business publishes company or service news.
Marketing Campaigns
Post-purchase upsell message via WhatsApp API
The scenario sends a personalised WhatsApp marketing template shortly after a completed purchase when a follow-up offer is relevant — a refill, companion product, or the next service in the cycle.
Marketing Campaigns
Win-back message for inactive customers (API)
The scenario sends a personalised WhatsApp marketing template to an existing customer who bought or used the service before but has been inactive for months.

Build for WhatsApp in hours
without infrastructure hassle