Your contact form works. Does the enquiry reach someone responsible?

A form can validate every field, show a friendly confirmation and send an email. The visitor sees success. The business may still have no reliable record of where the enquiry went or who must act on it.

Treat the form as the first step in a workflow. A customer submits a request; the site validates it; an integration routes it; a person or queue accepts responsibility; the customer receives an acknowledgement; someone follows up; and the outcome is recorded. Each handoff needs an observable result.

Trace one enquiry end to end

Use a clearly marked test submission and a mailbox or test record controlled by the team. Record the timestamp, destination, routing rule and resulting record identifier. Confirm the submitted details survive the journey and that the person who receives them can tell what the customer asked for.

Then test the exceptions. What happens if a required field is absent? If an address is malformed? If the primary recipient is unavailable? If an integration times out? A form that works only when every dependency is healthy has an undocumented operating assumption.

Separate acknowledgement from ownership

An automated receipt tells the customer the submission arrived. It does not tell them that a person has reviewed it or accepted the next action. Internally, a message delivered to a shared inbox is not the same as a named owner. Define the event that means “received,” the event that means “assigned,” and the event that means “answered.”

For each step, identify the system of record and the responsible role. The website may store the submission, a CRM may own assignment, and the team inbox may handle conversation. If the same status is copied manually between them, say who updates it and how the team notices a missed handoff.

Set acceptance checks that follow the work

A useful acceptance check does not stop at “the submit button works.” It verifies the expected record is created, the right team can find it, the assigned owner is visible, the acknowledgement is accurate, and the next action can be audited. Include a failed delivery or unavailable-recipient scenario so the team knows what recovery looks like.

If the workflow depends on a person noticing an email, be honest about that operating design. You may keep it, but define a backup owner and a simple check for submissions awaiting action. The first repair is often a clearer responsibility and record, not another application.