A contact form can look fine and still lose inquiries. The page may accept a message while the email behind it lands in spam, goes to someone who no longer works there, or cannot be answered with the reply button. None of that shows on the website. The dependable check is to send an inquiry yourself and follow it until a reply reaches you.

How a form message gets from the page to a person

When someone presses send, the browser passes the entries to a program on your web server or to a form service. That program checks them and usually turns them into an email or a help desk ticket. The thank-you message often means only that this handoff worked. The notes in WordPress’s own code for its built-in mail function, wp_mail, say as much: a true result does not automatically mean the email was received, only that the request was processed without errors.

Google’s troubleshooting guide for missing contact form messages says the form itself is usually not the cause; the root cause is often how the form’s mail is authenticated. A form that sends email is a sender for your domain and has to be authorized like any other, typically through SPF, DKIM or an SMTP relay that signs in with a username and password. When that is missing or out of date, Gmail may mark form messages as spam or reject them.

Two addresses on that email matter. The From address should be one on your own domain that the form is allowed to send as, such as a dedicated website address. The visitor’s address belongs in the Reply-To field. The internet message standard, RFC 5322, says Reply-To indicates where the author suggests replies be sent and that, without it, replies go by default to the From address.

Some forms put the visitor’s address in From instead. That message claims to come from the customer’s own email provider, which never authorized your website to send for it. Gmail’s sender guidelines tell senders not to impersonate other domains or senders without permission, call the practice spoofing and say Gmail might mark such messages as spam. They also tell every sender not to impersonate Gmail From: headers, which is what the form does whenever a visitor types a Gmail address.

WordPress has a trap of its own. When neither the form nor a plugin sets a From address, WordPress sends as wordpress@ followed by the site’s domain. A comment in WordPress’s code notes that some hosts block outgoing mail from that address if no such mailbox exists.

Set up the test

Use an email address you control that is outside your company, such as a personal account, so you see what a customer sees. Use test details only, never real customer information. Choose a short identifier, such as “Website form test Wednesday,” and keep notes as you go. Record these details:

  • The form’s page address and how you reached it from the home page.
  • The time you pressed send, to the minute, plus the phone and address you used.
  • Where the inquiry should land and who is supposed to answer it.
  • What happened at each step, including anything that looked odd.

Decide whether to warn the team. If you tell the people who watch the inbox, you are testing the plumbing. If you do not, you also learn whether a new inquiry gets noticed, who answers it and how long that takes. Either way, tell the person who maintains the site so they know to expect a test.

Fill it in on a phone

Open your website on your phone and find the contact form the same way a customer would, starting from a search for your business or from the home page rather than a saved link. Turn off Wi-Fi so the test does not depend on the office network. If you can, repeat it later on both an iPhone and an Android phone.

Fill in the required fields with test details and a message labeled “Website form test” plus your identifier. As you type, watch for these problems:

  • The phone keyboard or a sticky banner covering the field you are typing in.
  • A chat button or cookie notice sitting on top of the send button.
  • A send button that is hard to hit with a thumb.
  • Required fields that are not marked until you press send.
  • A spam check that does not let you through on the first try.

WCAG 2.2, the W3C accessibility standard, covers several of these. Its Labels or Instructions criterion requires labels or instructions wherever content needs input. Focus Not Obscured (Minimum) asks that a control receiving keyboard focus is not entirely hidden by content the site adds, and Target Size (Minimum) sets a minimum of 24 by 24 CSS pixels for targets people tap or click, with some exceptions. Ask the site maintainer to check the form against those criteria by name.

Try one mistake a real customer might make

Before sending the real test, press send with a required field left empty. WCAG 2.2 sets a baseline here: under Error Identification, a form that detects an error must identify the field and describe the problem in text, and under Error Suggestion it should offer a correction when one is known. A red outline with no words does not meet that. Next, type an email address without the @ and see whether the form catches it.

On a phone, check whether you can reach the send button with the keyboard open and whether you can correct an error without retyping the whole form. Then fix the errors and submit the valid test only once, so there is one clean message to follow.

Follow the message

Note what the page shows after you press send. A good confirmation says the message went through and what happens next. A blank page, an error code or the same form shown again needs a look from whoever maintains the site.

A confirmation on the page is only half the check. Open the inbox or help desk where the inquiry should land and look for the test. When it arrives, check these points:

  • It reached the right team or queue, not one person’s own mailbox.
  • Every field you filled in appears, including your phone number.
  • The subject line makes clear it came from the website form.
  • It is in the inbox, not in junk or quarantine.

If it is missing, check spam and the form’s delivery settings, then ask the person who maintains the site to review delivery logs. Give them the identifier, the time and the address you entered so they can trace it.

Check the full trip including the reply

Press Reply and read the To line before typing anything. It should show the address you entered on the form. Then send a short reply from the business mailbox the way staff normally would, and confirm it reaches your test inbox, outside the spam folder, from the address customers should see.

A form can deliver successfully and still make it difficult to reply if the sender and reply address are configured incorrectly. Each of these patterns points to a specific setting:

  • Reply goes to a no-reply or wordpress@ address, because the visitor’s address was never set as Reply-To.
  • Reply goes back to your own business address, because Reply-To holds a fixed address instead of the visitor’s.
  • The From line shows the customer’s address, so the form is sending in their name and delivery may suffer.
  • Reply works, but the answer leaves from one person’s mailbox instead of the shared address.

When the test never arrives

Work the problem from both ends. While the site maintainer checks the form’s mail settings and sending service, your email administrator can search the receiving side using the time and addresses you recorded.

In Microsoft 365, an administrator with the Exchange Administrator role opens the Exchange admin center, goes to Mail flow, then Message trace, and selects Start a trace. The default search covers all senders and recipients for the last two days, and you can type specific addresses, such as the form’s sending address or your test address, into Senders or Recipients. Ranges of 10 days or less return a Summary report almost at once; longer ranges, up to 90 days, come back as downloadable reports that can take several hours.

Each message in the results shows a status such as Delivered, Failed, Pending, Quarantined or Filtered as spam. Microsoft notes that the reported status can lag actual delivery by five to ten minutes, so a test sent moments ago may still show Getting status.

In Google Workspace, Google’s contact form guide points administrators to Email Log Search to find form messages that were not delivered as expected. Google’s help article Find messages with Email Log Search places the tool in the Admin console under Menu, then Reporting, then Email Log Search, says it requires the Gmail Settings administrator privilege, and allows searches by sender, recipient, subject or message ID within the past 30 days.

If the log shows error 550-5.7.26, which rejects unauthenticated mail under the domain’s DMARC policy, Google says your SPF record may not include every sender for your domain. Its guide suggests checking the record with the Google Admin Toolbox.

Release a quarantined test if needed, but fix the sender setup: authorize the form’s sending service in your domain’s SPF or DKIM records, or have the form sign in to an SMTP relay. For WordPress sites having trouble with the Contact Form 7 plugin, Google’s guide suggests trying the WP Mail SMTP plugin. Asking staff to check junk folders for inquiries is a workaround, not a repair.

Decide who owns the next reply

A delivered inquiry still needs a person. Send the form to an address that belongs to the business rather than to one employee, so it keeps working through vacations and departures. Then write down who watches it, who covers when that person is away, and how quickly a first reply should go out. A shared inbox works best when everyone knows those three answers.

In Microsoft 365, the usual tool is a shared mailbox, which Microsoft suggests for support addresses and reception or front-desk mailboxes. It can hold up to 50 GB without a license of its own, though each person who uses it needs a licensed Exchange Online mailbox, and members with the right permissions can send as the shared address. Microsoft says to block sign-in for the shared mailbox’s own account and keep it blocked, and it notes that you cannot prevent members from deleting messages there, one more reason to agree on how inquiries are handled.

In Google Workspace, a Google Group set up as a Collaborative Inbox adds ownership tools once a group owner or manager turns them on. Members with the permission Google calls Who can moderate metadata can select Take to claim a conversation or Assign to give it to someone else, who gets an automated email notice. Conversations can be marked complete, no action needed or duplicate, and a search can show only those that are not assigned or are still unresolved.

If the form creates help desk tickets instead, the same questions apply to the queue. Confirm the test ticket landed in a queue someone watches, that it was assigned to a person, and that the reply from the ticket reached your test address.

A worked example

Imagine a twelve-person landscape design firm whose website form sends to the office manager’s own mailbox. On a Wednesday morning she runs the test from her phone on mobile data, labels it “Website form test Wednesday,” and notes the time. The page says thank you, but nothing appears in her inbox.

She finds the test in her junk folder. The From line shows her personal test address, so the form is sending in the customer’s name. Because the visitor’s address sits in From, pressing Reply still reaches the customer, which is why nobody suspected a problem: inquiries that reached the inbox could be answered, and nobody saw the ones in junk.

The site maintainer switches the form to send from a website address on the firm’s domain, authorizes its mail service in the domain’s SPF and DKIM records and puts the visitor’s address in Reply-To. The form now goes to a shared mailbox the office manager and a project coordinator both watch, with the coordinator named as cover. A second test that afternoon lands in the inbox, and her reply from the shared mailbox reaches her personal account outside spam.

When to run it again

Run the same test after changing forms, mail settings or hosting. Add a few more triggers: a website platform or plugin update, a change of email provider or DNS host, and any change in who watches the inbox. Between those, repeat it on a set schedule, such as once a quarter.

What to do this week

  • Run the phone test with an outside address and a labeled message.
  • Find the test in the inbox and check the To line when you press Reply.
  • Send a reply from the business mailbox and confirm it arrives cleanly.
  • Write down who watches the destination and who covers when they are out.
  • If anything failed, send the maintainer your identifier, time and address.

Where ALCO can help

If you want help with any part of this check, the work falls under services ALCO USA Inc lists: website care, managed hosting and development for the form itself; email security and domains and DNS for how the form’s mail is sent and authenticated; and Microsoft 365 and Google Workspace for the mailbox it lands in. The ALCO help desk is staffed 24 hours a day, including holidays, and calls are answered by a person.

Sources