Form Entries, Delivery, and Spam Diagnostics

Step 1: Build the Complete Form
Create only the fields needed for the visitor task and give each one a visible label, expected format, required state, helpful instruction, and useful error. Configure the monitored destination, subject, reply behavior, consent language, retention, spam controls, success message, and failure message before placing the form on a public page.

Step 2: Submit Controlled Test Cases
Complete the form at desktop and mobile with a valid submission, each required field missing, an invalid email or phone value, a long message, keyboard-only input, and a deliberate spam-control failure. The page should preserve useful values, move focus to the problem, explain the correction, and never expose configuration or private server details.

Step 3: Review Entry Evidence
Open Form Entries and match the test submission to its form, time, validation state, consent context, delivery attempt, and final status. Restrict access to people who need the records, avoid placing secrets in message fields, and follow the configured retention, export, and erasure policy.

Step 4: Diagnose Without Guessing
If the visitor saw success but no message arrived, confirm the entry exists, inspect the recorded delivery result, verify the monitored destination and site mail transport, check fresh logs, and test again with a controlled address. Report one reproducible path through I.G.O.R. instead of repeatedly submitting real customer data or disabling every spam control.
