“Your order is confirmed” can mean several different things. The customer may understand it as payment received and stock secured, while the seller means only that a message arrived. That ambiguity creates avoidable support work.
Choose status language that matches the actual event. You do not need an automated notification system to do this well. A manual update based on a reliable record is more useful than an automatic message that overstates progress.
Name the event before writing the message
Separate receipt of an enquiry from acceptance of an order. Separate acceptance from payment verification where payment is required. Separate packing from courier handover.
Write a small internal status dictionary. For each status, define what must be true before somebody uses it and where that fact is recorded.
Do not adopt a status name merely because another store uses it. Your workflow may collect payment or confirm availability at a different stage.
Give the customer the useful consequence
A status label alone can be unclear. Explain what the event means and whether the customer needs to act.
For example, an enquiry acknowledgement can say that you received the requested items and will check availability. It should not claim that the items are reserved unless your actual process has created that commitment.
A packing update can state that the order is being prepared. A dispatch update should be based on the handover evidence available to you, not just the creation of a shipping label.
Use a consistent message structure
A useful update contains the reference, verified event, next step and any realistic update time.
More columns may be available: swipe horizontally, or focus the table and use the arrow keys.
| Event | Useful wording direction | Do not imply |
|---|---|---|
| Request received | We have the details and will check the request | Acceptance or payment |
| Order accepted | State the agreed items and next step | An unverified delivery date |
| Packed | Preparation is complete or at the stated stage | Courier possession |
| Handed over | Identify the verified dispatch event | Guaranteed arrival |
| Investigation open | Name what is being checked and next update | Resolution already completed |
These are writing directions, not ready-to-send claims about any particular order. Fill them from the protected order record.
Keep estimates separate from guarantees
Explain whether a date refers to production completion, dispatch or expected transit. “Three to five days” is incomplete if the customer cannot tell when counting begins.
If a date changes, acknowledge the earlier expectation and provide the best supported update. Avoid silently replacing an old estimate as though it had never been promised.
Do not blame a courier before checking the handover and tracking information. An order still in your packing area requires a different explanation from a parcel delayed after collection.
Decide who can send each update
A helper may be authorised to acknowledge an enquiry but not approve a refund or a custom delivery commitment. Make those boundaries explicit.
If several people or tools send messages, check that they are not producing contradictory updates. The message history should follow the order history, not become a second competing source of truth.
Do not claim that oBizee or WhatsApp automatically sends a particular notification unless that exact feature and configuration have been verified. This guide describes the communication standard regardless of the tool used.
Plan for missing or uncertain information
Sometimes the next event cannot be confirmed. Say what you know and what you are checking rather than choosing a more advanced status to reassure the customer.
An illustrative update is: “The label has been prepared, but I’m checking the collection record before confirming dispatch. I’ll update you by the end of the next working day.” Use only a follow-up time you can honour.
Avoid repeatedly sending “please wait” without a next action. A waiting case still needs an owner.
Keep a record of important promises
Store the relevant update in the order or support history so another person can see what the customer was told. Do not keep critical delivery commitments only in an individual's memory.
When a case closes, confirm the actual outcome rather than merely saying that it has been marked closed. Approval, processing and completion may be separate events.
Use the inventory guide for stock commitments and the Instagram-to-store guide for the wider buying path. Accurate order messages reduce uncertainty because their words correspond to real events—not because they sound more polished.
Examples are illustrative. Confirm current features, charges and suitability before making a business decision.
Explore this topic → · Find an oBizee setup guide · Ask about your store