A good website support request does not need technical language. It needs a clear description of what you were doing, what you expected to happen and what happened instead.
Start with the page and the task
Include the address of the affected page or website. Then explain the task in ordinary language: submitting an enquiry, updating an event, taking a payment, signing in or sending an email.
If the issue affects one particular customer, order or form entry, include its reference number where appropriate—but avoid unnecessary personal information.
Describe what happened
A short sequence is usually enough:
- What you clicked or entered.
- What you expected the website to do.
- What appeared instead.
Copy the exact error message when there is one. A screenshot is useful when it shows the entire browser window, including the page address. Mention whether the problem happens every time, only on mobile, or only for one user.
Choose urgency carefully
Critical means the website is offline, appears compromised, cannot take essential enquiries or payments, or is causing a serious business interruption. A spelling correction, new photograph or routine content change is important, but it is not usually critical.
Keep the conversation in one ticket
Add new information to the existing ticket rather than opening another one. That preserves the history and prevents two investigations of the same problem.
Never paste passwords, recovery codes, API keys or payment details into a ticket. Grey Lily Media can arrange a safer access method when access is required.
What happens after you submit
Your request is logged with its date, priority and conversation history. Grey Lily Media can then reproduce the issue, check recent changes, inspect logs or ask for one specific piece of missing information.
Support requests are normally reviewed within one business day. Critical issues are assessed first, but choosing Critical for routine work does not make the work faster—it makes the queue less useful for everyone.
A simple support-request checklist
- The affected website or page address.
- The task you were trying to complete.
- The actual result and expected result.
- The exact error message or a useful screenshot.
- How urgent it is and why.
That is enough. You do not need to diagnose the cause before asking for help.
Need help with this?
Clients can open a secure support request and keep the conversation in one place.
Keep reading
The Myth of Removing Every Barrier: When Website Friction Helps
Not every extra step on a website is a problem. Price signals, qualification questions and booking rules can improve customer fit and trust when each one has a clear job.
Read article
How Do You Know Whether Your Website Is Actually Working?
A practical guide to measuring whether your website produces qualified enquiries, calls, bookings or sales, without mistaking vanity metrics for business results.
Read article
How Should Your Website, Google Business Profile and Social Media Work Together?
Your website, Google Business Profile and social media have different jobs. Here is how to keep them accurate, connected and focused on meaningful customer actions.
Read article