Show a clear confirmation message after submission. State that the enquiry was received and explain the next step only if the team can reliably deliver it. Avoid promising a response time that staffing or business hours cannot support. An acknowledgement email can include the request summary and a way to correct an accidental submission, where appropriate.

Choose routing rules the team can maintain. Assignment may depend on service interest, region, account ownership, or another business criterion. Define who owns unmatched or incomplete submissions and who covers the queue during absence. A notification is not the same as ownership; someone needs to be accountable for taking or delegating the next step.

Pass the submitted answers, the page or service of interest, the submission time, and relevant campaign context to the CRM when available. Keep the record concise and readable. The responder should understand what the person asked without searching several tools. Do not infer details that were not provided or collect more personal information than the process needs.

Decide how often new enquiries are checked, which requests are prioritized, and how the next action is recorded. Expectations should reflect the business’s staffing, hours, and type of request. If the responder needs more information, record the question and a follow-up date. If the request is outside the company’s services, close the loop respectfully instead of leaving it in an active queue.

Not every form is ready for a sales conversation. Define how the team handles spam, vendors, job enquiries, incomplete forms, existing customers, and prospects outside the service area. Use consistent stages, such as “submitted,” “valid enquiry,” “assigned,” “contact attempted,” and “qualified,” so reports do not treat every form fill as pipeline.

Use stable definitions and review a meaningful period of data. A higher number of submissions alone does not prove the process is working if enquiries are irrelevant, undelivered, or never followed up. Check whether source data is available and consistent before comparing channels.

1. Submit a clearly labeled test request using the live website form.
2. Confirm the page acknowledges the submission correctly.
3. Check that the CRM record contains the expected answers and source information.
4. Verify owner assignment, notification delivery, and any follow-up task.
5. Confirm that the team can distinguish the test from a real prospect.
6. Repeat after material changes to forms, fields, routing, or automation.

• Several people receive the alert, but nobody is clearly responsible.
• Leads are assigned using a rule with no fallback for missing values.
• Responders lack the form answers or context the prospect already provided.
• Unqualified submissions are counted as sales opportunities.
• Marketing emails are sent without the required permission or preference handling.
• Response-time promises exceed the team’s actual coverage.