Start with the problem

Tell me what’s happening with your website.

Share the URL, symptoms and urgency. A real person will review the request and use those details to understand the next step.

Your request is reviewed manually. No automated diagnosis runs after submission.

Before you send

The best request describes the behaviour—not a guessed solution.

Useful details to include

  • What you expected to happen and what happens instead.
  • When the issue started and whether anything changed just before it.
  • The exact error message, affected page or device where possible.
  • Whether the website, checkout, security or customer communication is currently affected.

Do not send passwords, recovery codes, payment details, API keys or other secrets through the public form. If access is needed after the initial review, a safer exchange method can be agreed.

What happens with your message

It is emailed to the configured WebDiagnose support recipient. Authenticated SMTP should be configured and tested before launch.

Website support request

Manual review
0 / 5000

Do not include passwords, API keys, payment details or other secrets.

A real person will manually review the website and the problem you describe.

After you submit

A short path from request to a useful next step.

Submitting the form does not create a charge or authorize changes to the website.

  1. 01.

    Review

    The URL, symptoms, impact and urgency are read by a person.

  2. 02.

    Clarify

    A focused follow-up question may be needed before access or scope is discussed.

  3. 03.

    Agree the next step

    Availability, investigation, repair scope and any cost are confirmed separately.

Before you ask

Need to know about access, pricing or emergency support?

Read the FAQ