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

Ticket closed notification via WhatsApp API

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

Use case overview

The scenario sends the client a personalized WhatsApp template when a support ticket is closed. The message includes the client name, ticket number, and closure reason. A static URL button opens ticket history or a reopen/feedback page.

Template example

Hello, {{1}}! Your request #{{2}} has been closed. Reason: {{3}}. To reopen the conversation — message us or open the request using the button below.

Request history
  • {{1}}
    customer name
  • {{2}}
    ticket or case number
  • {{3}}
    closure reason (e.g. resolved, duplicate request, no client response)
  • “Request history”
    button — fixed in the Meta template
WhatsApp Business API for ticket closed notification

When to use it

Reach for this scenario when a support ticket is closed and the client still needs a final word on why — especially if they no longer have an open WhatsApp chat. It fits helpdesks sending closure notices with a recorded reason, enterprise support teams that need audit-friendly client communication, and agencies wiring ticket-closed webhooks from Zendesk, Freshdesk, or a CRM.

Fewer "is my ticket still open?" messages
Three body variables carry the client name, ticket number and closure reason in WhatsApp, so the client sees why the case ended without opening email or calling back.
Final notice outside the 24-hour window
The helpdesk fires an approved template when the ticket closes, which is allowed when there is no active session — unlike a free-text reply that WhatsApp would block.
No manual closure messages
The system captures the closure event, resolves the phone number, and sends the template automatically, so agents do not retype the reason for each closed ticket.
Reopen path without a new ticket
The static URL button opens request history or a reopen page fixed in the Meta template, so the client can follow up from the same chat instead of guessing how to reach support.

Workflow

  1. Trigger

    The helpdesk closes the ticket and records the closure reason.

    event · triggered

  2. Capture event

    The system resolves the recipient phone number and closure 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 notification with ticket number and closure reason.

    delivered

  5. Status tracked

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

    status: "read"

WhatsApp Business API for ticket closed 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_CLOSUREREASON="___"         # {{3}} closure reason

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_CLOSUREREASON=$TEST_CLOSUREREASON"; 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}} closure reason → ${TEST_CLOSUREREASON}
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_CLOSUREREASON}" }
      ]
    }

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

Customer Service
Ticket transfer notification via WhatsApp API
The scenario sends the client a personalized WhatsApp template when a support ticket is transferred to another department.
Customer Service
Ticket status update notification via WhatsApp API
The scenario sends the client a personalized WhatsApp template when a support ticket status changes.
Customer Service
Ticket escalation notification via WhatsApp API
The scenario sends the client a personalized WhatsApp template when a support ticket is escalated because resolution is taking longer than usual.
Customer Service
Ticket created notification via WhatsApp API
The scenario sends the client a personalized WhatsApp template when a new support ticket is created.
Customer Service
Ask for a photo or file via WhatsApp API template
The scenario sends the client a personalized WhatsApp template when support needs a photo, document, or proof to process a ticket and no 24-hour session is open.
Customer Service
Request ticket details outside 24h (WhatsApp API)
The scenario sends the client a personalized WhatsApp template when support needs more data to resolve a ticket and no session window is open.
Customer Service
Ticket accepted notification via WhatsApp API
The scenario sends the client a personalized WhatsApp template when their support request is accepted for processing.
Customer Service
Create a WhatsApp group via API (groups endpoint)
This scenario uses the groups API with a create operation to provision a named WhatsApp group for team broadcasts.

Build for WhatsApp in hours
without infrastructure hassle