Features

Website Enquiry Forms: Fields, Spam Protection and Missing Emails

Configure enquiry fields and spam protection, then troubleshoot missing emails through saved records, notification states, mail transport, delivery logs and inb

If a website enquiry email is missing, first find the submission in the admin, then ask the maintainer to check the notification result, active mail transport and recipient mailbox. When the record is saved, sales can follow up using its contact details while the email investigation proceeds. Keep separate evidence for the saved enquiry, the application's sending result and actual mailbox arrival.

This guide covers product quotations, project enquiries and document requests. CatchCMS supports custom fields, validation, CAPTCHA, honeypots, IP submission limits, email notifications and submission lookup. Use the first two sections to configure the form, then follow the diagnostic steps. For international-trade websites, also check languages and ownership with the multilingual product and enquiry guide.

1. Collect information the team can act on

  • Product quotations: name, contact details, product or model, quantity and requirements.
  • Website projects: website type, languages, site count, deployment and delivery requirements.
  • Support or document requests: the relevant product, issue and required files.

Require the information needed for follow-up and explain contact formats and data use. Automatic product-model or source-page values require theme integration and verification. Use the product catalog acceptance guide to connect details, resources and the enquiry entry. Verify available source-page information against what the current theme actually submits.

2. Configure fields, spam protection and notification ownership

  1. Create the form and fields in the admin, including types, required values and validation.
  2. Configure CAPTCHA and IP limits on the form. Have technical staff configure the honeypot through the public runtime settings and theme integration. Test normal entry, missing required fields, incorrect CAPTCHA and limit messages separately.
  3. Confirm the form's recipients, the deployment's mail transport and the people responsible for checking records and inboxes.
  4. Have the developer integrate the form, success messages and error display in the theme, then complete entry and submission on a phone.

The protection methods address different submission patterns. Review genuine usage and abnormal records when adjusting settings. Confirm project implementation individually for CRM integration, approvals, automatic assignment and automatic resending. For multiple sites, verify each form, data scope and staff access. Use dedicated test inboxes under the staging isolation checklist.

3. Preserve the enquiry and find its admin record

Record the customer's submission time and time zone, page, language, contact details and request summary. With an authorized admin account, select the correct site and form, search by submission identifier, processing state or notification state, then compare record times and field values with the customer’s details. Keep follow-up evidence in an authorized channel, assign a person to contact the customer and record the business outcome.

Once located, use the record identifier throughout the investigation. If the record is still missing, ask technical staff to check the site resolved from the actual domain, form availability, login requirements, validation, limits, endpoint response and application logs. After a timeout or page error, check again for an existing record before deciding to submit a new request clearly labelled as a test. Verify the page's success message together with the admin outcome.

The current CatchCMS public submission endpoint saves the validated submission, then calls mail sending synchronously. Its response includes the record ID and notification result. A saved enquiry remains available for business follow-up when notification encounters an error. Theme integration determines which response details visitors see; developers can inspect the endpoint response and logs.

4. Choose the next check from the notification result

Ask the maintainer to compare the admin record, endpoint response and logs using this table. Notification state describes sending; processing state describes business follow-up. Manage each separately.

ObservationCheck and action
skippedThe current flow skips sending when the notification recipient list is empty. Confirm that this is intentional, or have an administrator configure the intended recipients and retest.
failedThe mail sending call raised an exception. Technical staff should retain its time and error summary, then check transport, authentication, connectivity and provider restrictions.
sentThe mail call completed. Check the active transport, provider delivery records and mailbox location, confirming each recipient individually.
Pending or uncertain stateCompare the response, application logs and record update time to establish sending execution and state persistence. A response with state_persisted=false indicates that the notification state could not be saved and needs technical investigation.

The admin state can remain at an earlier stage when updating it encounters an error. Technical staff should establish sending evidence before arranging a controlled retest or a resend procedure implemented for the project. Record recipients, time, original enquiry identifier and result for each action so sales can recognize duplicate notifications.

5. Have technical staff inspect the sending environment

Establish whether the running deployment uses SMTP, a mail API, a development log transport or a capture tool. Log transport can complete the application's sending call and write the message to a log. External delivery requires an appropriate mail service configuration. The current code also defines a failover configuration with SMTP followed by log transport. When using it, establish which transport handled the message. Check the effective runtime configuration. After changes, the maintainer should handle configuration caches or process updates through the deployment procedure, then retest.

  • Connection and authentication: verify the provider's host, port, encryption, account and application-specific credentials, plus permission for programmatic sending.
  • Runtime connectivity: check connections, DNS, TLS and outbound network restrictions from the actual website environment. Maintain credentials through an authorized secure channel.
  • Sender identity: verify the sender address and required domain verification. For bounce or authentication errors, inspect applicable SPF, DKIM and DMARC settings using the current provider's instructions.
  • Sending restrictions: inspect account status, quotas, frequency limits, test mode and recipient restrictions. Use errors and logs to plan the next controlled test.

For the current synchronous form flow, begin with request, application and mail-service records. Projects adding queues or other notification channels should also inspect their job execution and failure records. Give providers a redacted error summary, with credentials and complete customer requests kept under controlled access.

6. Trace the message after the sending call completes

First use the recipient's webmail to inspect all folders, spam and filtering rules. Check desktop or mobile synchronization separately. The mailbox administrator can then inspect account status, capacity, forwarding, filtering and quarantine policies. Alibaba Cloud's sending and receiving troubleshooting guide in Chinese covers webmail/client separation, spam folders, receiving rules and delivery logs. Apply the checks supported by the actual service.

Ask sending and receiving administrators to trace the same time range, sender, recipient and provider message identifier. Google Workspace's Email Log Search troubleshooting guide checks delivery and post-delivery status separately. Log scope, retention and privileges depend on the service. Record the CMS submission identifier and the email system's Message-ID separately, linking them through subject, time and content.

For a bounce, retain the error code and reason for the appropriate administrator. When the provider records acceptance, continue tracing delivery and classification at the receiving end. If one recipient receives the message and another is missing it, record the result for each address. Include observation times and evidence locations.

7. A clearly labelled diagnostic example

Fictional example: an equipment company receives a test enquiry through its English PX-100 product page. Sales finds the complete contact and quantity fields in the admin. The notification result is sent, while the inbox has no matching message. The maintainer discovers that this rehearsal environment uses log mail and finds the notification content with the same submission identifier in its log.

The team follows up from the saved record. The maintainer configures the agreed mail service and a dedicated test recipient. A fresh enquiry with a new test label is submitted, and the team separately confirms its admin identifier, sending result, provider delivery and inbox arrival. The original record remains available for comparison. This example illustrates diagnosis and retesting; determine actual transport and failure causes from deployment evidence.

8. Complete retesting and handover with one record

Copy these fields: environment and site | page and language | form | test label | submission time and time zone | admin record identifier | notification state and persistence result | transport | provider message identifier and delivery result | arrival folder and time for each inbox | follow-up owner | open issue and deadline. Enter the observed result for each stage and retain original evidence within its authorized scope.

  1. At an agreed time, submit a clearly labelled test enquiry through the public page and inspect success and error display.
  2. Have business staff find the admin record and verify site, contact details, request, source and processing access.
  3. Have technical staff check notification and sending evidence, and mailbox owners verify arrival for every recipient.
  4. Complete the agreed Chinese, English and mobile journeys, including required fields, CAPTCHA and limits.
  5. Record follow-up for existing real enquiries, the procedure for duplicate notifications and the person and frequency for routine submission checks.

For AI-assisted maintenance, see MCP content management and specify the site, form and allowed fields in each task. Through project consultation, provide the form scenario, sites and languages, deployment and mail service, redacted symptoms and expected follow-up workflow. Confirm responsibility for CatchCMS configuration, theme integration and project development item by item.