Make the support report explain what the person could not finish

“The store is broken” may mean the product page is unavailable, the transaction is unresolved or a completed order is missing from a staff view. Each observation needs different evidence and may involve a different account owner.

Keep enough context to investigate

Record the affected route, action, device, approximate time with its zone and visible result. Include a safe reference where appropriate. Do not send customer exports, credentials or payment details through an ordinary message. An agreed controlled channel can be used if investigation requires sensitive evidence.

Distinguish the public display from the underlying record. A stale browser label, a delayed provider event and a failed import should not all be reported as an absent order. Preserve what staff actually observed before attempting a recovery.

Identify the authority for a correction

The code maintainer may not control the merchant account, approved Spanish wording or invoicing decision. The support record needs the person who can resolve that dependency. A technical fix must not silently change a commercial promise to make a queue disappear.

Define the window and the handover

Agree covered components, hours, time zone, urgency, contact route and the next owner outside coverage. Faith Forge Labs' US-based delivery does not establish continuous local on-call service. A proposed support window belongs in the project agreement.

Verify the recovered job

After a correction, return to the affected request, document or order. Check the actual relationship and an unaffected control. A restored homepage cannot establish that uploaded documents or new records survived a recovery.

Read maintenance scope and launch support planning. Discuss the recurring failure to define an investigation and continuing arrangement that fit the real operation.