Illustrative example — not a client transcript.
“We're thinking about opening up the kitchen, but we haven't worked out the budget.”
That opening already holds a project type, an early description and an unresolved budget. A rigid intake script might ask for all three again.
An AI receptionist for remodeling should give the contractor a clear project enquiry and an agreed next conversation. For a north New Jersey kitchen and bath remodeler, we connected nine-field intake to GoHighLevel lead capture and Calendly discovery-call booking.
Across roughly seven months, the build handled 900+ inbound calls, captured dozens of project leads and booked dozens of discovery calls. These historical call-log figures include early testing. A discovery-call booking is a next conversation, not a signed project or completed job.
The challenge is preserving what the homeowner means while producing a record the CRM can accept. The build exposed a useful lesson about uncertain budgets and timelines, alongside the integration fixes below.
Who gets intake, and who does not
The agent greets the caller as the company's virtual assistant. A trade partner, or anyone who says they want the owner, is transferred immediately. They get no intake. Sending them through homeowner questions would block the conversation they called for.
A new-project caller gets a choice: a texted link to a form, or intake on the call. Anything else, the agent takes a message.
The choice matters because some people are ready to talk and others want to gather details first. A form link sent is not a lead submitted, and it is not an appointment.
Nine fields, asked one at a time
| Field | How the build handles it |
|---|---|
| Name | Asked on the call |
| Spelled back to the caller | |
| Phone | Captured automatically from the incoming call |
| Project type | Asked unless the caller has already said it |
| Project description | In the caller's own words |
| Address | Addresses outside New Jersey are declined |
| Budget | Caller answer; the original prompt supplied a default when missing |
| Timeline | Caller answer; the original prompt supplied a default when missing |
| Source | How they found the company |
Nine is a count of information, not nine questions. Phone arrives with the call. If the caller has already said “kitchen”, asking for the project type adds effort and no information. And option lists are never read aloud: the agent asks when the caller hopes to start, and does not recite the CRM's timeframe choices.
Why plain English broke the CRM
Natural answers and CRM fields do not match, and three practical lessons show how.
A missing state. The CRM rejected a lead for “Andover NJ” because the agent left out the state. Asking the agent to remember was not the fix. We now parse the state server-side.
Natural answers the CRM rejected. The CRM rejected a timeline of “ASAP”, text containing en-dashes, and a source the caller had put in their own words. We added a value guard in n8n. Before a lead goes to the CRM, n8n re-checks the state and the field values.
A tester typing clean answers will not find any of these. They appear with real callers, who say “ASAP”, give a range with a dash and tell you “my neighbour told me”.
The original prompt also supplied default budgets and timelines when callers were undecided. We recommend changing that: keep unknowns unknown, preserve the caller's own words and send any record the CRM cannot accept to staff for review. A required dropdown should never turn uncertainty into a commitment. This improvement is a recommendation, not a verified deployed change.
Illustrative example of the recommended handling — not a client transcript.
AI receptionist: I'm the company's virtual assistant. Would you prefer a text form, or would you like to tell me about the project now?
Caller: I'll explain it now. We want to open up the kitchen. We haven't set a budget, and we'd like to understand the process before choosing a start date.
AI receptionist: Understood. You haven't set a budget or start date yet, so I'll note both as undecided. Which town is the house in?
From lead to discovery call
Once the fields are in, n8n submits the lead to GoHighLevel. Then the agent checks Calendly availability and offers one slot at a time. It books a 15-minute discovery call and gives one confirmation.
GoHighLevel holds the lead, any message and the texted form link. Calendly holds the booking. An email notification goes out as well.
The call is a discovery conversation. It is not a quote, a site visit, a project approval or a promise to start work.
- Route trade partners and owner requests before any homeowner intake.
- Let the caller choose a form link or intake on the call.
- Re-check the state and field values before the lead is submitted.
- Treat the discovery call as booked only after Calendly confirms it.
Test both failure branches before launch: a rejected lead and a slot that disappears between offer and booking. When the chosen slot is gone, the right move is to re-check the calendar and offer current times, not to insist on the one mentioned earlier.
What the team still owns
The contractor's team handles the transfer line, reads the messages and holds the discovery calls. It also evaluates scope, feasibility, site visits, quotes and whether to accept a project. A good intake gives them the caller's real starting point, so the first conversation can move forward.
Where this workflow fits
This approach suits a remodeler that wants project enquiries organised before the team's first conversation. The contractor still scopes and prices the work. Your service area, CRM fields and discovery calendar need mapping to your own operation; this implementation used GoHighLevel and Calendly in New Jersey.