Skip to content

Reseller operations

Manage reseller customers without turning WhatsApp into your database

A reseller panel can create or extend accounts. It does not replace a reliable record of who paid, which username belongs to whom, when service expires and what follow-up is due.

Keep the smallest useful customer record: identity, contact channel, source, package, verified payment, linked service username, activation, expiry and next action. Protect credentials separately.

The five operational queues

  1. New enquiries: qualification and next reply.
  2. Trials: reserved, delivered, expired or needs review.
  3. Payment review: never mark paid from a screenshot or customer statement alone.
  4. Active customers: linked username, verified expiry and support history.
  5. Renewals: due soon, renewed, expired or unable to reach.

Separate conversations from records

WhatsApp is useful for a customer-initiated sales conversation, but messages can be deleted, numbers can change and access can be interrupted. Store the commercial facts in one Sales Core and keep WhatsApp optional to the operating system.

Protect the fields that matter

  • Do not put usernames, passwords or full M3U links in analytics.
  • Limit credential access and encrypt stored secrets.
  • Keep payment evidence separate from payment verification.
  • Use a stable customer identifier instead of merging people only because names look similar.
  • Record the source as Unknown when a tracking reference is absent or altered.

A daily 15-minute routine

Work only the exceptions: new reseller leads, payments awaiting verification, unlinked usernames, failed deliveries and renewals due soon. Reconcile the reseller panel balance after fulfilment and stop obsolete follow-ups when a verified renewal is linked.

Continue the reseller learning path

Review how credits are allocated, model costs in the margin calculator, then compare the approved packages on the reseller pricing page.