Quick answer
Put the exact source URL, product code, selected option and quantity in the message, then ask about the one missing detail that affects your decision. Sending only a screenshot and “price?” makes it too easy for the reply to refer to another product or quantity.
Prepare the record before preparing the message
- Current source URL and date checked.
- Exact product or listing code.
- Neutral product description.
- One row for each requested color, size, model or set.
- Quantity per row and total quantity.
- Destination context only when it affects the question.
- The smallest unresolved issue that changes the decision.
Use a compact message with stable anchors
Hello. I am reviewing [exact code] at [source URL].
The intended quantity is [total]: [variant rows].
Please confirm [one specification, quantity rule or price basis] for this exact product and mix.
If the answer changes by option or tier, please list the difference and the date or validity of the information.
Delete any line that does not affect your decision. Add a shipping question only after the product, quantity and packing assumptions are stable enough to describe.
Ask one decision-changing question at a time
| Unresolved field | Focused question | Usable answer includes |
|---|---|---|
| Specification | Which current specification applies to code X, option Y? | Exact code, option, value, unit or included parts. |
| MOQ | What minimum applies to total, variant, carton and order? | Each rule and whether the intended mix satisfies it. |
| Price | What price basis applies to this exact mix? | Currency, unit, tier, variant, inclusions and validity. |
| Availability | Which requested rows are currently available? | Confirmed, unavailable and substituted rows kept separate. |
| Shipping | What quote basis applies to this packed request? | Weight, dimensions, service, fees, exclusions and validity. |
Turn every reply into a status
Confirmed
The response names the exact product and answers the field with a clear basis.
Estimated
The value may change after packing, measurement, availability or another dependency.
Substituted
A different option, quantity, product or service is offered and recorded separately.
Unanswered
The reply is friendly or fast but does not close the requested field.
Keep a reply ledger instead of rewriting the original row
| Date | Question | Answer | Status | Effect |
|---|---|---|---|---|
| YYYY-MM-DD | Field requested | Exact response summary | Confirmed / estimated / changed | Keep / clarify / remove |
This preserves the original request and makes later changes visible. Save only the minimum personal information needed to understand the exchange.
Use a follow-up only when it can close the remaining gap
Do not resend the whole request after a partial answer. Quote the product code and ask one short follow-up about the missing unit, option, tier, inclusion or validity. If repeated replies continue to avoid the same decision-critical field, mark it unresolved.
Keep contact and payment checks separate from product clarity
A precise reply does not verify identity or make a payment route safe. Confirm that the contact belongs to the current authorized source you intended to reach, share no account passwords or verification codes, and review transaction terms with the responsible service before any commitment.
