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

Ticket resolved notification via WhatsApp API

The scenario sends the client a personalized WhatsApp template when their support ticket is resolved.

Use case overview

The scenario sends the client a personalized WhatsApp template when their support ticket is resolved. The message includes the client name, ticket number, and a brief resolution summary. A static URL button opens the ticket page or feedback form.

Template example

Hello, {{1}}! Your request #{{2}} has been resolved. {{3}} If the issue recurs — we are here to help.

Request status
  • {{1}}
    customer name
  • {{2}}
    ticket or case number
  • {{3}}
    resolution summary (e.g. refund processed, settings restored, replacement shipped)
  • “Request status”
    button — fixed in the Meta template
WhatsApp Business API for issue resolved notification

When to use it

When a support ticket moves to resolved and the business needs the client to see what was done — not just a closed status in the helpdesk — reach for this scenario. It fits helpdesk teams sending a one-line outcome summary, field service and repair crews confirming a fix on site, and agencies hooking resolved-ticket webhooks from Zendesk, Freshdesk, or a CRM.

Fewer "is it fixed yet?" follow-ups
Three body variables carry the client name, ticket number, and a short resolution summary in WhatsApp, so the client learns the case is closed without emailing support or opening the helpdesk portal.
Resolution details stay in the chat
The confirmation lands in the client's WhatsApp thread with ticket # and outcome text, so they can scroll back instead of searching email for what was done.
One tap to ticket or feedback
A static URL button fixed in the Meta template opens the ticket page or feedback form — the API sends only the three body variables.
No manual closure messages
The helpdesk fires a resolution event, the system resolves the phone and resolution fields, and the approved template goes out without an agent retyping the summary.
Delivery logged in the helpdesk
Delivery result is recorded in the helpdesk or CRM, so the team knows whether the closure notice reached the client.

Workflow

  1. Capture event

    The helpdesk marks the ticket resolved and fires a resolution event.

    phone: "+…"

  2. Resolves the recipient phone

    The system resolves the recipient phone number and resolution 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 confirmation with ticket number and resolution summary.

    delivered

  5. Status tracked

    Delivery result is logged; errors are handled according to platform rules.

    status: "read"

WhatsApp Business API for issue resolved 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 ===
TEST_PHONE="___"                 # client phone in international format
TEST_CUSTOMERNAME="___"         # {{1}} customer name
TEST_TICKETNUMBER="___"         # {{2}} ticket number
TEST_RESOLUTION="___"         # {{3}} resolution summary

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_TICKETNUMBER=$TEST_TICKETNUMBER" \
            "TEST_RESOLUTION=$TEST_RESOLUTION"; 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}} ticket number → ${TEST_TICKETNUMBER}
# {{3}} resolution summary → ${TEST_RESOLUTION}
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_TICKETNUMBER}" },
        { "type": "text", "text": "${TEST_RESOLUTION}" }
      ]
    }

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

Build for WhatsApp in hours
without infrastructure hassle