AI Agent Skill for WhatsApp APIMore
1msg official logo

Per-stage feedback survey via WhatsApp API

The scenario sends the client a personalized WhatsApp template when a specific service stage is completed, asking them to rate how that step went.

Use case overview

The scenario sends the client a personalized WhatsApp template when a specific service stage is completed, asking them to rate how that step went. The message includes the client name, stage name, and a short feedback prompt. A static URL button opens the stage survey form or feedback page.

Template example

Hello, {{1}}! Stage "{{2}}" is complete. {{3}} Please rate this service stage — it takes about a minute.

Rate stage
  • {{1}}
    customer name
  • {{2}}
    completed service stage name (e.g. onboarding call, diagnostics, installation)
  • {{3}}
    feedback prompt or instruction (e.g. rate this stage from 1 to 5, takes 1 minute)
  • “Rate stage”
    button — fixed in the Meta template
WhatsApp Business API for service stage feedback

When to use it

Use this scenario when a multi-stage service reaches a defined milestone and the team needs structured feedback on that specific step on WhatsApp rather than a manual follow-up message or end-of-project email survey alone. It fits implementation and onboarding teams collecting 1–5 star ratings after each milestone, field service and B2B delivery workflows surveying after diagnostics or installation, and agencies connecting stage-completed triggers from CRM, PSA, or custom service workflows.

Feedback while the stage is fresh
The stage survey lands in WhatsApp with name, stage name and feedback prompt as three body variables, so the rating ask arrives right after the milestone instead of a single email survey weeks later.
Compliant first message after stage completion
The operations system fires an approved template when the stage is marked done, so the feedback request reaches the client even when there is no open conversation and free-text replies are not allowed.
No manual stage survey messages
The stage-completed trigger resolves the recipient phone and feedback fields, builds the template with three body variables and a static URL button, so staff do not retype stage context or remember to send a rating link.
Stage context before they rate
Customer name and stage name appear in the message body, so the client knows which completed step they are rating before tapping the fixed Rate stage button that opens the feedback form.
Delivery logged for stage analytics
Delivery result is written back to CRM or the operations system while survey completion is tracked on the linked form, so stage-level quality follow-up stays tied to the same milestone record.

Workflow

  1. Trigger

    The CRM or operations system fires a stage-completed event when the milestone is marked done.

    event · triggered

  2. Capture event

    The system resolves the recipient phone number and stage feedback fields.

    phone: "+…"

  3. Build & send

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

    POST /sendTemplate

  4. Delivered

    The client receives the WhatsApp stage feedback request with stage context.

    delivered

  5. Status tracked

    Delivery result is logged; survey completion is tracked outside WhatsApp on the linked form.

    status: "read"

WhatsApp Business API for service stage feedback

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_STAGE="___"         # {{2}} stage name
TEST_INFO="___"         # {{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_STAGE=$TEST_STAGE" \
            "TEST_INFO=$TEST_INFO"; 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}} stage name → ${TEST_STAGE}
# {{3}} additional info → ${TEST_INFO}
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_STAGE}" },
        { "type": "text", "text": "${TEST_INFO}" }
      ]
    }

  ]
}
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
Negative feedback follow-up via WhatsApp API
The scenario sends the client a personalised WhatsApp template after they submit a neutral or low satisfaction rating.
Surveys & Feedback
New feedback alert to your team via WhatsApp API
The scenario sends the team manager a personalised WhatsApp template when new client feedback is captured.
Surveys & Feedback
Post-ticket support survey via WhatsApp API
The scenario sends the client a personalized WhatsApp template after a support case or ticket is completed, inviting them to share feedback in a short survey.
Surveys & Feedback
Satisfied/not satisfied buttons via WhatsApp API
This scenario sends the client a short personalised WhatsApp template asking them to confirm whether they are satisfied.
Surveys & Feedback
Written review request via WhatsApp API
The scenario sends the client a personalized WhatsApp template after a completed interaction, asking them to leave a written review or testimonial.
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.

Build for WhatsApp in hours
without infrastructure hassle