Skip to content
Design-led software studio
Support library

Support library / Technical support

What to include when reporting a problem

The practical details that help the team reproduce a problem and shorten the time to resolution.

Updated

The guidance.

For a question about your own project, raise a request in the client workspace.

You do not need to diagnose the technical cause. A clear description of what you observed is usually more useful than a guess.

Include these details

  • The page, screen or part of the service involved.
  • What you expected to happen.
  • What happened instead, including the exact error wording.
  • When it started and whether it happens every time.
  • Who is affected and the business impact.
  • The device and browser being used, when relevant.

Screenshots and recordings

A screenshot or short screen recording can help, but check it before uploading. Remove customer data, passwords, security codes, payment details and any other information that is not needed to understand the issue.

Reproducing the issue

If possible, list the steps that lead to the problem. Mention anything that changed shortly before it began. Do not repeatedly retry an action if it could create duplicate payments, bookings, messages or records.

Need help with your project?

Sign in to raise a request and keep the answer connected to the work.