“Our inquiries are down, but we don’t know why” — before blaming ads, check your contact form

“Have inquiries dropped off lately?”

That kind of question often comes up in website operations.

When it does, the first things we tend to check are traffic-related:
“Are the ads underperforming?”
“Did our search rankings drop?”
“Is the landing page no longer matching the audience?”

Those can all be valid causes.

But sometimes, the issue sits much closer to the conversion point.
For example, the submit-tracking tag on the contact form may have come off, meaning submissions are not being counted in the first place.

The form itself still works.
Users can still fill it in and submit it.
So, at a glance, nothing looks broken.

That is exactly why form issues can be hard to notice.

This article is for the person responsible for a contact form on a B2B website. We will walk through how to review input fields, error messages, submit tracking, and post-submit paths so that form improvement becomes part of your team’s operating routine, not a one-off emergency fix.

---

Why this problem happens

Contact forms are one of the easiest parts of a website to postpone.

Once a form is live, it often receives less attention than ad campaigns, landing pages, content, or design updates. But the form is the final touchpoint before an inquiry. If something is unclear or broken there, the traffic you worked hard to earn can be lost at the very end.

Background 1: forms are often built on “a human can probably understand it”

Input labels and error messages are often created to the standard of “as long as a human can read it.”

That can leave forms with issues such as:

• Fields that rely only on placeholder text instead of a clear label
• Required and optional fields that are not obvious on screen
• Errors shown only with a red border, without a message explaining what went wrong
• A post-submit confirmation path that makes the user hesitate

A person may still be able to complete the form by guessing from context.
But if the meaning of each field is not clearly defined, the form becomes harder for users, harder for internal teams to maintain, and harder to evaluate structurally.

Background 2: forms can break quietly after launch

The difficult thing about forms is that they can be correct when built, then quietly break later.

A submit-tracking tag may go missing.
A thank-you page link may break.
An image or element may fail to load.

If the form itself still submits, visual checks alone may not catch the issue. The team may only realize something is wrong after looking at the numbers and noticing that inquiries appear to have dropped.

There is also a broader shift to consider. As mechanisms such as WebMCP suggest a future where AI agents may operate HTML forms directly, the structure of a form may matter more than before. We cannot yet know how widely that kind of mechanism will spread, but making labels, required fields, error messages, and post-submit paths clearer is already useful for human users.

In other words, improving the structure of a form is not just preparation for AI. It is also a practical way to make the form easier for people today.

---

Steps to solve it

Here is the process we use when reviewing a contact form.

The flow is simple:

1. Visualize the current state
2. Record and standardize the checks as part of monthly operations
3. Use the results over time to support improvement proposals

STEP 1: Visualize the current state

The first step is to review the form from top to bottom and flag anything that feels unclear.

When doing this, text-only comments can easily create confusion.
For example, saying “please fix the company name field” may not be enough. Which screen? Which state? Which part of the field?

That is why we capture the form screen and place comments directly on the relevant area. With MONJI+’s Feedback feature, each issue can be left directly on the screen capture, making it easier for designers and developers to understand exactly what needs attention.

The kinds of issues that come up include:

• The “Company name” field does not show whether it is required or optional
• A phone number format error shows only a red border, with no message explaining what is wrong
• The path to the post-submit confirmation page makes the user hesitate

The point of this step is not to fix everything at once.
It is to make the small points of friction visible so the team can discuss and handle them one by one.

STEP 2: Record and standardize it as a monthly operation

Next, avoid letting the review end as a one-time patch.

Form problems can come back when pages are updated, tags are replaced, fields are added, or layouts are adjusted. If the check depends only on someone remembering what happened last time, the same issue can easily recur.

So we add “form structure” items to the pre-launch checklist.

For example:

1. Does every input field have a label whose meaning is clear?
2. Can required and optional fields be distinguished both on screen and in the code?
3. When an error occurs, does the message explain what to fix and how?
4. Is the path from submit to completion a single, clear line?

By registering these in MONJI+’s Checklist feature, the team can call them up each time from the same flow used to create Feedback.

The important part is not relying on memory.
Once the checks are written down, form improvement becomes easier to repeat as part of normal website operations.

STEP 3: Use several months of results to support proposals and improvements

After improving the form, you also need to watch what happens next.

In cases where the submit-tracking tag has come off, simply checking whether the form can be submitted is not enough. You also need to confirm whether submissions are being measured correctly.

We now have main pages, including forms, crawled automatically on a schedule with MONJI+’s Website issue detection feature.

Machine-detectable issues, such as missing tags, broken links on post-submit pages, and failed image loads, are listed out. Detected issues can then be turned directly into Feedback.

After a fix, the Google Analytics integration lets the team track form submission counts from within the same project.

That makes it easier to follow the sequence:

“we fixed the issue” → “the numbers changed” → “we know what to check next time”

Recurring issues can also be added to the project Wiki as new check items. This way, what the team learns from one incident becomes part of the next pre-launch check.

---

What changed in practice

The biggest change for us was how we think about forms.

Previously, pre-launch checks tended to focus on visual breakage and typos. Those are important, of course. But for a contact form, the following questions matter just as much:

• Is the meaning of each input field clear?
• Are required and optional fields easy to distinguish?
• Does the error message explain what to fix?
• Is the post-submit path easy to follow?
• Is submit tracking working correctly?
• Are key pages being monitored for issues on a schedule?

By turning these points into Feedback, checklists, scheduled crawls, and Wiki notes, form improvement becomes less dependent on one person’s awareness.

Instead of fixing rough edges once and moving on, the team can carry those lessons into future operations.

---

Notes and limitations

Improving the form structure does not solve everything.

Some issues are easy for machines to detect, such as missing tags, broken links, or failed image loads. But questions like “is this form easy to use?” or “can someone complete it comfortably?” still require human judgment.

The future spread of mechanisms like WebMCP is also not something we can decide or predict with certainty.

Still, making labels, required fields, error messages, and post-submit paths clearer is useful regardless of what happens next. It helps human users today, and it may also make the form easier for AI agents to interpret in the future.

Rather than treating this as a special AI-only measure, it is more realistic to start by making the form structurally clearer for everyone.

---

MONJI+: a website operations platform born from the field

For teams that want to make pre-launch form checks part of their routine, the Feedback and checklist features mentioned here are available to try on the 30-day free trial.

▼ Features mentioned in this article

• Feedback
• Checklist
• Website issue detection
• Google Analytics integration
• Wiki

▼ Start free
https://tool.monji.tech/signup

---

MONJI+, the WebOps platform, was born to solve the challenges we have felt firsthand in the field.

MONJI+ brings the people involved in website operations together into one team, and supports issue resolution across every phase of website operations.

From the start, we have never aimed to build a “finished product.”

The challenges truly worth facing are found in the field of website operations. That is why we have continued listening to the real voices of people working there.

By taking in each voice one by one, we have continued making updates that resolve small points of friction. New features have also grown out of challenges from the field. Through that accumulation, MONJI+ has become supported by users across 77 countries.

▼ Learn more about MONJI+
https://monji.tech/plus/

A world where people working in website operations can say, with pride, “I love this work.”

▼ To make that real, we are waiting to hear your voice
https://monji.tech/plus/co-creation/

---

Summary

When inquiries appear to be down, it is natural to check ads, search rankings, and traffic first.

But before stopping there, it is worth checking whether the contact form itself is causing the issue.

A form can look normal even when the submit-tracking tag is missing. Input fields can seem understandable while still lacking clear labels, required or optional distinctions, and useful error messages. A post-submit path can technically work while still making users hesitate.

Start by capturing the form screen and making unclear points visible.
Then add form-structure checks to your pre-launch checklist.
Finally, monitor key pages on a schedule so missing tags, broken links, and other detectable issues are caught earlier.

With those steps in place, form improvement becomes less of a one-time fix and more of a repeatable team routine.

A contact form is not finished just because it is live.
It is the final touchpoint before an inquiry, and it deserves to be reviewed continuously.