Guide Billing & Account

How to open a support ticket that gets answered

A ticket that includes five specific things gets solved far faster than one that just says something is broken.

iFastHosting Support Team Updated 26 August 2026 5 min read Beginner

The fastest support reply is the one that does not need a follow-up question first. Most delay in getting a problem fixed is not support being slow to look — it is a first message that says "my site is broken" and a second message, sometime later, that asks what "broken" actually means. Five specific things in your first message avoid that entire round trip.

The five things worth including every time

Include	Why it matters
The domain or service	Support needs to know exactly which account and site you mean before they can look at anything.
The exact error text	"It's not working" describes nothing. The precise wording or error code points straight at the cause.
The exact time	A timestamp lets support match your report against server logs, which is often how the actual cause is found.
What changed recently	An update, a new plugin, an edited file — most problems start immediately after something changed, and naming it saves guessing.
What you already tried	Stops support suggesting the first three things you already ruled out, and shows them where you actually got stuck.

Name the domain or service precisely

If your account has more than one hosting service or domain, say exactly which one the ticket concerns. "My website" is ambiguous the moment there is more than one; the full domain name is not.

Quote the error exactly, do not paraphrase it

"It shows an error" and "it shows a 500 Internal Server Error" send support down completely different paths. Copy the exact wording, including any error code, rather than summarising it in your own words — a summary can accidentally drop the one detail that would have identified the cause immediately.

A screenshot says more than a description

If the problem is visual — a broken layout, an error page, a message in a control panel — attach a screenshot rather than describing it. It removes any ambiguity about what you are actually seeing, and it often shows details you would not have thought to mention.

Give the exact time, not "earlier" or "just now"

"It happened this morning" is not precise enough to match against a server log; "around 9:40am UK time" is. If you noticed the problem rather than watched it happen, say when you noticed it and be clear that this may not be the exact start time — that distinction matters to whoever is reading the logs.

Say what changed

Most problems have a trigger: a plugin update, a theme change, a new piece of code, a DNS edit, a payment method update. If you made any change — even one that seems unrelated — shortly before the problem started, mention it. Correlation is not proof, but it is usually the fastest lead support has to work from.

List what you have already tried

If you have already cleared your cache, tried a different browser, or checked that a payment went through, say so. It stops support suggesting the same first steps back to you, and it also tells them something useful: that the problem survives basic troubleshooting, which usually means it is not the first thing it looks like.

Do not worry about sounding too technical or not technical enough

You do not need to diagnose the problem yourself before writing to support — that is their job. What helps is describing exactly what you saw, when, and what you had just done, in your own words. A precise plain description beats a guessed technical one every time.

Billing questions need slightly different details

For a billing question rather than a technical one, the equivalent specifics are the service name, the invoice or order number if you have it, and exactly what looks wrong — an unexpected charge, a missing refund, a price that does not match what you expected. The same principle applies: specifics over general descriptions get a specific answer back.

Where to send it

Contact us to open a ticket or find the right channel for your question. If your account is suspended and you cannot access your usual ticket system, use the email option on that page instead so the message still reaches support.

One ticket, one issue

If you have two unrelated problems, raise two tickets rather than combining them into one. A single ticket covering both a billing question and a technical fault tends to get only the first one properly addressed, since it is easy for the second to be read as a secondary note rather than a separate request needing its own answer.

None of this is complicated, and it takes barely any longer to write a ticket this way than to write a vague one — the difference shows up entirely in how many replies it takes to reach an answer.