Use support tickets for account and technical help

Support tickets are the durable channel for anything that is not answered by the marketing site or this blog: billing mismatches, access problems, DNS you cannot untangle, VPS not provisioning, and feature questions. Chat-style DMs are great for quick hellos, but tickets preserve timestamps, staff replies, and resolution history—which matters when you need to reference “what we agreed last Tuesday.”

Open a ticket the right way

From the dashboard, go to Support → New ticket. The subject should be specific: “Wallet top-up REF123 not credited” beats “Help!!!”.

In the message, use a simple structure:

• Goal — what you were trying to accomplish\n- Steps — what you clicked or ran, in order\n- Expected — what should have happened\n- Actual — error text, blank screen, or wrong number\n- Identifiers — domain name, order ID, instance label, approximate time

If file uploads are not available, describe screenshots in words or host them somewhere safe and link (only if you trust the URL).

One thread per issue

Do not open three tickets for the same Paynow problem—it fragments context. Reply on the original thread with new information (“bank sent receipt at 14:05”).

If a ticket is closed and the issue returns, open a new ticket referencing the old ID. Reopening semantics vary; when in doubt, new ticket + link.

How staff work behind the scenes

Agents may need to reproduce your issue or query registrar/cloud APIs. That takes longer than a single chat bubble. Silence does not mean ignore—it often means investigation.

Urgent subject lines (Production site down, Suspected unauthorised order) help triage. Still include details in the body; urgency without facts slows everyone down.

After resolution

When fixed, confirm on your side before assuming. For DNS, flush local cache or test from an external resolver. For payments, verify wallet ledger lines.

If you are satisfied, you can close the ticket when the UI allows, or simply thank staff and let them close it.

What tickets are not

They are not a substitute for reading error messages or checking spam first. They are not instant phone support unless we advertise that tier. They are the right place for anything account-specific that requires human eyes on our side.