COD Confirmation WhatsApp Template for Travel

Personalise it so it reads 1:1, not like a blast

The difference between a confirmation that converts and one that gets ignored is specificity. Generic "your booking is confirmed" copy feels automated; a message naming the traveller, their exact package or route, the pickup date and time, and the precise amount payable reads like a personal note from their travel desk. Use {{1}} for the name, {{2}} for your internal booking reference so support can pull it up in one search, {{3}} for the human-readable package or route, {{4}} for the date and pickup detail, and {{5}} for the COD amount. The more concrete the details, the higher the trust and the fewer the "is this real?" replies your team has to field. Keep the amount and date accurate to the paisa and minute — a mismatch here is the fastest way to trigger a dispute at pickup.

Get it approved as Utility on the first try

Submit this template under the Utility category — it is transactional and tied to a booking the customer actively made, which is exactly what utility is for. The single biggest cause of rejection is contamination: the moment you add a discount, an upsell, or promotional language ("book your next trip and save!"), Meta reclassifies it as marketing and may reject the utility submission. Keep the body strictly informational — confirm, pay, or cancel — and nothing else. Provide realistic sample values for every variable when you submit, because reviewers check that {{5}} looks like a currency amount and {{2}} looks like a reference. Avoid ALL-CAPS shouting, excessive emoji, and shortened tracking links, all of which slow review. In InfiQ's template management you can save this as a reusable utility template, submit for approval, and reuse it across every COD departure without re-drafting.

• Category: Utility — never mix in an offer or you push it to marketing
• Provide sample values for {{1}}–{{5}} at submission time
• Keep buttons functional: Confirm, Pay now, Cancel — no promo CTAs
• Approval is usually granted within a day; then send instantly via InfiQ

What it costs to send

Since Meta moved off per-conversation billing on 1 July 2025, WhatsApp charges per delivered message by category, and this template bills at the utility rate — the cheaper transactional tier, well below the marketing rate. The free 24-hour service window still applies when a customer messages you first, so any back-and-forth after they tap a button costs nothing extra within that window; it is a free service window, not a billing unit. InfiQ applies transparent ₹ pricing (ex-GST), so you see the exact per-message utility cost before you send a single confirmation. For most travel operators the maths is decisive: one prevented no-show on a fixed-departure seat or a held hotel room recovers the cost of thousands of confirmation messages.

Variations you can copy

One confirmation rarely fits every product line, so adapt the base template to the moment. A stripped-down version with just the name and booking reference works for high-volume, low-value bookings like intercity cabs where speed matters more than detail. A reminder variant re-sends the same confirmation a few hours before pickup for early-morning departures where no-shows spike. And because a large share of Indian travellers are more comfortable in their own language, a Hindi or regional-language version of this exact utility template — submitted separately for approval — noticeably lifts confirmation rates in tier-2 and tier-3 markets. Keep every variation strictly utility; if you want to add a limited-time upgrade offer, build that as a separate marketing template with an opt-out line rather than bending this one.

• Shorter: name plus booking reference only, for quick high-volume sends
• Pre-departure reminder: re-send hours before pickup to cut morning no-shows
• Regional language: a Hindi or local-language utility version for wider markets