Tickets for hosting companies: members verify their billing account (Paymenter, Blesta or WHMCS) before a ticket opens and pick the service or invoice it's about.
Staff get a User info button with the client, their services and unpaid invoices.
Verify with a service ID, or with a Support PIN from our Paymenter and WHMCS extensions.
tickets hosting check (email) shows exactly what the bot finds on the billing panel.
Known issues
Some Paymenter setups refuse the API key (401 / 403) - the error now says why: the key, its permissions, its IP list or Cloudflare.
Blesta and WHMCS are written from their API docs and haven't been tried on every version yet.
Behind Cloudflare, the bot's IP has to be allowed or every check is blocked.
Pterodactyl: members make a panel account or link one they have, and create, list and delete their own servers.
The server owner picks the panel, server types, location, resources, servers per member (and per member with hosting limit), a role and allowed channels.
Email verification with a 6-digit code (hosting smtp setup) - asking for a code never tells anyone whether an email has an account.
Private by design: emails, passwords and keys never appear in a channel; keys are encrypted and locked to their server.
