WEBSITE OR APP REPAIR BRIEF

Use this with your hosting provider, developer or Turing Websites.
Keep passwords, API keys, payment details and customer records out of this brief.
Share account access separately through an agreed secure route.

Website URL or project name:
Your name and contact email:
Business name (optional):

Is the project live or preparing to launch?
Are customers affected now? Which actions still work?

Affected feature:
What should happen?
What happens instead?
Exact error (redacted):
Steps that show the problem (avoid repeated live payments or messages):

First noticed (date, time and timezone):
Last known working (date, time and timezone):
Recent changes or deployments:
Provider incidents or support reference:

AI builder or website platform, if known:
Hosting provider:
Database provider:
Payment, email or booking services involved:

Available source code / repository history:
Available database backups and dates:
Uploaded-file backups and dates:
Accounts you own or administer (names only, no credentials):

Changes or fixes already attempted, with times and results:

What must work after the repair?

Keep the current code, relevant logs and available backups before changes.
Agree what a restore affects and how later customer activity will be preserved.
For an active outage, contact your provider's support.
For suspected compromise or exposed data, use the provider's security support
and your incident-response specialist promptly.

Guide: https://turingwebsites.com/blog/what-to-do-when-your-website-or-ai-app-breaks
Website repair: https://turingwebsites.com/services/website-repair
AI app rescue: https://turingwebsites.com/services/ai-app-rescue