Support is available 24/7 by ticket. What decides how quickly something is resolved is not how urgently the ticket is worded but how much of the diagnosis is already in it. A message with the exact error, the affected address and what changed usually gets an answer instead of a question.
Opening a ticket
Submit from the client area at billing.ahosting.net, which links the ticket to your account automatically. Emailing from an address that is not on the account creates a ticket nobody can immediately connect to your hosting, which costs an exchange.
Choose the right department. Billing questions in a technical queue reach a technician who has to hand them on.
What to include
Five things, and they turn a three-day exchange into one reply.
The exact error message, copied rather than described. "It says there's an error" and the actual text are very different starting points. A screenshot is fine; text is better because it can be searched.
The exact address where it happens. Not "my site". The full URL of a page that reproduces it. An account often holds several domains.
What you were doing. Loading a page, sending mail, running an import.
When it started, and what changed around then. An update, a plugin, a DNS change, a migration. This is the single most useful line in most tickets, and the one most often omitted.
What you have already tried. Saves the reply that suggests it.
Three checks before you open one
These take three minutes and resolve a good share of problems.
Is the account over its disk quota? A full account cannot write, and the symptoms look unrelated: mail stops arriving, uploads fail, forms break, database writes are refused. Several unconnected faults at once is very often just a full account.
Does the domain still resolve here? dig NS yourdomain.com. If it points elsewhere, nothing configured here is being used.
Does it happen in a private window? If not, it is your browser's cache in place of the site.
When to open one immediately
Do not spend an hour diagnosing when several unrelated sites fail at the same moment. One site with a problem is a site problem; four at once is a server or network problem, and working through them individually wastes the time you should spend reporting it.
The same applies to anything you cannot reach at all, cPanel refusing connections, a suspended account, an order that took payment and provisioned nothing.
Never send passwords
Support can reach your account without them, and a password sitting in a ticket thread is a credential in a place it should not be.
If access to something external is genuinely needed. An old host during a migration, change that password to something temporary, provide it, and change it back afterwards. That is ordinary practice.
Be equally careful in the other direction. Support will not ask for your password by email, and a message that does is not from them.
What support can and cannot do
Can: anything about the server and the account, resources, mail delivery, certificates, restoring from a host-side backup where one exists, migrations from another host, and configuration questions.
Cannot, generally: write or debug your application code, fix a third-party plugin, design your site, or recover data you never backed up. A host maintains the environment; what runs inside it is yours.
That last one is worth internalising before you need it. Host-level backups exist for infrastructure recovery and their retention is not chosen around your needs. Creating and restoring backups in cPanel goes into keeping your own.
While you wait
Reply on the same ticket rather than opening another. Duplicates split the history and slow everything down.
If you find more information, add it. If it resolves itself, say so and close it. That is genuinely useful rather than merely polite.
Check spam for replies. Support responses land there often enough that "nobody answered" and "the answer was filtered" are frequently the same situation.
Where else to look first
For onboarding questions, the rest of this section covers most of it, activating your service, requesting a free migration, and testing after migration.
For a broken site, the error log usually contains the answer before anyone else has to look. Understanding cPanel error logs deals with which log holds which failure.
Before sending one, How to Write a Support Request That Gets Solved Fast goes over the five lines that remove three replies.
Ask for the specific thing you need
Onboarding questions are answered fastest when they name an outcome rather than a topic. State what you are trying to achieve, what you have already done, and where you got stuck. A request to help with setting up hosting produces a general reply; a request to point a specific domain at a specific account, having already changed the nameservers, produces an answer. Include the domain and the account name, since almost every useful reply requires both and asking for them costs a full exchange before anything happens.