Start with the context
Tell me what’s happening with the website
You do not need to diagnose the problem before getting in touch. Tell me which website is involved, what you are trying to fix or improve, and anything that makes the timing important.
No passwords, hosting credentials or other sensitive access details are needed for the first conversation.
A useful first message
A few practical details are usually enough
Give me the context you already have. Technical terminology is optional.
- The website: the public URL, if available
- The situation: what is broken, unclear or needs improving
- The timing: any launch, client deadline or business dependency
- Your role: whether the website is yours or you’re contacting me for someone else
If you’re not sure which Kelly Creative service fits, that’s fine. Describe the website, the problem or outcome, and I’ll work out the sensible next step.
01
Direct contact
You deal with Kevin
02
No diagnosis required
Start with what you can see
03
No credentials yet
Secure access comes later
AU
Australia based
Remote support Australia-wide
A useful first message
Give me enough context to understand the job
You do not need to write a technical brief. A few practical details are usually enough to establish whether I can help and what the sensible next step is.
The website
Which site is involved?
Send the URL if the website is publicly accessible.
What is happening
What can you see or need changed?
Describe the problem, concern or piece of work in your own words.
What matters now
Is anything making the timing important?
Include a launch, client deadline, broken feature, performance problem or other dependency.
Your role
Whose website is it?
Tell me whether it is your website or whether you are contacting me on behalf of a client.
The right starting point
Different problems need different first steps
You do not need to choose perfectly. Describe the situation and I can help work out where the job belongs.
Repairs & help
Something is broken or behaving badly
Errors, failed updates, plugin conflicts, layout problems or other WordPress behaviour that needs investigation.
Website audit
You need evidence before making changes
If the condition is unclear, the website feels slow or fragile, or several technical concerns are competing for attention, an audit may be the better starting point.
Agency support
You are a web professional
If this is client work, tell me whether you need technical support behind the scenes, white-label delivery or a clearly introduced specialist. Your client relationship stays yours.
Something else? Not every enquiry fits neatly into a service page. Tell me what you’re trying to achieve and I’ll let you know whether it’s something I can help with.
If you already know you want to talk, you can ignore these routes and use the form below. They exist to help—not to make you diagnose the website yourself.
Send the details
Tell me what you need help with
Start with what you know. I will ask for anything else that is genuinely needed.
- Name and email address
- Website URL, if there is a public site involved
- Your role — whether the website is yours or you’re contacting me for someone else
- The problem or objective in your own words
- Deadline or dependency, when relevant
Security boundary: please do not include WordPress passwords, hosting credentials, API keys, recovery codes or private customer data.
Website enquiry
Send the website context
The form should collect only the information needed to understand the enquiry and choose the next step.
Before you send anything
No diagnosis, proposal or login details required
“Here is the website. This is what is going wrong. This is what I need to achieve. This is when it matters.”
That is enough to start.
Common questions
What you need to know before getting in touch
These are the boundaries that matter at the first-contact stage.
Do I need to know what is causing the problem?
No. Describe what you can see, what changed or what you are trying to achieve. Investigation is part of technical WordPress work.
Should I send my WordPress login?
Not initially. Please do not send passwords or credentials through the contact form. I will tell you what access is needed if we decide to proceed.
Can I contact you about a client website?
Yes. Include your role and how you want the working relationship handled. Support can be behind the scenes, white-label or clearly introduced where appropriate.
What if the problem is urgent?
Tell me what has happened, what is currently blocked and any genuine deadline or dependency. I can then tell you whether I am able to take it on.
What if my enquiry does not fit one of these services?
That is fine. Tell me what you are trying to achieve or what is happening with the website. You do not need to choose a service before getting in touch; I can tell you whether the work fits Kelly Creative and what the sensible next step is.
Start with what you know
Send the website, the situation and the outcome that matters
You do not need to solve the technical problem before asking for help. The first useful step is simply enough context to decide what happens next.