Recover the customer contact path while a quote form is broken

Establish the outage window

Record the first reported failure, the last successful marked test and any change made between them. These establish an investigation window, not an exact count of lost customers. Check whether requests were accepted without staff notification or whether the form never accepted them. Preserve saved records and relevant error information before replacing the component.

Choose an alternative that staff can handle

A Wix notification problem can be separate from an unusable form. Investigate the layer that failed. For a temporary route, choose a phone number, email address or alternate form that someone will actually monitor. The customer-facing note should state what works now and what the customer should send, without blaming a provider or exposing internal account details.

Use the receiving evidence your system actually provides. If it stores submissions, inspect the marked record there. Otherwise ask the maintainer to verify server acceptance and the intended receiving destination through supported logs or delivery evidence. A thank-you screen alone is not proof. Wix-specific submission-table names belong to the Wix example.

Source checks: Wix Forms: Troubleshooting · Wix Forms: Choosing Who Gets Notified About Form Submissions

Create a temporary contact route

Make the temporary path specific to the original customer task. A person asking about a roof repair should not land on a generic page with five unrelated options. Keep instructions short and avoid requesting sensitive documents through an improvised mailbox. Assign one person to collect incoming requests until the normal form is restored.

• Replace or annotate the unusable form with the tested temporary phone or email destination.
• Test that destination from a customer device and verify the message reaches the assigned person.
• Review saved submissions from the investigation window and mark genuinely unhandled enquiries.
• Repair the normal form in a controlled copy or maintenance window; test acceptance and notification.
• Restore the normal path, remove obsolete outage notices and retain the incident note.

Avoid claims about unknown lost requests

Do not estimate a lost-lead count from missing emails or traffic alone. Do not promise to retrieve answers that the receiving system never accepted. A temporary phone number with unattended voicemail merely changes the failure point. Avoid silently moving old requests into a new system without preserving their original time and handling status.

Verify recovery at the receiving end

Log the temporary route's test result, genuinely unhandled saved requests and restoration test identifiers. Review whether customers still mention the old notice or broken page. These observations show whether recovery is complete. They cannot establish how many visitors would have contacted the business if the interruption had never happened.

Close the incident with a tested restoration

Keep a compact incident record with the investigation window, affected pages, alternate route and accountable staff member. Include outstanding enquiries and the next review date. When the normal form works, give staff one consistent place to update responses so requests received during the interruption are not forgotten or contacted twice.

Worked example: an illustrative customer journey

For example, a gutter service finds that its form stored three recent requests but stopped emailing alerts. The owner places a tested phone route beside the form and reviews those three records. Two were already handled; one still needs a response.

After repairing notifications, TEST-RECOVER-601 reaches storage and the current inbox. The owner removes the temporary notice and checks the outstanding request. There is no evidence here of every potentially lost visitor, so the incident report records only the verified saved requests and repair tests.

Questions about this task