How to Get Support, and How to Get It Fast Print

The one principle

Every hour we spend asking what the problem actually is delays the fix by that hour. The difference between slow support and fast support is almost never effort on our side, it is information in the first message: what you did, what you expected, and what happened instead. This article shows you the channels and, more valuably, what to put in the first message so the first reply is the fix.

Support tickets: the main channel

Open a ticket from the client area, logged in, so the ticket is attached to your account and services from the start. Tickets are the right channel for almost everything: technical problems, billing queries, changes you want made, and anything that benefits from a written record. They reach the people who can act, they hold their history, and nothing gets lost in a chat scrollback.

WhatsApp: the critical line

Our dedicated support WhatsApp is +27 72 270 9321, and it exists for when things are genuinely on fire: a server down, email failing, your connection to us blocked, or your particular corner of the world blowing up. If it is critical, we will handle it there, day in, day out.

Three rules keep this channel fast and safe, and they apply to everyone:

• Support only. No orders and no account changes happen via WhatsApp, ever, those run through the client area and tickets, where they are verified and recorded. This is a security measure, not bureaucracy: a chat message asking us to change your account is exactly what an attacker impersonating you would send.
• We verify who you are. Tell us your name and your account or domain, and if the details do not match what is on record, we will not proceed, and will require an email from the official account holder before going further. If that ever happens to you, it is the system protecting your account, not doubting you.
• Only this number is us. As our security articles note, password resets and support contact come from this Business WhatsApp and nowhere else, any other number claiming to be Linuxweb is not Linuxweb, treat it as phishing and report it.

For everything not burning, tickets remain the better channel, they hold their history, attach to your account, and never compete with a phone's notifications.

What to put in the first message

• The domain involved. First, always. We host hundreds of domains, and everything starts from which one is yours.
• The exact error, exactly. Copy the full message or screenshot it, paraphrased errors lose the code that identifies the cause, our Email Errors articles show how much a single line like a 550 or 554 reveals.
• What you were doing when it happened, sending from Outlook, editing DNS, uploading files, and roughly when, timestamps let us find the moment in the server logs.
• What you have already tried, so nobody repeats it, including anything a knowledgebase article had you check.
• What changed recently, new device, password change, domain move, new plugin, in our experience the answer hides in this line more often than any other.

A ticket carrying those five things is routinely solved in one reply. A ticket saying "email is broken" is solved in five, four of which are questions.

Before the ticket: the two-minute checks

• Search this knowledgebase for the error message or symptom, these articles exist because the same twenty problems account for most tickets, and the fix may be one search away.
• Check whether it is just you: downforeveryoneorjustme.com answers it in seconds, and if the site is up for the world but not for you, our article on website access issues explains the IP bans that cause exactly that, and why WhatsApp is the channel for them.
• Try webmail when the problem is email, if webmail works, the mailbox is healthy and the problem is a device or program, which changes the whole diagnosis, as our Email articles show throughout.

None of this is a toll gate, skip it all and open the ticket, but the checks catch a good share of problems before a ticket is needed at all.

What to expect from us

Tickets are answered by the people who run the servers, not a first-line script, which is why the detail in your first message lands so directly on the fix. Order processing follows the rhythm described in our article on what happens after you place your order, and anything security-related follows the policies our security articles set out, password resets via Business WhatsApp among them. When something on our side genuinely breaks, the fastest truth we can tell you is in the ticket queue and our status updates, and honesty about a problem beats silence every time, that is a commitment, and you may hold us to it.

Good to know

The support system also works in reverse: when you spot something wrong that does not affect you, a typo in an article, a link that dies, something in cPanel behaving oddly, a ticket about it is genuinely welcome. Three hundred clients see more than we can, and half the improvements in this knowledgebase started as somebody's passing observation.