Start one step after the thank-you screen

Take a recent enquiry and follow it through your business. Who first saw it? Where did the details go? What did someone need to ask again? The gaps in that journey are a better starting point than deciding how many fields belong in a new form.

A useful intake captures enough context for the next decision. For a specialist service, that may mean the type of request and the customer's constraints. It does not mean asking for every detail before you have earned a conversation.

Make ownership explicit

An email delivered to a shared inbox does not establish an owner. Decide whether a request belongs to a person, a role or a queue, and how someone accepts responsibility for it.

Give the team a small set of meaningful states. New, awaiting information, in progress and closed may be enough. Each state should explain what is happening and what can move the request forward. Avoid creating statuses merely because a dashboard has room for them.

  • The customer receives a clear acknowledgement.
  • The request has a record that preserves its context.
  • A person or queue owns the next action.
  • Unanswered requests remain visible.

Design the exception, too

What happens when the email fails, the same person submits twice, or the intended owner is away? These are ordinary workflow cases. The first version can handle them with a visible exception queue and a manual reassignment action.

Automate only after the rule is clear. A reminder can prompt an owner to review a request; it should not imply that a customer received a response if no response was sent.

Measure the handoff before adding more features

Begin with the questions your team needs answered: Which requests have no owner? Which are waiting on the customer? Where does work repeatedly stop? Record the events needed to answer those questions, then compare the new workflow with your starting point.

This can be a focused improvement to an existing website and internal process. The objective is a reliable next step, not a larger software project for its own sake.