Attach the original scope
Include the order identifier, service identifier, target, and quantity. Save the description that explains coverage. Support needs to distinguish the request from other orders on the same account, especially if several services affected the target.
Describe the observed change
Record the metric, observation source, and timestamps. Explain any additional orders or content changes that occurred between measurements. A single screenshot without context may show a current total but not establish which purchase is relevant to the issue.
Ask for an eligibility decision
State the specific condition you believe applies and request confirmation. Do not present an estimated shortfall as an automatically owed amount. If the listing defines exclusions or a minimum drop threshold, address those details before expecting a refill.
Decision checklist
| Decision | What to check |
|---|---|
| Scope | Order and service identifiers |
| Change | Dated metric observations |
| Coverage | Applicable written condition |
Worked example
A hypothetical enquiry says order 123 requested 1,000 units, completed on Tuesday, and the monitored total fell by 120 between two dated checks. It also notes a separate campaign on Wednesday so support can assess attribution rather than assume the entire drop belongs to one order.
Example figures explain the decision; they are not current prices or promised results.