# Can you replace our email-based intake with a structured system?

Canonical URL: https://newphysician.org/can-you-do-this/build-an-intake-system/

Yes. Good intake reduces missing information and makes the next step obvious without turning the first contact into an interrogation. The form, routing, acknowledgment, and staff queue should be designed as one process rather than separate widgets.

What a solution might involve

Identify the minimum information needed to route a request. Use conditional questions only where they change the next action. Provide clear acknowledgments, duplicate handling, assignment, and a way to request missing information. Keep an audit trail of status changes.

What needs care

Collecting more information than necessary increases friction and exposure. Sensitive documents should not be requested through an unreviewed channel. Automated acknowledgment must not imply acceptance, eligibility, professional advice, or a response deadline the team cannot meet.

How we would judge whether it works

A complete request reaches the correct queue, an incomplete request receives a useful next step, and a duplicate does not become two cases. The requester knows what happens next and the team can see who owns the response.

Likely engagement

Business Engine: $5,000 to $15,000. This is a likely starting tier, not a quote. Scope, access, dependencies, and responsibility for operation need agreement first.

Discuss Business EngineWhat to send first

Show common requests, the minimum routing information, and the point at which specialist review is required.

Send me the messy version.

Experience and scope

Selected builds documents the currently authorized public proof. This page describes a proposed approach, not a claim of a completed client engagement in this exact workflow.

Related problems

Can you build a customer portal without replacing our whole business system?

Can you stop requests bouncing between departments?



[Send me the problem](https://newphysician.org/send-me-the-problem/)