Elementor Forms: What to Ask and How to Display Errors

A contact form should facilitate inquiries and help your team receive and respond to them. These are the decisions you should make.

A person arrives at your website, understands what you do, and decides to write to you. They have spent time explaining their needs and are one step away from starting a business conversation. At that moment, a confusing form can introduce doubts that the rest of the page had managed to resolve.

Perhaps it asks for data the client doesn’t have yet. Perhaps it returns an error without explaining what is happening. Or it confirms the submission, but the inquiry never reaches the person who should answer it.

That is why designing a contact form requires making decisions that go beyond its appearance. You have to think about what information your team needs, what the visitor expects when sending it, and how that inquiry is managed within the company.

Table of Contents

The form starts before the first field

The page leading to the form should already help the visitor decide if they are in the right place. If you offer several services, it is helpful for the person to understand which one might fit their needs before asking them to write.

It also helps to explain what will happen next. A phrase like “Tell us what you need and we will review the scope of your project” provides more context than an isolated button with the word “Send.” If there is a defined response time and your team can meet it, indicate it. If there isn’t one, it is preferable to explain the next step without creating an expectation you don’t control.

This preparation is especially important for complex services. Someone looking to redesign their website doesn’t always know what budget they need, what technology their current page uses, or how to describe their problems accurately. The form should facilitate a conversation, not become a preliminary exam.

What information is worth asking for

The useful question is not how many fields a form should have, but what your team needs to provide a reasonable initial response.

In an initial inquiry about a service website, it is usually helpful to know who is writing, how to respond to them, and what they want to solve. Their current website address can also be useful if they already have one. Other data—such as phone number, budget, or expected date—depends on how your sales process works.

Not all useful information has to be mandatory. A phone number can facilitate a conversation when the client prefers to talk, but requiring it can make someone who expects an initial response by email uncomfortable. Similarly, asking for the budget can help guide the scope, provided the visitor has enough context to give an answer.

For example, if a company inquires about a redesign, they may not yet know how much it costs to solve their problems. Asking for an exact figure without explaining what the service covers can cause them to abandon the form or answer at random. A more useful option is to offer indicative budget ranges or allow them to explain that they are still defining the investment.

A more detailed form can also make sense. If you receive many inquiries that don’t fit your service and each one requires evaluation time, some additional questions can help both parties. The key is that the benefit must be clear: guiding the request, preparing a more useful response, or avoiding a conversation that isn’t a good fit.

Before adding a mandatory field, it is worth asking a simple question: if we didn’t have this data, could we respond anyway? If the answer is yes, it can probably be optional or requested later.

What should happen when something fails

A person can make a mistake when typing their email, leave a field empty, or try to send the form when there is a connection problem. The design must handle these situations with the same care as a successful submission.

A message like “An error has occurred” forces the visitor to guess what to do. It is more useful to point out the affected field and explain the problem in clear words. If the email is missing, simply indicate it. If the format seems incorrect, a recognizable example can be shown.

The message should appear near the data that needs attention and not rely solely on color. A red mark can help locate the field, but it doesn’t explain by itself what needs to be corrected.

What happens to the rest of the inquiry also matters. If someone has written several paragraphs about their project and an error erases all the content, it is reasonable that they won’t want to start over. Preserving what was written and allowing for correction or resubmission should be part of the form review, depending on the possibilities of the solution and its integrations.

When the problem cannot be resolved from the form itself, offer a clear alternative. For example, a contact email address can prevent the visitor from getting stuck on an error screen without knowing how to communicate with the company.

A confirmation should say something useful

After clicking the button, the visitor needs to know if their inquiry has been sent. While it is processing, a visible indication helps avoid uncertainty and repeated submissions.

The subsequent confirmation should answer two questions: what happened and what can I expect now.

“Thank you for your message. We have received your inquiry and will review the information to get back to you” provides more clarity than a simple “OK.” If the process includes a call, a preliminary review, or a response within a specific timeframe, it can be explained there, as long as it reflects the team’s actual workflow.

It is best to avoid confirmations that promise more than the system or the company can guarantee. The message should correspond to the point in the process that has been completed: confirming that the form accepted the data is not the same as ensuring that a person has already read the inquiry.

If an automatic email is also sent to the client, its function is to reinforce that clarity: remind them that they have made contact, explain the next step, and offer a way to reply if they need to add information.

From the click to the person responding

A form can look good and show a correct confirmation, but that alone doesn’t prove that the inquiry has reached the right team.

Depending on the website configuration, the message can be saved in WordPress, sent by email, incorporated into a CRM, or go through several of these stages. Each serves a different function. The log allows you to consult the saved information; the notification alerts someone that there is a new inquiry; the CRM can help assign it and follow up.

The choice depends on the volume and organization of the company. For a small team, receiving a notification and keeping an accessible log may be enough. If several people handle requests, it may be necessary to define who receives them, how they are assigned, and what happens when someone is away.

Before connecting tools, it is worth clarifying the process:

  • Who should receive each type of inquiry?
  • Where is the message kept if the email notification fails?
  • How does the team know if someone has already responded?
  • What data is actually needed in the next stage?
  • Who checks that the form and its notifications are still working?

Technology should support those decisions. Adding a CRM or automation can be useful, but it does not replace the responsibility of attending to requests.

In our guide on how to check form delivery, we explain in more detail the difference between the confirmation message, the log, and the receipt of the notification.

Contact must also work for people who navigate differently

Not all visitors use a mouse or access from a large screen. A person may navigate the page with a keyboard, enlarge the text, or use assistive technology to complete the fields.

This affects visible decisions: labels that remain available while typing, understandable instructions, errors associated with the corresponding field, and a navigation order that makes sense. On mobile, additionally, the form must be able to be completed without buttons, messages, or fields being cut off.

Accessibility is not a finish added at the end. It is part of allowing more people to understand the page and get in touch with you. The W3C guidelines on form notifications offer useful criteria for communicating errors and confirmations.

What to ask for in a web design project

If you are hiring a team to build your website, you don’t need to choose every technical adjustment of the form. You should, however, be able to understand how the entire journey has been planned: what the visitor will see, what information will reach your company, and who will handle it.

Before launch, ask the responsible team to explain how errors are managed, where inquiries are stored, and how you will receive notifications. If external tools are involved, also confirm who administers each one and what happens if the person or provider in charge changes.

After launch, the form remains an operational part of the website. Changes in email, integrations, or the fields themselves can affect the path of an inquiry. Being clear about who reviews those connections and how failures are detected helps the contact remain reliable over time.

At Capricorn Nexus, we approach web design and its continuity as related parts of the project. If you are preparing a new page or your current form raises doubts, we can review the scope of your web project with you: tell us what type of inquiries you receive, who handles them, and what problems you have detected in the process.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top