Hand an unresolved AI investigation to our support team with the findings and exact changes already attempted. A concise evidence record helps us continue from the current state without repeating work or accidentally reversing a useful correction.
IN THIS ARTICLE
01 Preserve the session findings
Record the selected service and website, original symptom, time of failure and relevant activity entries. The Engineer conversation is tied to the current browser session, so preserve the useful summary before starting a new chat or closing the tab. Do not rely on an open chat as the site's permanent maintenance record.
02 Prepare the support handoff
- State the expected behaviour and the smallest set of steps that reproduces the problem.
- Summarise what the Engineer observed, separating evidence from its suggested explanation.
- List changes you approved and whether each completed, failed or was undone.
- Identify the latest verified backup and whether new business data has arrived since it was created.
- Attach only relevant redacted errors or screenshots through the authorised support channel.
- Explain the business impact and any time-sensitive workflow affected.
Should I keep asking the AI to try different fixes?
Not when the investigation is repeating itself, the cause is unclear or the required operation exceeds the available tools. Pause further changes and preserve the current state. Additional speculative edits can make the original issue harder to isolate.
What information should stay private?
Do not include passwords, API keys, private payment links or unnecessary customer records. Support can request a secure access method if additional access is needed. A redacted log excerpt with the timestamp and error is usually more useful than an entire secret-bearing configuration file.
What if credits ran out before the task finished?
State where the task paused and what was already verified. Running out of allowance does not mean the last proposed change was applied, so check the activity result. Support can review the technical issue without assuming that a new credit purchase is the solution to every interruption.
03 Confirm the recovery scope
If an Undo or restore was used, describe exactly what it covered. File Undo does not automatically reverse database or external actions. Keep the site in the agreed operational state while support investigates, and repeat the original business test after the eventual fix is confirmed.