Team Inbox APIMore
1msg official logo

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.

Use case overview

The scenario sends a personalised WhatsApp marketing template shortly after an in-person visit, showroom trip, consultation, or phone contact. The message thanks the client, references the company or specialist they met, the service discussed, and the recommended next step. A static URL button opens the offer or booking page.

Template example

Hello, {{1}}! Thank you for visiting {{2}} — it was great to speak with you about {{3}}. {{4}} Tap the button below to take your next step with us.

Take next step
  • {{1}}
    customer name
  • {{2}}
    company or specialist the client met during the visit
  • {{3}}
    service or topic discussed during the visit or contact
  • {{4}}
    recommended next step or marketing offer (repeat visit, membership, booked service)
  • “Take next step”
    button — fixed in the Meta template
WhatsApp Business API for post-visit marketing message

When to use it

Use this scenario when a client completes an in-person visit, showroom tour, consultation, or phone contact and the business wants a warm marketing follow-up on WhatsApp — not a utility reminder and not a survey — that thanks them and offers the natural next step such as a repeat visit, membership, or the service discussed. It fits clinics and salons offering post-appointment packages, showrooms and studios following up after a tour, car service centers nudging booked maintenance, and agencies wiring post-visit triggers from booking systems or CRM into WhatsApp marketing flows.

Convert visits while interest is still warm
The post-visit trigger fires shortly after the appointment or contact is logged, so the marketing message reaches the client on WhatsApp while they still remember the visit — not days later when they have moved on.
Offers tied to what they actually discussed
Four body variables carry the customer name, the company or specialist they met, the service topic from the visit, and the recommended next step, so the message reads as a personal follow-up rather than a generic marketing blast.
Compliant outreach outside the 24-hour window
An approved MARKETING template delivers the post-visit offer even when no conversation is open, so the business does not depend on the client messaging first after they leave.
Less manual rep follow-up after visits
The booking system or CRM resolves the phone and visit fields, builds the template with four body variables and a static URL button, and logs delivery — so staff do not retype visit context or remember to send each offer by hand.
Post-visit conversion analytics on the same record
Delivery result is written back to the booking system or CRM, so post-visit marketing campaigns report on the same visit record that triggered the message.

Workflow

  1. Build & send

    The booking system or CRM fires a post-visit trigger when the visit or contact is logged as complete.

    POST /sendTemplate

  2. Capture event

    The system resolves the recipient phone number and visit context fields from the contact record.

    phone: "+…"

  3. A personalised post-visit marketing

    A personalised post-visit marketing template is built with four body variables and a static URL button.

    POST /sendTemplate

  4. Delivered

    The client receives the WhatsApp marketing message with visit context and the recommended next step.

    delivered

  5. Delivery result is logged

    Delivery result is logged for post-visit conversion and repeat-visit campaign analytics.

    POST /sendTemplate

WhatsApp Business API for post-visit marketing message

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_COMPANYORSPECIALISTNAME="___"         # {{2}} company or specialist name
TEST_SERVICE="___"         # {{3}} service name
TEST_NEXTSTEP="___"         # {{4}} 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_COMPANYORSPECIALISTNAME=$TEST_COMPANYORSPECIALISTNAME" \
            "TEST_SERVICE=$TEST_SERVICE" \
            "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}} company or specialist name → ${TEST_COMPANYORSPECIALISTNAME}
# {{3}} service name → ${TEST_SERVICE}
# {{4}} 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_COMPANYORSPECIALISTNAME}" },
        { "type": "text", "text": "${TEST_SERVICE}" },
        { "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

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
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.
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