A long WhatsApp conversation can contain several versions of the same order. The customer changes a colour, asks about a second item, gives a different delivery date and finally says “okay.” Unless you create a clear summary, neither person can be certain which version that agreement refers to.
A summary is not a payment receipt or proof that stock has been reserved. It is a readable statement of the proposed order and what happens next. Build it from checked facts rather than copying the last few messages.
Identify the actual items
Use the public product name together with the choice that changes what you will supply. Record the colour, size, variant or personalisation exactly enough for somebody else to prepare the order.
For a set, state both the ordered quantity and the contents. “Two” could mean two individual earrings or two pairs. Resolve that before asking the customer to confirm anything.
A product link or photograph can support the description, but it should not replace the written choice. Images can disappear from a conversation, and similar-looking products may have different dimensions or prices.
Separate confirmed facts from information still needed
Check availability, delivery coverage and any custom-work capacity before presenting the summary as ready to accept. If something remains unknown, label it.
For example, “delivery charge to be confirmed after postcode check” is honest, but the order is not yet a final-total proposal. Do not ask the buyer to agree to a total that can silently change later.
The WhatsApp Business feature documentation describes a catalogue cart as items sent in a message. Treat that incoming message as information to process, not proof that payment, availability and delivery have all been confirmed.
Use a compact, complete confirmation format
The following is an illustrative structure, not an oBizee notification template:
More columns may be available: swipe horizontally, or focus the table and use the arrow keys.
| Section | Information |
|---|---|
| Reference | Your private enquiry or order reference |
| Items | Product, option, quantity and counting unit |
| Charges | Item amounts, agreed discount and delivery charge |
| Total | The amount and currency the customer is being asked to accept |
| Fulfilment | Ready-made or made-to-order; dispatch estimate |
| Delivery | The necessary address confirmation in the private conversation |
| Next action | What the buyer should confirm and how payment is handled |
Only include information needed for this order. Do not copy identity documents, unrelated conversations or sensitive account information into the summary.
Ask for confirmation of the important choices
A useful request is specific: “Please confirm the cream colour, one pair and the delivery details above.” It helps the customer notice the parts most likely to cause a packing mistake.
For personalisation, present the exact text separately. Names, initials and dates need explicit checking. Do not rely on autocorrect or assume that an earlier spelling remains current after several revisions.
If you send a revised summary, mark it as the replacement and identify the changed field. Avoid having two apparently valid totals or delivery addresses in use at the same time.
Record the agreement in the order workflow
Once the customer confirms, transfer the agreed details into your actual order record. Keep a reference connecting the conversation and record so another person does not create the same order again.
Record payment status through your payment-confirmation process. Do not use “confirmed” as a single label for customer approval, stock commitment and money received; those states can happen at different times.
If stock must be held manually, follow the rule you have actually established. The stock guide explains why an enquiry and a reservation should not be treated as the same event.
Handle changes after confirmation deliberately
When a customer asks to change something, check whether the order has reached production or packing. Do not promise an edit before checking its practical effect.
Create an updated agreement if the change is accepted. Preserve the earlier version in the protected record instead of overwriting the history without explanation. The packer needs the current version; support may need to understand how it changed.
If the change affects the total, obtain the customer's agreement to that difference. Do not quietly substitute an item because it seems similar or costs the same.
Check your summary with somebody unfamiliar with the chat
Ask whether they could identify the exact item and next action from the summary alone. If they need to read dozens of messages to find the colour or quantity, improve the format.
Keep the summary short enough to read but complete enough to prevent guesswork. For missing product information, start with catalogue preparation. The useful outcome is one clear agreement connected to one order record—not a longer conversation with a more official-looking heading.
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