Few inquiries after launching your international trade website? What’s wrong with the form settings?

When an export-oriented website attracts traffic but receives few inquiries, you cannot conclude outright that the form is the problem. However, the form is worth checking first: customers may not see where to access it, may be blocked by required fields while filling it out, or may have submitted it without their information being delivered.

When troubleshooting, distinguish between “viewing the page,” “starting to fill out the form,” “successful submission,” and “sales receiving the inquiry.” Checking only whether the website loads or whether there are new emails in the inbox cannot tell you where customers are dropping off.

First, confirm that customers can find and use the form

A product detail page is where customers may decide to make an inquiry after learning about the specifications. If the only “Contact Us” link is in the top navigation, customers have to leave the product page to submit their requirements, adding another step to the process. Place a clear inquiry entry point near the product information, such as “Request a Quote” or “Ask About Product Specifications,” and have the button open the form directly or take customers to where the form is located.

The button text should also match the action that follows. If clicking a “Download Catalog” button instead requires customers to submit complete purchasing information, they may feel misled. A “Request a Quote” button should let customers specify the model, quantity, or requirements, rather than requiring them to provide order details they may not yet know.

Mobile checks should go beyond confirming that the form is visible. Test it on an actual phone to make sure input fields are not cut off by the edges of the page; the current field and submit button remain visible when the keyboard opens; dropdown menus work correctly; and error messages are not obscured. For multilingual websites, check each language version separately: translating the page does not mean that form instructions, buttons, and submission feedback have also been updated.

Set up fields to support the first conversation

The form's purpose is to help both parties get in touch, not to collect all the information for a complete order at once. Name, email address, and a description of the inquiry can serve as basic information. Whether fields such as product model, purchase quantity, and destination should be required depends on whether the business needs that information to provide an initial response.

For example, a quote request for standard components may require the model and quantity to calculate the price. But if a customer has not yet decided on a model, making that field mandatory can prevent them from making an inquiry. You can make the model an optional field and prompt customers to provide the intended use, dimensions, or drawing information in the description so sales can help confirm the details later. For custom equipment, customers may not know the purchase quantity when they first get in touch.

Pay particular attention to settings that can make the form harder to complete:

• Requiring a phone number or instant messaging account: Customers may not want to provide these when making first contact. If email is sufficient for an initial conversation, make these fields optional.
• Overly complicated country or region selection: If this information is only needed to determine shipping conditions, provide easy-to-search options and avoid requiring information that is not yet needed.
• Overly strict input format restrictions: Phone numbers may include country codes, spaces, or symbols; date and address formats also vary by region. Validation should reject genuinely invalid entries, not require all customers to follow a single format.
• Making file uploads a requirement: Drawings can help clarify requirements, but not all customers can provide them right away. Specify the supported file types and size limits, and allow customers to submit an inquiry without an attachment.

Reducing the number of fields does not mean giving up screening altogether. If sales needs to distinguish between product categories, offer a short list of options while retaining “Other” and a text field for details. If certain information is essential to an accurate quote, explain why it is needed rather than simply marking it “Required.”

A clickable submit button does not mean the inquiry has been delivered

The form submission process involves page validation, server-side processing, data storage, and notification delivery. A problem at any stage may leave customers without feedback after they click submit, or show them a success message even though the company has not received a notification.

Submit test inquiries using different email addresses and devices, then check each step against the same record:

1. Enter valid information and submit the form. Confirm that a clear success message appears, rather than the page remaining unchanged or loading indefinitely.
2. Intentionally leave a required field blank or enter an invalid email address. Check that the message identifies the specific field and that the other information the customer has entered is retained.
3. Log in to the website backend and confirm that the test record has been saved, including the product name, page source, and information entered by the customer.
4. Check whether the notification inbox or customer management system received the same record. If the record is in the backend but not in the inbox, check the recipient address, spam filtering, and email delivery settings.
5. If the record is not in the backend, check the submission endpoint, verification service, plugins, or recent page changes. If necessary, ask the website development service provider to review the error logs.

Testing should cover more than the main homepage. Forms on product pages, forms in pop-ups, and different language versions may use different configurations. Retest the forms if the website template, plugins, or recipient email address have recently changed. If validation fails, the page should explain how to correct the issue or try again later, so customers are not left unsure whether their submission succeeded after filling out the form again.

Use data to distinguish between “no one filled out the form” and “submission failed”

A website may receive traffic but few inquiries without customers ever viewing the form. Track events such as form display, form-start, and successful submission by page or traffic source, then compare them with the records actually saved in the backend. Before analyzing the data, confirm the event trigger conditions: clicking the submit button does not mean the submission succeeded. Where possible, base the success event on server confirmation or actual storage in the backend.

If product pages receive many visits but the form is rarely displayed, check the entry point's placement, button text, and page content. If many visitors start filling out the form but few complete the submission, focus on required fields, input validation, and the mobile experience. If records are being saved normally in the backend but fewer reach the sales team, check the notification and routing process first.

When sample sizes are small, a few tests or occasional visits can significantly change the proportions. Avoid concluding that a particular field is the sole cause based on short-term fluctuations. Before comparing results, exclude internal test records and keep in mind that visitors to different product pages, from different countries or regions, or through different traffic channels may have different needs.

After adjusting the form, submit it once from a customer's perspective: Can you find the entry point? Is each field clear? Can you correct errors? Is there clear feedback after submission? And has the company actually received the information? Make sure this process works from start to finish, then use traffic sources and page content to assess inquiry quality. This helps avoid relying on adding buttons or removing fields to solve every problem.