Customer Intake Call Reference

Why this matters

The initial customer call (or text / chat) shapes the entire service experience. Good intake = right tech, right tools, right expectations. Bad intake = wrong assumptions, wasted trips, frustrated customers. The intake person (often dispatcher OR office) needs systematic process. This is the field card.

Who does intake

Typical handlers:

• Receptionist / customer service
• Dispatcher
• Owner (small business)
• Tech (sometimes)
• Online booking (some)

Each has access to scheduling + standard questions.

Information to gather

Customer identification:

• Full name
• Phone (primary + alternate)
• Email (for confirmations)
• Service address (verify; not billing)
• Best time to reach

Service request:

• What's happening (their words)
• When did it start
• Duration / frequency
• Any troubleshooting attempted
• Urgency

Property details:

• Type (residential / commercial)
• Single family / condo / apartment
• Equipment specifics (brand, model if known)
• Equipment age (estimate OK)
• Special access (gate, dog, etc.)
• Parking situation

Service preferences:

• Preferred time of day
• Day flexibility
• Communication preference (call / text)
• Authorized decision-makers (spouse, etc.)

Payment:

• Method preference
• Insurance involvement
• Warranty coverage

Customer's words matter

Listen to customer's description:

• They may not use technical terms
• They describe symptoms
• They give context

Don't:

• Translate too quickly
• Assume what they mean
• Jump to diagnosis

Do:

• Repeat back to confirm understanding
• Ask clarifying questions
• Capture verbatim sometimes

Question types

Open:

• "Tell me what's happening"
• "When did this start?"
• "How does it feel / sound / smell?"

Specific:

• "Is the breaker tripped?"
• "Is water still flowing?"
• "Is there power to the unit?"

Yes / no:

• "Are you currently home?"
• "Does the customer have a key for entry?"
• "Has another company looked at this?"

Mix depending on what's needed.

Categorizing urgency

Emergency (immediate):

• Active water leak
• No heat (freezing weather)
• No cooling (vulnerable people)
• Gas leak
• Power out (medical)
• Sewage backup
• Locked out
• Roof leak (active)

Urgent (same / next day):

• Equipment not working (but not emergency)
• Customer flexibility needed
• Inconvenient but not dangerous

Standard (scheduled):

• Maintenance
• Non-urgent repair
• Routine work
• Inspections

Tell customer expected response time.

Dispatching decisions

Based on intake:

• Which tech (specialty, area, availability)
• Which time slot
• What parts / tools needed
• Estimated duration
• Any special equipment

The better intake = more accurate dispatch.

Phone scripts (templates)

Opening: "Thank you for calling [Company]. This is [Name]. How can I help you today?"

Information gathering: "I'd like to get some information from you. Can you tell me what's happening with your [equipment]?"

Confirming scheduling: "OK so we'd like to schedule [tech] to come by on [day] between [time window]. Does that work?"

Setting expectations: "There's a [trip charge / service fee] for the visit. The tech will diagnose and provide an estimate before any work begins. Does that sound good?"

Confirming: "Just to confirm: [customer name] at [address], we'll see you on [day, time]. We'll send confirmation by [text / email]. Anything else I should know?"

Texting / chat intake

For text-based:

• Same information
• Asynchronous
• Customer may respond between activities
• Don't bombard

Sample text: "Hi! Thanks for reaching out. To help schedule your service, I need a few quick details:

1. What's the issue?
2. When did it start?
3. Your address?
4. Best time for service?"

Online booking forms

Capture:

• Required fields (name, phone, address, service)
• Service type dropdown
• Date / time preferences
• Notes field

Verify human OR follow up to confirm.

Customer's emotional state

Customer may be:

• Stressed (no heat in winter)
• Angry (multiple service issues)
• Anxious (cost concerns)
• Calm (routine maintenance)

Match your tone:

• Empathetic for stressed
• Calm for angry
• Reassuring for anxious
• Professional for calm

Reading red flags

Sometimes intake reveals:

Customer who's been to others:

• "Three other techs couldn't fix it"
• Could be legitimate; could be customer issue
• Document; tech can decide

Customer pushing back on basic info:

• Won't provide address
• Won't provide phone
• May not be serious customer
• Or test of your professionalism

Customer with unrealistic expectations:

• "I want this done for $X" (way below cost)
• "I need it done today" (when standard scheduling)
• Set expectations early

Customer with abusive language:

• Even in initial call
• Document
• Manager may decide whether to take

When intake reveals out-of-scope

If service request beyond your trade:

• Refer to appropriate trade
• Don't promise what you can't deliver
• Reputation maintained

Specific scenarios

Customer's first time call:

• Slower, more thorough
• Education about service
• Set expectations clearly

Repeat customer:

• Faster (info in system)
• Reference past visits
• Personalized

Emergency call after hours:

• Different process
• Premium pricing disclosed
• Confirm customer accepts
• Dispatch immediately

Customer who hangs up frustrated:

• Don't argue
• Document
• Manager call-back if appropriate

Pricing disclosure at intake

Should mention:

• Trip charge / dispatch fee
• After-hours premium
• Diagnostic fee
• Standard pricing structure

Don't promise specific price (need diagnosis usually):

• "Tech will provide estimate after diagnosis"
• "Pricing depends on what's found"

Pre-arrival communication

After intake:

• Confirmation text / email
• Reminder day before
• "On the way" text

Customer feels informed.

When customer can't be reached for confirmation

If unable to confirm:

• Try multiple times
• Email if no phone answer
• Sometimes cancel + reschedule

Don't waste trip when uncertain.

Calendar / schedule integration

Modern software:

• Booking integrates with technician calendar
• Customer can choose available slots
• Confirmation automatic
• Reminders automatic

Reduces intake person workload.

Documentation

Each intake creates record:

• Customer info
• Service request
• Dispatch details
• Communication record

This is start of customer service file.

Quality assurance

Listen to / review intake calls:

• Did intake person gather necessary info?
• Were customer questions answered?
• Tone professional?
• Time appropriate (not too long; not too brief)?

Coaching opportunity.

Intake training

For intake person:

• Service offerings
• Pricing structure
• Tech specialties
• Common questions + answers
• Difficult customer scripts
• Software usage

Ongoing training; not one-time.

Common intake mistakes

Not answering. The most expensive intake mistake is the call that rings out to voicemail. Most callers with a problem simply dial the next company. Every unanswered ring is a lost job you never see in a report.

Diagnosing over the phone. "That's probably your capacitor" commits the shop to an answer nobody has verified, sets a price expectation, and makes the tech look wrong when it turns out to be something else. Gather symptoms, do not name causes.

Quoting a repair price sight unseen. Give the diagnostic or trip charge clearly and confidently. Anything past that is a guess the customer will hold you to.

Taking the customer's diagnosis as the work order. "I need a new water heater" often means "I have no hot water," which is sometimes a thermocouple. Book the symptom, not the customer's conclusion, or the tech shows up with the wrong truck load.

Skipping the service address verification. Billing address, mailing address, and the property with the problem are frequently three different places. On rentals and property management calls this is the number one cause of a wasted trip.

Missing access details. Gate code, dog, locked crawlspace, tenant not owner, alarm code, parking restriction, unit number, elevator reservation in a building. Every one of these turns into a lost hour when it surfaces at the door.

Not confirming who can authorize the work. A tenant cannot approve a repair, and a spouse who is not home may need to be consulted. Establish the decision maker at intake, not at the point of sale.

Booking with no equipment information. Make, model, approximate age. Even a photo texted in beforehand can turn a two-trip job into one.

Understating the time. Squeezing a job into a slot it does not fit breaks the rest of the day and the next customer's window.

Not writing what the customer actually said. Paraphrase loses the detail that solves the call. Quote them.

Talking past the emotion. A caller with water running through the ceiling needs to hear "we can get someone there today" before they hear your intake questions. Acknowledge first, gather second.

Ending the call without a confirmed next step. Date, window, what the customer needs to do, what the charge will be, and how they will be notified. If any of those is missing, the call is not booked.

References

• Service business operations standards
• Customer service training (NESRA, Service Roundtable)
• Manuall internal: Customer Communication Standards, Service Call Pricing Models