Our average first response time on support tickets is 15 minutes, verified from live ticket data as of 2026-09-30. Simple account questions often get answered faster; a ticket that needs someone to dig into server logs or reproduce a bug can take longer.
If you're waiting on a response right now, live chat and email are also available alongside tickets.
What counts as "answered"
The 15-minute average measures time to first human response, not time to full resolution. A quick account question might be fully resolved in that first reply. Something like a hacked WordPress site or a DNS migration usually needs back-and-forth: the first reply confirms we've seen it and started working, and the fix itself can take longer depending on what's wrong.
If you're dealing with a full outage, don't wait on a ticket to start troubleshooting. Work through my site is down: a 5-minute triage checklist first. Most "down" reports turn out to be DNS caching, a suspended account, or something else you can identify yourself in under five minutes, often faster than waiting for a first reply.
How to open a ticket
Tickets are opened from the portal at portal.flashcloud.com under Support. You can also reach us by live chat or email, but tickets are the best route for anything that needs a paper trail or attachments.
A few things that make a ticket faster to answer:
- State the exact domain or account affected in the first line.
- Include the exact error message or error code you're seeing, not a paraphrase.
- Say what you already tried. If you've already ruled out DNS or checked for suspension, say so, it saves a round trip.
- Attach files if they help explain the issue.
Every ticket is answered by a real person. There's no phone line and no ticket-answering bot in the loop, which is part of why response time varies a bit by complexity: a human is actually reading and reproducing the issue before replying.
Why response time varies
A few factors move a specific ticket's response time away from the 15-minute average:
- Ticket volume. Response times can run longer during peak hours, when more tickets are coming in at once.
- Complexity. Technical issues that need someone to reproduce a bug, check server-side logs, or coordinate a fix take more investigation before the first reply goes out than a straightforward question does.
- Missing information. A ticket that says only "my site is broken" with no domain and no error message needs a clarifying reply before real troubleshooting can start. That round trip adds time that a detailed first message would have skipped.
If billing is involved
If your ticket relates to an unpaid invoice or a suspended account, check why was my account suspended? first.
When to open a ticket
If you've ruled out the common causes (DNS caching, suspension, a known outage) and something is still wrong, open a ticket rather than continuing to troubleshoot alone. Include the domain, the exact error, and what you've already checked. With that detail, most tickets get a useful first response well within the 15-minute average, and you skip the back-and-forth that vague reports require.