Refills, cancellations and order troubleshooting
Check service-specific refill eligibility, partial orders, cancellations and public-target issues. Prepare a useful private support ticket.
All resources →A refill is not the same as a refund
A refill concerns an eligible drop after delivery under a particular service’s rules. A cancellation concerns stopping eligible work; a refund or balance adjustment concerns money and order settlement. These are separate decisions. A refill badge alone does not promise permanent retention, unlimited replacements or a money-back guarantee.
| Situation | First check | What not to assume |
|---|---|---|
| Count decreased after completion | Exact service refill availability and stated period / conditions | That every service includes a refill. |
| Order is still running | Status, target availability and service cancellation option | That delivered work can be undone immediately. |
| Partially completed | Recorded remaining quantity and settlement / support details | That the missing portion means no work was delivered. |
| Wrong target | What was submitted and current provider state | That an already submitted target can always be edited. |
| Deposit or payment issue | Private payment record and applicable terms | That a provider’s refill promise is a cash-refund promise. |
A useful order troubleshooting sequence
- Confirm you are checking an order that belongs to your own account and note its reference.
- Match the order service ID to the intended platform and deliverable, including comment likes versus normal likes.
- Check that the submitted username or full link is correct and the target has not been deleted, made private or restricted.
- Compare order quantity with the listing’s limits and keep target conditions stable during processing.
- Read the current status and available average-time information. An average is not a promised deadline.
- Avoid overlapping orders on the same target while asking Support to investigate delivery or a drop.
- Use private Support for a cancellation, refill or acceleration request. A submitted request is not approval or proof that the provider has performed it.
What to include in a private support ticket
Provide the order reference, a short description of the problem, when you observed it and the service or target detail that appears incorrect. Include relevant baseline and follow-up counts only where they help explain the issue. Never send platform passwords, recovery codes, API keys or session cookies. Keep customer-specific information out of public reviews and shared screenshots.
If your account has no matching order, find the correct reference before requesting an order action. Support cannot verify an order from an unrelated account through a public guide. A normal acknowledgment does not grant cancellation or acceleration eligibility.
Sign in for private Support → · Read the existing service terms →
Drops need evidence and context
A before-and-after total can be affected by new organic activity, other orders, deleted accounts and platform corrections. Record an observation time and explain what else was running. Without isolating these effects, the net decrease cannot be attributed to one service. Missing retention data should remain No data yet rather than becoming a made-up 0%.
Calculate an observed net decrease →Questions before you choose
Can every order be cancelled?
No. The service option and order state matter. Sending a request does not guarantee that a provider can stop work that has started.
Will an acceleration request guarantee a faster finish?
No. Support can review the request, but a provider queue or platform interruption may prevent faster delivery.
Is there one refund period for all services?
No universal period is created by these guides. Consult the current terms, exact service conditions and private Support for the applicable review.