A Courier Business's Messaging Stack: Templates, a Receipt, and One MCP Shortcut

Take a composite example: a small local courier operation running same-day delivery across a handful of city neighborhoods. A handful of riders, a dispatcher coordinating routes, a support line that's really one person checking a phone between calls. Every shipment goes through the same handful of states — picked up, out for delivery, delivered — and every one of those states is a moment a customer wants to know about. Below is how that flow maps onto WhatsApp templates, a transactional email receipt, a keyword-triggered reply, and an MCP-connected dispatcher, using only what the underlying products actually do.

Two template messages, submitted to Meta once

WhatsApp Business Cloud API messages that a business sends first (rather than replies to something a customer wrote) have to be pre-approved HSM templates. For a courier, that's typically two: "your shipment has been picked up" and "your shipment is out for delivery," one for each state a customer cares about hearing from the business first. Tricknowtech handles the Meta submission and review for these templates, so the business isn't the one filing paperwork with Meta or waiting on their review queue directly.

The trigger for sending either message is a status change in the courier's own tracking system — a rider marks a shipment as picked up, and that event calls the WhatsApp API to fire the matching template to the customer's number. That's a direct API call the business's own backend makes (or a manual send through the dashboard, or, as below, a single call through MCP) each time a status actually changes. It is worth being precise about this because it's easy to conflate with the other WhatsApp feature covered next: this status-triggered send is not an automation rule. Automation rules in the product are keyword-matched against what a customer types in, not wired to backend events like a shipment status flip.

A keyword reply for "where is my order," then a human

Customers text back. A large share of inbound messages to a courier's WhatsApp number are some variant of "where is my package" or "has it shipped yet." On Growth-tier plans and above, an automation rule can match keywords like "where," "status," or "track" in an inbound message and send a canned reply — asking for the AWB number, pointing to a tracking link, or giving a generic response about delivery windows — without a human touching it.

The boundary matters here too: the rule only sees the text the customer sent. It has no visibility into the shipment's actual current status — it isn't reading from the tracking system, it's pattern-matching a keyword and firing a pre-written reply. If the customer's question isn't resolved by that reply, or they respond with something the keyword rule doesn't catch, the conversation lands in the shared team inbox, where a human agent picks it up. From there it can be bridged into a support ticket if it needs to be tracked past the chat itself. For a courier operation this two-stage setup does the routine filtering — freeing the one person checking WhatsApp from retyping the same status update over and over — while still routing anything unusual (wrong address, damaged package, a re-delivery request) to someone who can actually act on it.

What the automation rule can and can't do

• Can: match keywords in an inbound customer message and send an immediate canned reply.
• Can: hand off to the shared inbox when no keyword matches, or when the customer keeps writing.
• Can't: fire automatically because a shipment's status changed in the courier's own system — that's a template send, triggered by the business's own event, not the rule engine.

The delivery confirmation email as the paper trail

WhatsApp messages are good for a fast nudge but not much of a record either side wants to hold onto. Alongside the "delivered" WhatsApp template, the same status-change event can trigger a delivery confirmation email through the Email API — a shipping notification, one of the categories the API is built for. It functions as the durable receipt: something with a timestamp that lands in the customer's inbox and stays there, useful if a dispute comes up later about whether and when something actually arrived.

Because the Email API is transactional-only — enforced through the AWS SES production-access condition it operates under, not a policy the business has to self-police — a delivery confirmation is exactly the kind of send it's built for, and a promotional "here's a discount on your next delivery" email is not. Every send, whether from an approved template or freeform, gets checked by an LLM before it goes out to confirm it's genuinely transactional; templates are reviewed once and freeform content is checked live on each call. If the courier sets up a custom sending domain, DKIM signs automatically when hosted with Tricknowtech (or via CNAME records otherwise), and bounce or complaint webhooks mean a bad customer email address surfaces as a webhook event rather than a receipt silently vanishing — something a dispatcher can act on by calling the customer instead.

A dispatcher sending one message without opening the dashboard

Mid-route-planning, a dispatcher juggling a spreadsheet and a map doesn't necessarily want to open a browser tab, log into the dashboard, and click through to WhatsApp just to confirm one delivery. With an MCP token generated from profile settings, the same account is reachable from Claude Desktop, Cursor, or any other MCP-compatible assistant. The dispatcher can ask it to look up the approved delivery-confirmation template with list_whatsapp_templates, then send it for one specific shipment with send_whatsapp_template — a single call, no dashboard, without breaking whatever else they were doing.

The scope of what's MCP-reachable on the WhatsApp side is intentionally narrow: send_whatsapp_text, send_whatsapp_template, list_whatsapp_accounts, and list_whatsapp_templates. Setting up a new broadcast campaign or editing an automation rule still happens in the dashboard — those stay deliberate, reviewed actions rather than something an AI assistant can trigger on a whim. Once the customer replies, a push notification reaches whoever's watching the shared inbox, and the conversation picks up from there — through the keyword rule if it matches, or straight to a human if it doesn't.