Arabic Hosting Support: How to Write Your Request and Pick the Channel That Gets It Solved Faster

Most of the delay in fixing a hosting problem does not come from the first reply. It comes from the back-and-forth where support asks for your domain name, the error message and when the problem started. A complete request sent through the right channel cuts out those rounds and gets you to a fix sooner. This guide gives you a template to copy, rules for choosing a channel and a way to follow up without slowing things down.

Pick the channel for the situation

Why a ticket for technical problems? It keeps the whole history in one place with its attachments, so nothing has to be re-explained if another engineer picks it up, and you keep a written record of what was agreed. Phone and WhatsApp are good for raising the alarm on something urgent; move the details into a ticket straight after.

EngHosting's channels are phone and WhatsApp on +201121552051, email at support@enghosting.com, support tickets and the client area. All of them are listed on the contact page.

Seven things every request should contain

• Service and domain: the domain name and the type of service, such as shared hosting or a VPS, so support goes straight to the right account.
• The exact URL: the page where the problem appears, not just the home page.
• The error message, word for word: copy the text exactly, and attach a screenshot in addition to the text, not instead of it.
• Timing: when it started, whether it is constant or intermittent, and from which device or network.
• The last change: a plugin update, a DNS edit, a site migration, a PHP version switch. Most faults start right after a change.
• What you have tried: so you are not asked to repeat steps you have already done.
• Impact: the whole site, one page or one user. This sets the request's priority.

A template you can copy

• Subject: 500 error on the checkout page of example.com since this morning.
• Service: shared hosting, domain example.com.
• Problem: clicking "Place order" shows "Internal Server Error"; every other page works.
• Started: today at about 10 a.m.; happens on every attempt, on more than one device.
• Last change: I updated the payment plugin last night.
• Tried: cleared the cache and disabled the caching plugin; no change.
• Impact: customers cannot complete orders.

If you write in Arabic, keep error messages and technical names in their original English form. Translating "Internal Server Error" or a plugin name makes it harder to search logs and documentation for the exact string.

What to prepare for each type of problem

• Email: the full bounce message as you received it, the sender and recipient addresses, and the time it was sent.
• Domain and DNS: the domain, its current nameservers, and any record you changed and when.
• Slowness: the URL, the times it happens, a speed test result if you ran one, and whether it happens only on your network.
• Suspected hack: do not delete files before reporting it, and change your passwords as described in our website security checklist.
• Restore request: the date you want to go back to, and whether you need files, a database or email. What you can restore yourself is covered in our cPanel backup and restore guide.

Never paste passwords into chats

If support needs access to your site's admin panel, ask which secure method they use rather than typing the password into WhatsApp or a plain email. If you must share access, create a temporary account with limited rights, or change the password as soon as the work is done.

Following up and escalating without slowing things down

• One problem per ticket; mixing two unrelated issues slows both.
• Add new information as a reply in the same ticket instead of opening a new one for the same issue.
• If you phone about an open request, give the ticket number first.
• If the wait is long, ask in the same ticket for an update and a time estimate, and ask for escalation when the impact is serious.
• Do not confirm the ticket as resolved until you have tested the fix yourself.

Know where support stops

On shared hosting, server and platform problems are the host's responsibility, while your site's code, plugins and theme are yours, although support can usually point you in the right direction. On a VPS or dedicated server, EngHosting's acceptable use policy makes the server the customer's full responsibility once the login details are delivered, and managing it from the inside is a separate paid service. Knowing this split saves you waiting on a request that falls outside the included support, and lets you ask for the right service from the start.

If you have not bought yet and are still comparing providers, read how to test a host's support before you buy. For the rest of the series, see our Arabic website hosting guide.

Useful links: Shared Hosting, Linux VPS, Domain Registration, Contact Us.