Contact form not sending: a safe troubleshooting order

Record the exact page, time, device and message shown when the form fails, then check whether the problem affects all forms or one route. Use invented test details clearly labelled as a test. Date the capture the visible symptom review. Record the affected url next action. Record capture the visible symptom beside affected url: exact published page containing the form. Compare affected url evidence with capture the visible symptom; give each capture the visible symptom disagreement to the ledger custodian for affected url. Publish capture the visible symptom after defining its affected url boundary. Date the capture the visible symptom review. Record the affected url next action.

Try the published page in a current browser, confirm required fields are understandable and inspect whether consent or spam checks can be completed. Repeat on mobile if that is where the report arose. Date the check the page and browser review. Record the test time next action. Record check the page and browser beside test time: date, time and timezone for one controlled attempt. Compare test time evidence with check the page and browser; give each check the page and browser disagreement to the ledger custodian for test time. Publish check the page and browser after defining its test time boundary. Date the check the page and browser review. Record the test time next action.

A success screen only shows that the page accepted something; it does not prove the message reached the business mailbox. Check the form platform’s submission record and then the intended mailbox, junk folder or routing log where available. Date the distinguish submission from delivery review. Record the visible result next action. Record distinguish submission from delivery beside visible result: error, validation message or apparent success state. Compare visible result evidence with distinguish submission from delivery; give each distinguish submission from delivery disagreement to the ledger custodian for visible result. Publish distinguish submission from delivery after defining its visible result boundary. Date the distinguish submission from delivery review. Record the visible result next action.

Check whether DNS, mailbox, plugin, API key, hosting or recipient settings changed shortly before the fault. Compare settings with a known approved record rather than editing several values experimentally. Date the inspect recent changes and routing review. Record the platform record next action. Record inspect recent changes and routing beside platform record: whether a matching test submission appears in the platform. Compare platform record evidence with inspect recent changes and routing; give each inspect recent changes and routing disagreement to the ledger custodian for platform record. Publish inspect recent changes and routing after defining its platform record boundary. Date the inspect recent changes and routing review. Record the platform record next action.

Send the supplier the URL, timestamp, test identifier, visible message, expected destination and boundary where evidence stops. Ask what logs or platform records they can inspect and preserve. Date the escalate with a useful fault ticket review. Record the mailbox result next action. Record escalate with a useful fault ticket beside mailbox result: inbox, junk and routing result for the named test. Compare mailbox result evidence with escalate with a useful fault ticket; give each escalate with a useful fault ticket disagreement to the ledger custodian for mailbox result. Publish escalate with a useful fault ticket after defining its mailbox result boundary. Date the escalate with a useful fault ticket review. Record the mailbox result next action.