Order and delivery notifications that customers actually open

The complete guide

Order and delivery notifications that customers actually open: everything you need to know

What are order and delivery notifications?

Short answer: Order and delivery notifications are the messages a business sends to confirm a purchase, share tracking details, announce out-for-delivery status and confirm an order arrived. In Com.Bot they are triggered by store or order events, built from Meta-approved templates with variables for customer name, order number, tracking link and delivery window, so one template covers thousands of orders.

Order and delivery notifications are the messages a business sends to confirm a purchase, share tracking details, announce out-for-delivery status and confirm that an order arrived. On chat channels they replace or supplement email and SMS with a message that lands in the same app where the customer talks to friends and family.

In Com.Bot these messages are triggered by events in your store or order system. A new order fires a confirmation, a courier scan fires a shipping update, a failed delivery attempt fires a reschedule prompt. Each message is built from a Meta-approved template with variables for the customer name, order number, tracking link and delivery window, so one template covers thousands of orders.

The feature sits inside Com.Bot's broader business communication platform, alongside the shared team inbox, visual bot builder, contacts CRM and WhatsApp commerce tools. That means a delivery update can hand off to a live agent, open a reschedule flow or trigger a review request without leaving the platform.

• Order confirmation with items, total and order number
• Shipping and tracking updates with a courier link
• Out-for-delivery and delivered confirmations
• Failed delivery attempts with a reschedule option
• Payment due or COD confirmation for existing orders
• Delivery alerts for service businesses and bookings

Who needs order and delivery notifications?

Short answer: Any business that ships a product or delivers a booked service needs order and delivery notifications, especially small teams without a large support desk. D2C brands, marketplaces, pharmacies, subscription boxes, restaurants, repair services, coaching institutes and agencies managing messaging for clients all use them to answer what happens next.

Any business that ships a product or delivers a booked service benefits, but the fit is sharpest for small and growing teams without a large support desk. A D2C skincare brand sending 400 orders a week cannot afford two staff answering tracking questions all day. A coaching institute confirming session times and reminding students of a booked slot has the same problem in a different shape.

Agencies and service businesses use the feature on behalf of clients. Because Com.Bot supports multiple WhatsApp API channels on higher plans and a shared team inbox with role-based access, an agency can run order updates for several brands from one workspace and give each client a clean view of their own conversations.

Marketplaces, local delivery services, pharmacies, electronics sellers and subscription boxes are common users. So are restaurants and cloud kitchens confirming prepaid orders, and repair or installation services confirming an appointment window. The pattern is the same: a customer completed a transaction and now wants to know what happens next.

• D2C and ecommerce brands shipping physical goods
• Agencies managing messaging for multiple clients
• Service businesses confirming booked appointments
• Marketplaces coordinating third-party sellers
• Subscription and repeat-delivery businesses
• Local delivery and installation teams

Why do order and delivery notifications work better on chat?

Short answer: Order and delivery notifications work better on chat because a WhatsApp message from a verified business appears with your brand name and logo, and customers open it like a conversation. Replies open the 24-hour customer service window, so your team can answer or reschedule without a new paid conversation, unlike email.

Email open rates for transactional mail are unpredictable, and SMS is expensive and plain. Chat apps behave differently. A WhatsApp message from a verified business appears with your brand name and logo, and customers open it because it looks like a conversation, not a broadcast. Read receipts on RCS and reply behavior on WhatsApp give you a clearer picture of whether the update was seen.

The bigger advantage is the reply. When a customer gets a delivery update on WhatsApp, they can reply in the same thread. That reply opens the 24-hour customer service window, so your team can answer a question, change an address or reschedule a delivery without starting a new paid conversation. On email, that exchange becomes a support ticket. On chat, it is a two-line reply.

Com.Bot runs the same notification logic across WhatsApp, Instagram DMs, Facebook Messenger and Google RCS. Instagram and Messenger automation works through Meta's official messaging APIs for professional accounts, and RCS Business Messaging delivers rich cards with images and action buttons on supported Android devices.

• Branded sender with logo and verified badge on RCS
• Read receipts and reply behavior you can track
• Customer replies open a free 24-hour service window
• Rich cards, buttons and tracking links in one message
• RCS reach on supported Android phones and carriers
• One platform across four chat channels

How do you set up order and delivery notifications in Com.Bot?

Short answer: Setting up order and delivery notifications in Com.Bot starts with your WhatsApp Business API channel, provisioned as an official Meta Business Partner with direct integration. You connect your store or order system, choose triggering events, create Meta-approved utility templates, map variables for name, order number and tracking link, then test before going live.

Setup starts with your WhatsApp Business API channel, which Com.Bot provisions as an official Meta Business Partner with direct integration. You connect your store or order management system, then choose which events should fire a message: order placed, payment received, order packed, shipped, out for delivery, delivered, delivery failed. Com.Bot's automation builder supports 1,000+ integrations, bot triggers and external actions such as API calls and webhooks, so custom order systems connect through a webhook if there is no ready integration.

Next you create the message templates. Meta requires business-initiated messages to use approved templates, and each template is filed under a category. Order confirmations, shipping updates and delivery confirmations are utility templates because they relate to a transaction the customer already started. Cart reminders, offers and re-engagement messages are marketing. Getting the category right matters: it affects approval and the rate Meta charges.

Finally you map variables and test. A template like "Hi {{1}}, your order {{2}} has shipped. Track it here: {{3}}" pulls the customer name, order number and tracking link from your data. Com.Bot's visual drag-and-drop bot builder and bot debugging sessions on Gold and Platinum plans let you run a test order through the flow before it goes live. Once approved, the flow runs on its own.

• Connect your store or order system to Com.Bot
• Pick the order events that should trigger a message
• Create and submit Meta-approved templates by category
• Map variables for name, order number and tracking link
• Test with a live order before switching it on
• Route replies to the shared team inbox

What are the rules and compliance points for order and delivery notifications?

Short answer: Order and delivery notification rules require Meta-approved templates sent only to opted-in contacts. Transaction updates like shipping and delivery confirmations are utility templates, while offers, cart reminders and re-engagement are marketing. WhatsApp message charges are billed separately from the plan by category and country, and replies open the 24-hour service window.

WhatsApp Business API has clear rules. Business-initiated messages must use Meta-approved templates and go only to contacts who opted in. You cannot message a phone number just because someone once visited your site. Opt-in has to be collected, and it is worth collecting it at checkout with a clear checkbox that explains what the customer will receive.

Template categories must be applied honestly. A shipping update for an order the customer placed is utility. A back-in-stock alert, a price drop, a cart reminder or a re-engagement message is marketing, even if it mentions a product the customer viewed. Authentication templates are for one-time passcodes only. Misclassifying a marketing message as utility is a common reason templates get rejected or accounts get flagged.

Meta charges per delivered template message by category and the recipient's country. WhatsApp message charges are billed separately from the plan, based on message category and the recipient's country, and there is no monthly conversation cap. When a customer replies, the 24-hour customer service window opens and free-form replies inside it are not charged as service messages. Quality rating and messaging limits grow with good engagement, so keep lists clean and send only what the customer expects. The green tick is granted by Meta, not by a provider; Com.Bot can help you apply.

• Collect opt-in before sending any template
• Use utility templates for transaction updates only
• File offers and cart reminders as marketing
• Keep authentication templates for OTPs
• Respect the 24-hour service window for free-form replies
• WhatsApp message charges are billed separately from the plan

What mistakes should you avoid with order and delivery notifications?

Short answer: Avoid treating order and delivery notifications as a marketing channel, since adding discount codes to shipping updates pushes templates toward marketing classification. Do not send an update at every warehouse scan, hardcode tracking links, ignore time zones, leave replies unassigned or skip opt-in collection at checkout, because reports lower your quality rating.

The most expensive mistake is treating notifications as a marketing channel. Adding a discount code to every shipping update, or sending a promotional follow-up outside the service window, pushes templates toward marketing classification and annoys customers who only wanted tracking. Keep utility messages clean and separate promotional sends into their own marketing templates with their own opt-in.

The second mistake is sending too many updates. A confirmation, a shipped message and a delivered message are usually welcome. A message at every warehouse scan is not. Map only the events customers care about, and let them opt down if they want fewer. Frequency is the fastest way to earn a block or a report, and reports lower your quality rating.

Other common errors include hardcoding tracking links that break, forgetting time zones when promising a delivery window, ignoring replies because no one owns the inbox, and skipping the opt-in step at checkout. Each one is avoidable with a short setup checklist and a clear owner for the shared inbox.

• Do not mix promotions into utility templates
• Do not send an update at every internal scan
• Do not promise delivery windows in the wrong time zone
• Do not leave customer replies unassigned
• Do not skip opt-in collection at checkout
• Do not ignore quality rating warnings

How do you measure results and what does it cost?

Short answer: Measure order and delivery notification results by tracking delivery rate, read or reply rate, order status support tickets and repeat purchase rate from notified customers. Com.Bot plans are billed quarterly: Silver $149, Gold $349 and Platinum V1 $2,500, with WhatsApp message charges billed separately by category and country.

Track four numbers: delivery rate, read or reply rate, support tickets about order status, and repeat purchase rate from notified customers. In Com.Bot you can see message status in the shared inbox and connect outcomes to your contacts CRM, where each contact record shows the conversation history. If "where is my order" tickets drop after you turn on shipping updates, the feature is paying for itself.

Cost has two parts. The Com.Bot plan covers the platform, and WhatsApp message charges are billed separately from the plan, based on message category and the recipient's country, with no monthly cap. Plans are billed quarterly in USD: Silver at $149, Gold at $349 and Platinum V1 at $2,500. Gold is the recommended tier for growing brands and adds more team members, more bot builder blocks and faster support. Add-ons include extra team members, social channels and ecommerce stores at $10 per month each.

If you want help, expert assistance is available at $49 per hour for WABA, CRM and inbox work, and $99 per hour for ecommerce, bots and automations. You can sign up at https://v3.com.bot/register, book a demo or reach support on WhatsApp at +91 080 6987 1810, or email sales@com.bot. Com.Bot is owned and managed by Com Bot AI Limited, Surat, India, and serves 50,000+ active customers across 50+ countries.

• Delivery rate and read or reply rate per template
• Volume of order status support tickets
• Repeat purchase rate from notified customers
• Plan cost plus pass-through Meta conversation charges
• Add-ons at $10 per month per extra seat or channel
• Expert help from $49 per hour

Frequently asked questions