1msg official logo

NPS survey via WhatsApp API template

The scenario sends the client a personalized WhatsApp template after an interaction is completed, asking them to rate how likely they are to recommend the business.

Use case overview

The scenario sends the client a personalized WhatsApp template after an interaction is completed, asking them to rate how likely they are to recommend the business. The message includes the client name, interaction context, and a short 0–10 NPS prompt. A static URL button opens the NPS survey form.

Template example

Hello, {{1}}! {{2}}. {{3}} Please take our short NPS survey — it takes about a minute.

Take NPS survey
  • {{1}}
    customer name
  • {{2}}
    interaction context or topic (e.g. recent purchase, completed visit, closed support case)
  • {{3}}
    NPS prompt or instruction (e.g. on a scale of 0 to 10, how likely are you to recommend us)
  • “Take NPS survey”
    button — fixed in the Meta template
WhatsApp Business API for nps survey after interaction

When to use it

Use this scenario when a customer completes an interaction — purchase, service visit, delivery, or support case — and the team needs a structured 0–10 NPS score on WhatsApp rather than a manual message or email-only survey. It fits e-commerce teams measuring loyalty after checkout, service businesses after appointments, and agencies connecting NPS triggers from CRM or helpdesk workflows.

Higher NPS response rates
The NPS request lands in WhatsApp with name, interaction context and 0–10 prompt as three body variables, so the loyalty ask sits in a channel the client already uses instead of an email survey they never open.
Compliant first message after completion
The post-interaction trigger sends an approved template when the case is eligible, so the NPS request reaches the client even when there is no open conversation and free-text replies are not allowed.
No manual agent survey messages
The NPS trigger resolves the recipient phone and survey fields, builds the template with three body variables and a static URL button, so agents do not retype interaction context or remember to send a survey link.
Interaction context before they score
Customer name and interaction topic appear in the message body, so the client knows which completed interaction they are rating before tapping the fixed Take NPS survey button that opens the 0–10 form.
Delivery logged for follow-up analytics
Delivery result is written back to the CRM or analytics stack while NPS submission is tracked on the linked form, so follow-up stays tied to the same interaction record.

Workflow

  1. Build & send

    The CRM or product fires a post-interaction NPS trigger when the case is eligible.

    POST /sendTemplate

  2. Capture event

    The system resolves the recipient phone number and survey fields.

    phone: "+…"

  3. A personalized template message

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

    POST /sendTemplate

  4. Delivered

    The client receives the WhatsApp NPS request with interaction context.

    delivered

  5. Status tracked

    Delivery result is logged; NPS submission is tracked outside WhatsApp on the linked form.

    status: "read"

WhatsApp Business API for nps survey after interaction

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_TOPIC="___"         # {{2}} topic or subject
TEST_ADDITIONALINFO="___"         # {{3}} 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_TOPIC=$TEST_TOPIC" \
            "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}} topic or subject → ${TEST_TOPIC}
# {{3}} 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_TOPIC}" },
        { "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

Surveys & Feedback
Survey completion reminder via WhatsApp API
The scenario sends the client a personalised WhatsApp template when a survey request is still pending after the first ask.
Surveys & Feedback
Post-visit survey via WhatsApp API template
The scenario sends the client a personalized WhatsApp template after a visit or appointment is completed, asking them to share feedback on the experience.
Surveys & Feedback
Delivery rating survey via WhatsApp API
The scenario sends the client a personalized WhatsApp template after an order is delivered, asking them to rate delivery quality.
Surveys & Feedback
Service quality survey via WhatsApp API
The scenario sends the client a personalized WhatsApp template after a service interaction, asking them to rate the quality of service they received.
Surveys & Feedback
One-tap survey with WhatsApp quick-reply buttons
This scenario sends the client a short personalised WhatsApp template asking for quick feedback.
Surveys & Feedback
Review request message via WhatsApp API
The scenario sends the client a personalized WhatsApp template after a purchase when a review is due, asking them to rate the product and share feedback.
Surveys & Feedback
Service rating request via WhatsApp API
The scenario sends the client a personalized WhatsApp template after a service is completed, asking them to rate the quality of what was delivered.
Surveys & Feedback
CSAT survey after support via WhatsApp API
The scenario sends the client a personalized WhatsApp template after support is completed, asking them to rate service quality.

Build for WhatsApp in hours
without infrastructure hassle