Teach the confirmed product terms, account workflow, privacy practices and escalation route before giving broad access. A practical checklist should show how to process an ordinary order and recognise when a request needs someone else’s authority.
Start with the actual offer
Provide the current plan and credit rules rather than a collection of old promotional screenshots. Explain the difference between subscription duration, simultaneous connections and reseller credits. Ask the new person to work through a sample order using clearly fictional data.
Teach the record-keeping steps
Show how to identify an existing account, record payment separately from fulfilment and update the credit ledger. Explain which details belong in a customer message and which should remain private. Use limited permissions where the system supports them instead of sharing a master login by default.
Make escalation straightforward
Give clear examples of questions staff should not answer from guesswork, such as unconfirmed refunds, permissions or broadcast availability. Provide the appropriate support owner and a concise escalation format. Review real mistakes as process improvements rather than encouraging staff to hide corrections.
