WhatsApp Business API Order Notifications and CRM

Order notifications through the WhatsApp Business API mean sending your customer an automatic WhatsApp message from a pre-approved template when the order is received, shipped and delivered; CRM is the structure that gathers those notifications together with incoming WhatsApp messages, email and marketplace questions in one inbox. Bulutegra's CRM module does both inside the Integration Panel: a notification goes out when the order status changes, and when the customer replies, the message lands in front of the same team. This article explains the problem, how the module works, and what to check before you start setup.

The problem: customer communication in five different places

In a multi-channel business, customer messages arrive scattered. Amazon buyer messages, eBay messages, Trendyol's Q&A section, your own store's contact form and email, plus WhatsApp on the company phone. Each sits in a separate app, under a separate person's responsibility, with a separate response time. Some messages are answered late and some never seen; because marketplaces score response time, the cost is lost visibility.

Notifications are just as scattered. A customer who ordered from your own store writes on WhatsApp asking "where is my order"; someone on the team looks up the order and types a reply by hand. That question repeats dozens of times a day and asks for information the system already has. We covered handling marketplace questions in marketplace Q&A and customer messages; this article is about bringing WhatsApp and email into the same structure.

What the WhatsApp Business API is, and how it differs from the app

The WhatsApp Business app on a phone is a fine start for a small business, but it is tied to one device, messages are typed by hand and it has no link to your order system. The WhatsApp Business API is the interface Meta offers businesses so that software can send messages in your number's name and collect incoming ones. Several people work from one number, messages are logged, and they can be linked to order data.

API use has rules, and they change from time to time:

• Your business account must be verified by Meta
• If you message the customer first, the message must follow a pre-approved template
• The customer must have opted in to receive notifications
• Messages are priced by conversation type; check the current rate card

Setting up without knowing these rules ends in rejected templates and undelivered notifications. For current terms, read Meta's own documentation and your country's data protection rules, including GDPR where it applies.

How order notifications work

In the CRM module, notifications are tied to order status. When an order reaches a given status in the Integration Panel, the template defined for that status is sent to the customer's number. The typical flow:

1. The customer orders from your own store and opts in to WhatsApp notifications.
2. The order lands in the panel; the "order received" template goes out with the order number and a summary.
3. When the order ships, the "shipped" template goes out with the carrier and tracking number.
4. On delivery, a "delivered" message is sent, with a link to the returns portal if you choose.
5. If the customer replies to any message, the reply lands in the CRM inbox and is linked to the order.

You define the template content; fields such as order number, product name and tracking number fill automatically. You also decide which statuses trigger a notification; messaging on every status only wears the customer out.

On marketplace orders the buyer's phone number is often not shared with the seller, and marketplaces restrict buyer communication to their own channel. Plan WhatsApp notifications for opted-in customers from your own store; communication with marketplace buyers follows the marketplace's rules.

One inbox: WhatsApp, email and marketplace questions

The second part of the CRM module is the inbox. WhatsApp messages, emails and product questions from connected marketplaces appear in one list. Next to each message you see the source channel, the related order or product where there is one, and how long it has been waiting. The team opens the message, writes the reply, and the reply goes back through the channel it came from: a marketplace question returns to the marketplace, a WhatsApp message returns to WhatsApp.

The practical benefits of this structure:

• Waiting messages are sorted in one list; nothing is forgotten in another app
• Because the message is linked to the order, the team replies without searching for it
• Several people work in the same inbox, and it is visible who took which message
• User roles apply: the warehouse team sees only the messages relevant to it
• Message history is kept per customer, so when the same customer writes again, the earlier conversation is there

For user roles and access structure, see security, 2FA and roles in marketplace integration; the CRM inbox works with the same role model.

Checklist before setup

Completing these preparations before switching the CRM module on shortens setup:

• Start business verification for the WhatsApp Business API; approval time is not in your hands
• Choose a dedicated number for notifications; do not use a personal phone number
• Write the text of the order received, shipped and delivered templates and submit them for approval
• Define where and how consent for notifications is collected on your store
• Add your email account and the Q&A access of connected marketplaces to the panel
• Decide which team member owns which channel and set a response time target

The response time target is last on the list but first in importance. A single inbox makes messages visible; if nobody has answered the question of who replies within how long, visibility alone produces no result.

What notifications do for operations

Automatic notifications are not only about customer satisfaction. When "where is my order" questions fall, the team has time for real problems: wrong items, damaged deliveries, return requests. Sending the tracking number immediately lets the customer follow delivery problems too. A returns portal link in the delivered message helps returns start through the portal rather than a phone call. We described the rest of that flow in marketplace returns management and the returns portal.

How it works with Bulutegra

CRM is one of Bulutegra's add-on modules and runs inside the Integration Panel. Because order statuses are already tracked in the panel, notifications attach to the order flow without a separate system; the WhatsApp Business API, email and marketplace questions are gathered in one inbox, every message is linked to its order, and the team works under user roles. See the module's scope under Solutions; to review your current message flow together, request a quote.