Customer Intake Form Template for Service Businesses

A customer intake form template for service businesses. CSR script, qualifying questions, and the 9 fields that drive better dispatch and a higher book rate.

5 min read6 sectionsApril 26, 2026

9 essential intake fields

(1) Customer name and primary phone. (2) Service address (validated). (3) Equipment make and approximate age, if known. (4) What is happening (open question, capture verbatim). (5) When did it start (today, days, weeks, months). (6) Have you tried anything (filter changes, reset, etc). (7) Best arrival window (today preferred, alternatives). (8) Source of inquiry (LSA, referral, repeat, etc). (9) Service agreement or membership status.

CSR call script

Greet by company name and CSR first name. Ask for name first, then address, then phone. Capture equipment age before symptom; technicians prefer this order. Repeat the symptom back to the customer. Then ask for the booking directly with two choices: "I have a 2pm slot today or 9am tomorrow, which works better?" Analysis of 60M-plus tracked calls found only about 35 percent of agents ever actually ask for the booking, so the assumptive close is where most book rate is won or lost. Confirm arrival window, confirm phone for tech to call before arrival, and end with: "We will see you between X and Y. Tech name will call when on the way."

Handle the price question, then skip what wastes time

When the caller leads with "how much?", do not just quote a number; that turns them into a price shopper. Reframe: "I want to get you the most accurate price, so let me ask two quick things." Service Nation Alliance survey data shows only about 10 percent of customers decide on price alone; reputation, reviews, and trust drive the rest. Then skip the three things that waste call time: asking for a credit card before the tech arrives (most shops collect on completion), selling membership during an emergency call (offer at end of job), and long coupon explanations. Keep service calls to roughly 6 minutes, 4 to 6 is the working range, but never rush an emergency call past the urgency cues.

Lead source attribution

Always capture source. "How did you hear about us?" with a defined list: Google, LSA, Yelp, referral, repeat, sign, vehicle, other. This single question feeds every marketing decision; without it CAC math is broken. The stakes are real in 2026: HVAC Local Services Ads leads average roughly $93 each, and a fumbled intake on a paid call is near-$100 of spend that produced nothing. Google also scores LSA responsiveness into ranking, so how you answer and book is itself a marketing input, not just a fulfillment one.

Repeat-customer fast-track

When phone matches an existing customer, skip name/address/phone capture. Confirm address with "still at X?" Cuts call time by 90 seconds and signals professionalism.

How agentic AI takes this further

A voice bot that reads the 9 fields off a script is not an agent, it is an IVR with a nicer voice, and it does not solve the actual problem the section above quantifies, most CSRs capturing 4 to 5 fields instead of 9 under real call pressure. A rule that auto-sends a "thanks for calling" text after every call is automation, fixed, and blind to whether the call that just ended actually captured what the dispatcher needs. A real intake agent perceives the call transcript as it comes in through the phone system or CallRail, decides whether all 9 fields actually got captured, and drafts the missing pieces as a follow-up text if the CSR forgot to ask, like the equipment age or the lead source.

It reads the live or near-live call transcript off the phone system, a native line or a CallRail-tracked number, checking it against the shop's own 9-field structure rather than a generic call-quality rubric. It also reads the caller's phone number against the existing customer database the instant the call connects, because whether this is a first-time caller or a repeat customer changes what actually needs asking, the same lookup a sharp CSR does from memory on a good day.

Judging field completeness means checking the transcript against each of the 9 fields specifically, not just scanning for keywords: "best arrival window" has to actually contain a window, not just the customer saying "whenever works." High confidence that a field is genuinely missing, the CSR never asked lead source at all, produces a drafted follow-up question. Lower confidence, the CSR asked in a roundabout way the transcript captured awkwardly, produces nothing, because chasing a field that was actually covered just annoys the customer for no reason.

The write is a drafted follow-up text through Twilio, plus a completeness flag written back to the call or job record in the FSM, one idempotent update per call so a retry never sends the same follow-up twice. If the text send fails, say a bad number format from the transcript, the agent retries once and then flags the failure to the CSR rather than assuming the customer received a message that never went out.

That follow-up does not go to the customer unsupervised. It queues for the CSR or office to approve, because an automated text landing on a customer who just hung up from an emergency call can feel tone-deaf if the timing or wording is off, and a person catches that a script cannot. Where the agent earns real time back is the repeat-customer fast-track: it pulls the existing record the instant the phone number matches and hands the CSR a pre-filled ticket, cutting the call down before the CSR even says hello, a genuine time save rather than a judgment call, which is why it can run with a lighter touch than the follow-up text. Built in n8n against the FSM and phone system APIs, with call data logged in Supabase, this becomes a system the shop can audit for book-rate impact over time. Pineido builds AI agents for small business around exactly this kind of intake-completeness workflow, source handed over, running on the shop's own CSR line rather than a rented call-scoring tool.

It will not handle the actual sales conversation, close the booking, or decide how to respond to a price-shopping customer, those calls stay with the CSR who has read the section above on what wastes call time and what does not. What it reliably does is catch the fields a rushed call skips, equipment age, lead source, the two the section above calls out as most commonly dropped, before the dispatcher discovers the gap onsite. Run consistently over CSR shifts, that shows up as fewer jobs missing basic context by the time a tech arrives, not a specific book-rate number until it has actually been measured on your call volume.

Get operations insights weekly

Join service-business operators who get one actionable insight on ops, automation, and growth every week.

Checking that you're human. You can send in a moment.

No spam. Unsubscribe anytime.

You’re subscribed! Look for our next issue in your inbox.

Frequently asked questions

How long should an intake call be?

Service work: 4 to 6 minutes, with about 6 minutes being the sweet spot in tracked-call data. New install or replacement quote: 8 to 12 minutes, since these need education and value-building. Emergency: 3 to 5 minutes; speed and urgency capture matter more than detail.

Should CSRs use a script or free-form?

Script with allowed deviations. Pure free-form skips fields. Pure scripted sounds robotic. Mid-tier shops typically need a script; senior CSRs can deviate within guardrails.

What about online booking and missed calls?

Online booking forms should capture the same 9 fields. Most FSM platforms (Jobber, Housecall Pro, ServiceTitan) provide configurable booking forms; use them. Just as important: close the missed-call gap. CallRail reports a 14 percent missed-call rate in home services, and 78 percent of customers hire the first business that responds, so pair the form with missed-call-to-text auto-reply and fast callback.

How does Pineido help?

Customer intake redesign is part of a CRM cleanup or intake automation sprint. Includes script buildout, FSM form configuration, and CSR training.

Ready to ship?

Tell us where you are stuck. We will review it and send a focused recommendation within one business day.

Written by

Kostadin Stamboliev

Founder and Imaginator

Founder and Imaginator at Pineido. Practitioner across IT consulting, app and web development, technical SEO, and AI / automation. Ships production code in 30-day sprints with fixed scope and clear ownership.

LinkedIn