AI can turn a website form, a call note or a Parade sign-in into one consistent lead brief: source, lot status, plan status, desired location, missing facts and the next review step. It organizes what the prospect supplied. It never decides that a lot works, a plan fits or the project moves forward.
What does AI do when an inquiry arrives?
Intake preparation. A new inquiry reaches the office as a short form, a voicemail, an email thread or a hurried note from an event weekend. An agent puts those facts into the same working structure, marks empty fields and lines up questions for whoever owns the response.
The agent keeps the prospect's exact meaning. "Has land" is not a surveyed, buildable lot. "Has plans" can mean a saved image, a sketch or a construction set. The brief keeps the original wording and marks the operating field as unconfirmed until a person reviews it.
This is one tactical workflow in the AI for builders article library. It does not replace your qualification process or your sales judgment.
Which facts belong in the brief?
| Intake field | What the agent records | What a person decides |
|---|---|---|
| Original source | Form, call, referral, event or other stated path | Whether the source record is accurate |
| Lot status | The prospect's wording plus any address or parcel reference | Control, feasibility and due-diligence needs |
| Plan status | Stock plan, sketch, plan set or nothing supplied | Design readiness and fit with your process |
| Location | Requested town, community or lot location | Service-area and pipeline fit |
| Project intent | Spaces, use, style and timing as described | Scope fit and the right next conversation |
| Missing facts | Questions the source material does not answer | Which questions matter before the lead advances |
How does intake handle incomplete or conflicting facts?
By showing the uncertainty. If a form says the prospect owns a lot and an attached message says the parcel is under consideration, both statements go in the brief with a conflict flag. Same when a target community sits outside your service area or a requested plan clashes with the site assumptions.
Do not let the agent fill blanks from a nearby record or someone else's prior conversation. Two decision makers submit separately. A buyer's agent asks about the same project. Similar names and email addresses are not grounds to merge records without a controlled matching rule and human review.
What does the agent say when the source is vague?
It uses operational labels: "not supplied," "needs confirmation," "conflicting source statements." It never uses labels that sound like conclusions: "qualified," "bad fit," "ready to build." You can define routing flags. The person responsible for sales decides what they mean for the inquiry.
The custom-home lead qualification article covers the human decision that follows intake.
How do you build a reviewed intake process?
- Choose approved inputs. The forms, call notes, event records and inbox paths the agent may read.
- Define the brief. Fields, source labels, missing-data terms and conflict flags the office will use.
- Protect the original. The submitted message or recording reference stays attached to the working record.
- Assign a reviewer. One person checks identity, project facts, routing and next action.
- Test the hard cases. Duplicate inquiries, vague lot claims, buyer-agent questions and event notes with no contact details.
- Record the decision. Approved status and next action go in the builder-owned CRM, not an agent transcript.
The AI operations stage starts with a bounded workflow like this, a named reviewer and a manual fallback. We run a fleet of Claude and Codex AI agents that researches, drafts, builds and checks the workflow. People set the rules and review every output.
Where does the brief live after review?
In your lead record. Not in a chat window, a private inbox or a temporary automation log. The CRM record carries the original source, the current owner, the next action and the facts your sales process needs. Clean source data is also what makes lead attribution possible later.
Keep sales records apart from plan archives and active-project documents. A lead brief can link to an approved upload location. It does not scatter plan sets, surveys or private documents across tools. The builder CRM guide covers record ownership, fields, pipeline stages and export controls.
How do Parade and model-home inquiries differ?
Event intake is thinner than a web inquiry. A scanned code, a handwritten note or a short conversation establishes interest, not project fit. Keep the event, the location and the stated question. Do not turn casual traffic into a construction-ready lead. The follow-up owner asks for lot, plan and timing context after reading the note.
What stays outside the agent's authority?
Approving a lot. Assessing feasibility. Promising a start. Interpreting a plan set. Stating an allowance. Choosing a sales path. Rejecting a prospect. Sending messages, until you have separately defined and tested that permission. Intake is done when the responsible person holds a faithful, reviewable record.
Once that record is approved, AI follow-up drafting can prepare a response without pretending the agent made the qualification call. For record boundaries and permissions, see AI and builder data privacy.
What else gets asked about AI lead intake?
Can AI qualify a custom-home lead?
No. AI lead intake organizes stated facts and applies approved routing flags. A person decides lot, plan, scope, service-area and operating fit.
Should the agent merge duplicate inquiries?
The agent flags likely duplicates. A person or a controlled matching rule confirms the merge, so two prospects or two projects never collapse into one.
Can intake include uploaded plans?
Yes. The brief records that a plan was supplied and places it in an approved location. Plan interpretation and feasibility review stay with qualified people.
What if the agent cannot identify the source?
Mark the source unresolved, keep the original record and route it for review. The agent does not guess the source from the content of the inquiry.