What happens after someone submits your contact form?

A prospective client submits a form and sees a confirmation. From the visitor’s side, the firm has the inquiry. From the firm’s side, several things may still need to happen before a person takes responsibility for it.

The difference is easy to miss in a marketing report. A form submission is a countable event. Assignment, a contact attempt, a conversation, and a decision about the case happen in other systems, often under other people’s supervision.

We have written about why attribution that ends at the form is inadequate. The implementation question is more specific: what record crosses each boundary, and how would anyone know if it stopped moving?

Follow the inquiry, not just the notification

In the JTNY implementation, website form reporting can group submissions by captured context such as the first-touch page, content cluster, and the call to action used. That is useful: a submission from an employment page can remain distinguishable from a general contact inquiry.

The bridge into Docket gives the intake team a place to work with the inquiry. Notifications help the team notice an inquiry. The durable record is what lets someone follow it through intake. An email being sent does not tell you that someone owns the next action.

A handoff therefore needs a way to identify the same inquiry on both sides. Without that link, two plausible-looking reports can describe different populations. A website may count a resubmission as another event while intake treats it as the same person. Neither report has to be technically broken for the comparison to be misleading.

For your own system, ask to see the record identifier carried from the website into intake. It need not be visible to the prospect. It does need to survive retries and let an operator investigate a missing or duplicate record without guessing from names.

The next action needs an owner

Once an inquiry arrives, the system needs to distinguish an assigned task from completed human contact. A staff member logging a call attempt is an operational event. It does not mean the prospect answered.

The distinction matters after hours. A response-time rule measured in business hours can be met while a person waits through a long evening or weekend. Both clocks can be useful, provided the report says which one it measures. A firm deciding whether it needs evening coverage needs elapsed waiting time as well as compliance with its internal service target.

The Docket work gives us a concrete reason to connect the website to case operations. The publishing layer supplies context; intake records what staff did next. The operating review can then ask whether a weak source is sending unsuitable inquiries or whether suitable people are waiting too long to speak to anyone. Those explanations lead to different decisions.

Here is the chain we want an operator to be able to inspect:

This is an operating specification. It should not be mistaken for a claim that every part is already automated.

Where our own measurement still stops

Docket remains the source of qualified and retained outcomes in the work described here. The website attribution report does not automatically become a retained-matter report merely because its submissions reach Docket. Those outcomes still need to be joined to their originating records.

Our Docket page states the current boundary: outcomes return through the operating review, while the full automatic feedback loop remains on the roadmap. That limitation belongs alongside the product description. Otherwise a buyer could reasonably hear “integrated intake” and assume every page already has a reliable cost-per-retained-matter figure.

Calls have their own boundary. A tracking number assigned to a practice area can identify that source category. It does not, on its own, identify the exact visitor or page journey behind every call. A tap on a phone link, a connected call, and a retained matter need different definitions and different evidence.

Organic search also has limits. Search Console reports query performance in aggregate; it is not a list of each named prospect’s search history. We should not fill that gap with a confident label in a dashboard.

A small audit that exposes the gaps

Choose a recent, manageable sample of inquiries with the person responsible for intake. Use appropriate internal access and keep identifying details out of the marketing presentation. For each record, establish whether the source was captured, who owned the first action, whether contact occurred, and what the current outcome is.

Allow “unknown” as an answer. An unknown source is a measurement issue to investigate. An inquiry awaiting contact is an operational issue. A person who was contacted and declined representation belongs in a different category again.

Write down where the trace breaks. If the website has a record that intake cannot find, examine delivery and reconciliation. If intake has the record but no next action, examine assignment. If a matter was retained but marketing cannot connect it to the inquiry, examine the outcome join.

That exercise gives the firm a concrete next piece of work. It also makes the conversation with a marketing provider more useful: the question becomes which handoff to repair, and who will demonstrate that it now works.