First message
Use a compact message with a visible structure
Hello. I am comparing product code H204 from this page: [direct URL].
Proposed quantity: 24 units — black 12, grey 12, sizes M–XL.
Please confirm: the MOQ for this product and each size/color, the unit-price tiers near 24 and 50 units, the available colors, the measurement chart for this exact code, standard packing, and estimated preparation time.
If shipping can be estimated, please state the weight basis, route, currency, included fees, and quote validity for [country/region]. Thank you.
This is a format, not a script to paste blindly. Replace every bracket and remove questions that do not apply. A shorter, accurate inquiry is better than a long generic request for a complete catalog.
Different needs
Change the message when the decision changes
When you need a sample
Ask whether a sample of the exact code and variant is offered, how its price and packing differ from bulk terms, and whether a later order uses a separate MOQ.
When the catalog has no price
Name the code, quantity, color, size, and requested inclusions. Ask for currency and validity instead of asking for a context-free “best price.”
When a photo is unclear
Describe the missing angle or measurement. Request evidence for that feature rather than asking broadly for “more QC.”
Reply quality
A quick reply is not always a usable reply
| Reply pattern | What it gives you | Best next action |
|---|---|---|
| Answers by product code and line item | Traceable quantities, variants, prices, and conditions. | Copy the answer into the comparison record with its date. |
| Sends a broad price list | General context, but not necessarily the selected product or quantity. | Return to the exact code and ask which row applies. |
| Changes the item | A substitute rather than confirmation of your request. | Decide whether to start a new comparison; do not merge the products. |
| Uses only voice notes or disappearing content | Information that is difficult to review and audit. | Ask for the key terms in writing before continuing. |
| Requests immediate payment before details | Pressure without enough transaction context. | Stop and review identity, source, terms, and payment protection. |
Message hygiene
Share only what the inquiry actually requires
- Do not send passwords, payment credentials, identity documents, or full address details just to request a catalog price.
- Do not treat a WhatsApp number as supplier verification; compare it with consistent public source context.
- Do not move a payment merely because a contact says the account changed. Recheck the responsible route and protection.
- Do not combine several products in one paragraph when each has different codes, sizes, quantities, or questions.
- Preserve the reply date and quote scope because availability, price, MOQ, and shipping conditions can change.
After the reply
Convert the conversation into facts and unresolved questions
Move each confirmed term into its own field: product code, variant, quantity, unit price, currency, MOQ rule, packing, lead time, shipping scope, validity, and responsible party. Anything not answered remains blank or unresolved. Do not let a friendly conversation fill missing evidence.
