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

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.

Use case overview

The scenario sends the team manager a personalised WhatsApp template when new client feedback is captured. The message includes the customer name, feedback topic, and a short summary. A static URL button opens the feedback dashboard.

Template example

🔔 New feedback

Client: {{1}}

Topic: {{2}}

Details: {{3}}

Review the feedback and follow up if needed.

Open feedback
  • {{1}}
    customer name
  • {{2}}
    feedback topic or survey name (e.g. post-visit rating, delivery CSAT)
  • {{3}}
    feedback summary (rating, score, or short comment excerpt)
  • “Open feedback”
    button — fixed in the Meta template
WhatsApp Business API for new feedback team notification

When to use it

Reach for this scenario when a client submits feedback through a survey, rating widget, or form and the operations or quality team needs to know immediately — not after checking email or refreshing a dashboard. It fits customer success teams monitoring CSAT and NPS, quality teams routing post-visit or post-delivery ratings to a duty manager, and integrators wiring survey webhooks into internal WhatsApp alerts.

Faster follow-up on new feedback
The survey platform or CRM emits a new-feedback event, and the approved template reaches the manager's phone with customer name, topic and summary as three body variables — before low scores sit unnoticed in the inbox.
Alerts that reach mobile first
The message goes to WhatsApp on the manager's phone instead of email, so the team sees new feedback without opening a dashboard; only an approved template can start the conversation when there is no open chat.
One tap into the feedback record
A static URL button fixed in the Meta template opens the feedback dashboard, so the manager does not hunt for the new entry after reading the alert — only the three body variables are sent via the API.
Logged delivery for quality analytics
The send result is logged after delivery, so CRM or quality workflows can track whether the alert reached the assigned manager.

Workflow

  1. Trigger

    The survey platform or CRM emits a new-feedback event.

    event · triggered

  2. Capture event

    The system resolves the team manager phone number and feedback summary fields.

    phone: "+…"

  3. Build & send

    An internal notification template is built with three body variables and a static URL button.

    POST /sendTemplate

  4. Delivered

    The manager receives the WhatsApp alert on their phone.

    delivered

  5. Status tracked

    Delivery result is logged; the manager opens the feedback dashboard via the button to follow up.

    status: "read"

WhatsApp Business API for new feedback team 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 ===
MANAGER_PHONE="___"                 # manager phone in international format
TEST_CUSTOMERNAME="___"         # {{1}} customer name
TEST_TOPIC="___"         # {{2}} topic or subject
TEST_REQUESTDETAIL="___"         # {{3}} request detail

PHONE_NORM="$(printf '%s' "$MANAGER_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" "MANAGER_PHONE=$MANAGER_PHONE" \
            "TEST_CUSTOMERNAME=$TEST_CUSTOMERNAME" \
            "TEST_TOPIC=$TEST_TOPIC" \
            "TEST_REQUESTDETAIL=$TEST_REQUESTDETAIL"; 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}} request detail → ${TEST_REQUESTDETAIL}
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_REQUESTDETAIL}" }
      ]
    }

  ]
}
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 manager."
    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
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
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.
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