Keep one brief per client with approved links, quantities, budget and package choices. Confirm each target is public before ordering, place orders in bulk with one line per target, save the returned order numbers against the client, and reconcile wallet charges with orders every week.
1. Write a brief for each client
Before any order, agree and record:
- the exact profile, post or video links, copied from the browser,
- the quantity for each link,
- the package for each link, by name,
- the total budget and who approves changes,
- the dates the campaign runs.
A brief prevents the two most expensive mistakes: ordering for the wrong link, and ordering twice.
2. Check every target
Open each link in a private browser window. If you cannot see it without logging in, the service cannot reach it either. Confirm that:
- the account is public and will stay public during delivery,
- the username has not changed since the brief,
- no other order for the same interaction is running on the same link.
3. Place orders in bulk
In your Boostsy account, bulk ordering accepts one line per order in the form service, link, quantity. Review every line before submitting. Each accepted line returns an order number; paste those numbers into the client's brief.
If your own system places the orders, use the customer API. Send an idempotency key with every order so that a retry after a timeout cannot create a duplicate.
4. Use scheduled delivery deliberately
Schedules repeat an order at an interval. Before you set one, add up the total quantity and total cost across all runs, not just one. Check that the package allows repeat orders on the same link.
5. Track by order number
Use the order number as the reference in every client report and support message. Status meanings are in understanding order status. A status of "needs review" means the outcome is uncertain; do not reorder until support has checked it.
6. Reconcile weekly
Export orders and wallet transactions as CSV from your account. For each client:
| Check | Why |
|---|---|
| Sum of charges equals the brief | Catches unapproved or duplicate orders |
| Refunds and partial credits are recorded | The client is charged only for what was delivered |
| Pending payments are excluded from balance | A pending top-up is not spendable |
| Cancellation requests are followed up | A request is not a completed refund |
7. Keep access separate
- Create one API key per integration and revoke keys you no longer use.
- Enable two-factor authentication on the account that holds the wallet.
- Share delivery reports with clients, never login details or API keys.
- If you resell at scale, a reseller panel keeps each client's customers and payments apart from your own.
8. Report honestly
Report what was ordered and delivered: counts, dates and order numbers. Do not present delivered counts as organic growth. Clients who understand what they bought stay longer than clients who discover it later.