A contact form that actually reaches you: an OffPress testing checklist
A visitor fills out your contact form, sees a thank-you message, and leaves. From their perspective, the job is done. From yours, there are still important questions: was the response saved, did the right person receive a notification, and is there a clear place to reply?
Treat those as separate checks, not one event. This practical walkthrough is for business owners and creators setting up an enquiry form or checking one after a website migration. It follows the current OffPress forms and submission routing guide. Labels and available controls can differ on older or customized sites.
1. Decide what the form is for
Write a one-sentence purpose before changing any settings: “Help prospective clients ask about a project,” for example. Then choose only the fields needed to handle that request. A general enquiry might need a name, reply email, and message; a project enquiry might also need a service choice. Avoid collecting information simply because you might use it someday.
Keep a contact request separate from a newsletter signup. Someone asking about your services has not thereby given permission to subscribe them to marketing emails. Make the form’s purpose clear in its heading, field labels, and confirmation message.
2. Check the form and its actual page
Open Content Admin → Workspace → Forms. Review the form’s fields, required-field rules, and the message under After submission. Save your changes. Creating a form does not automatically place it on a website page; ask in Site Design to add it at the intended location if it is not already there.
Visit the actual page on desktop and a phone. Check that labels remain readable, fields are usable, and the submit button is easy to find. A form that looks correct in an editor still needs testing where visitors will use it.
3. Make notification delivery explicit
In the updated form editor, go to Notifications → Email submissions to. Enter the address of the person or shared mailbox that should receive enquiries, then save. This address is private to site staff rather than displayed to visitors. Read the routing summary above the settings to confirm the intended destination.
Do not assume leaving the address blank disables notifications. For contact forms, the documented behavior is to keep the site’s existing notification address, falling back to the workspace billing email if no site address is configured. Newsletter signups behave differently: a blank address means no standard notification email. Choose deliberately rather than relying on a blank field.
4. Choose Inbox routing separately
Newsletter subscription, notification email, and Inbox conversations are separate actions. Under Notifications, review Add to newsletter audience and Create an Inbox conversation independently. For a normal enquiry form, check that the audience setting reflects its contact purpose rather than treating every sender as a subscriber.
The documented Inbox choices are automatic routing for contact messages only, always requesting a conversation, or no conversation. These settings do not activate the Inbox plugin. Enable Inbox separately if you want to handle conversations there. If your form lacks these controls, ask OffPress to check its installed form version instead of assuming the routing changed.
5. Run a complete test, not just a successful click
Use an email address you control and a distinctive message such as “Contact form check — please ignore.” Record the page and test time so you can identify the response. Then check each outcome:
- Validation: try an empty required field or invalid email. The form should explain the problem rather than claim success.
- Confirmation: submit valid details and check that the success message appears only after the submission succeeds.
- Saved response: locate the test in the relevant submission view. With Inbox available, check Inbox → Conversations and the Forms channel for routed messages. Without Inbox, Content Admin can show retained Form submissions.
- Notification: confirm the intended mailbox received the email. A saved response is not proof of email delivery.
- Audience: for a dedicated newsletter signup, check Email → Audience. For an ordinary contact enquiry, confirm that the sender was not unintentionally subscribed.
If notification delivery fails, check whether the response was saved before asking anyone to resubmit. If duplicate notifications arrive, review Advanced email settings → Additional email templates as well as the standard notification settings. Changing routing applies to new submissions; it does not automatically reroute older responses.
6. Repeat the check before a migration goes live
An imported form may still depend on an old service. Its familiar appearance is not evidence that its submission connection works on the rebuilt website. Test the whole flow before moving your domain, and repeat it on the live address after launch or after a meaningful form change.
Keep a short record: form URL, purpose, notification recipient, expected Inbox or Audience behavior, test date, and result. Add that record to your monthly website content review so the form remains part of website maintenance, not a one-time launch task.
For current controls and setup details, use the forms guide or browse the OffPress documentation. The goal is simple: every useful enquiry should have a verified destination and a clear next step for your team.