Make every serious inquiry visible, owned, and honestly handled.

• A website form sends an email, but nobody can prove the inquiry was stored.
• Requests arrive through several inboxes, calls, referrals, or platforms.
• Ownership depends on who notices first or remembers to follow up.
• The buyer receives a generic message that overstates what actually happened.
• Scheduling, qualification, proposals, and follow-up are disconnected.
• The business cannot reconstruct source, response, meeting, or outcome consistently.

1. Validate. Reject malformed, oversized, automated, or incomplete input before a record is created.
2. Commit. Store the inquiry and its follow-up event durably before showing a success state.
3. Acknowledge. Tell the buyer exactly what was received and what the message does, without impersonating a human response.
4. Assign. Give the inquiry an accountable owner, visible status, and defined exception path.
5. Route. Move qualified inquiries through the appropriate scheduling, estimate, proposal, or direct-response path.
6. Learn. Record whether the conversation, opportunity, proposal, and final outcome happened, along with a useful reason.

• Current-state lead-source and handoff map.
• Data contract, validation rules, spam controls, and privacy boundaries.
• Durable form handling, outbox processing, retries, and idempotency.
• Internal notification, ownership, statuses, queues, and exception alerts.
• Truthful acknowledgment, qualification, private scheduling, and follow-up rules.
• CRM integration, source attribution, lifecycle fields, and reason codes.
• Test states, access inventory, operating runbook, and team handoff.

The exact scope follows the existing tools, volume, compliance needs, access, and the number of paths the team must support. See the target-state intake blueprint for the operating logic.

Useful automation can confirm a durable receipt, preserve context, route a record, and make failure visible. It should not claim that a person has read the message, promise a response time the business cannot uphold, or use synthetic personalization to imitate judgment.

The human response should arrive with the context needed to be useful. Scheduling stays private when fit review or sensitive context should come first.

• A storage failure never produces a receipt or success screen.
• A notification failure leaves a retryable record and visible alert.
• A browser retry does not create a duplicate inquiry.
• Contact details stay out of analytics, URLs, and ordinary exception messages.
• Every consequential state has an owner and a recovery instruction.
• The client owns the production accounts, source, access, and operating record in scope.

Is this just a website form project?

No. The form is one entry point. A dependable intake system also covers validation, durable storage, internal ownership, truthful acknowledgment, qualification, scheduling rules, follow-up, failure handling, and the final record.

Does Field Theory replace the CRM or other tools?

Not by default. The work begins with the operating path and evidence. Existing tools are retained when they can support the required ownership, status, integration, access, and recovery behavior.

Can the system promise an immediate human response?

Only if the business can operationally support and verify that promise. An automated receipt can confirm a durable submission, but it must not pretend that a person has reviewed or answered the inquiry.

Can email, scheduling, and CRM services be connected?

They can be included when the providers, permissions, privacy requirements, and failure paths are defined in scope. No production connection is represented as active before it is authorized and tested.

• The website is not the whole system
• What should happen in the first 30 minutes after a quote request?
• Workflow automation for service businesses