Tradexa
Skip to article

Order updates and promotional messages: why they need different workflows

5 min read
Share
An order update helps a specific order while a promotion offers an eligible audience a reason to purchase, with distinct checks for each.
In this article

A customer waiting for a dispatch update and a customer considering a new offer need different messages. Sending both through the same contact list does not make them the same workflow.

An order update should help someone understand or complete a specific transaction. A promotion should give an eligible customer a relevant reason to consider another purchase. Separate the purposes before deciding the channel, trigger or success measure.

What does the customer need right now?

For an order message, the immediate job may be confirming payment, explaining dispatch or asking for information needed to complete delivery. Keep the transaction recognisable and the next action clear.

For a promotion, the job is different: the customer should understand what is offered, why it is relevant and what to do if interested. A broad “shop now” message may be easy to send but gives little reason to care.

Do not turn every service update into an offer. That can make a useful message harder to understand and introduces different platform-policy considerations.

Two messages, two different jobs

These are sample wording for a hypothetical seller, not approved WhatsApp templates. Replace references and links with real records and use the platform's approval process where required.

An order update

Example message: “Your order TX1042 has been dispatched. Track it using the link in your order details. Need help with this delivery? Reply with your order number.”

  • Trigger: a confirmed dispatch event with a usable tracking reference—not simply an order being created.
  • Recipient: the customer attached to that order, eligible for contact on the selected channel.
  • Reply owner: support checks the order and delivery record; a delayed or damaged delivery goes to a person who can act.
  • Measure: whether the customer receives usable information and whether dispatch-status enquiries fall. Delivery performance remains a separate measure.

A promotional campaign

Example message: “Looking for a second lens for your camera? Explore this week's lens offers on our website. Reply if you'd like help choosing. Reply STOP to stop promotional messages.”

  • Trigger: a planned campaign for an eligible audience with relevant interests, an actual offer and stock to fulfil it.
  • Recipient: customers with appropriate messaging permission, excluding opt-outs. A previous order by itself is not permission for all promotions.
  • Reply owner: a sales/support team that can help with the product, explain the offer and honour opt-outs.
  • Measure: responses, retained purchases and contribution after message and offer costs—not just sends.

Keep the service message free of a surprise sales pitch. Give the promotion a clear reason to matter, rather than disguising it as order information.

What should trigger each message?

An order workflow should rely on the appropriate verified transaction event and customer record. Before enabling it, test the timing and the link between the message and the order.

A campaign needs an eligible audience, approved message where required, a schedule and a decision about frequency. Buying once is not blanket permission for every future promotion.

WhatsApp's business messaging policy sets requirements for permission, respecting opt-outs and approved templates in applicable messaging contexts. Check the current policy and your configured channel workflow before sending; a customer-data record alone does not establish eligibility.

What could a cleaner workflow change?

Imagine 800 orders a month, with 120 customers contacting the team because they cannot understand the dispatch status. Each enquiry takes six staff-minutes to investigate and answer: 12 staff-hours.

Classify those 120 enquiries first. Suppose 50 only need an available tracking reference that the customer was never sent; the other 70 concern delivery problems or questions still requiring help. If the revised update reaches and answers those 50 customers before they contact support, it releases five hours a month—60 a year at steady volume. Test that prevention against actual enquiry records; delivery problems remain with the team.

That gives the team more time for damaged deliveries, product advice and other conversations that require a person. As orders grow, clear routine updates can keep some service work from growing at the same rate. Relevant promotions serve a separate growth job: giving interested customers a useful reason to buy again.

Campaigns need different evidence: relevant responses, purchases and contribution after campaign costs, not simply the number of messages sent.

Keep the workflows connected without mixing their purposes

Tradexa's HyperMarketing supports configured customer campaigns and transactional workflows across WhatsApp, email, SMS and push in the supported scope. WhatsApp templates follow an approval workflow. Supported abandoned-cart recovery and the WhatsApp support desk are separate capabilities with their own setup.

Automation does not remove responsibility for eligibility, accurate events or human follow-up. Decide who reviews failed messages and who handles a customer reply.

Start with one transaction where customers repeatedly ask the same question. Make that update useful first. Then build promotions around a clear audience and offer. The business gains a calmer service workflow and a more deliberate way to create demand, rather than one larger stream of messages.

See the current WhatsApp business messaging policy when setting up that channel.

Example note: The numbers illustrate a scenario, not measured customer results. Actual outcomes vary with business type, category, demand, competition, team, processes, business setup, external conditions and how effectively the workflow is used. Replace the example inputs with your own before making a decision.

Keep reading

View all