Service Call Intake Checklist: What to Capture on Every Call
A printable intake checklist for dispatchers and CSRs: the exact fields to capture on every service call — address read-back, access details, symptoms, callback — and how to ask for them.
In short
Capture six things on every service call: callback contact, the address read back digit by digit with its role, access details (unit, gate code), the problem in the caller's own words, scheduling expectations, and a full read-back. Print this page and keep it at the desk.
Most failed dispatches are born in the first three minutes of a phone call. Not because dispatchers are careless, but because a busy intake call has no structure: the caller talks fast, the line is noisy, and whatever gets typed is whatever got heard. A one-page checklist fixes more of this than any software — and it costs nothing. Here is the one we recommend, built from how real shops lose money on intake.
1. Contact and callback
- Caller name, and who they are for this job (tenant, owner, office manager).
- Best callback number — read it back. If the tech cannot reach anyone on site, the visit dies.
- A second contact if the caller will not be on site.
2. The address — read back digit by digit
- Street number and name, spelled out. Read the number back digit by digit ("one six zero zero"), not as a whole ("sixteen hundred") — this is where 1500 becomes 500.
- City and ZIP. A ZIP mismatch is the fastest way to catch a misheard street.
- The role of the address: is this where the tech should GO, or the billing address? If the caller mentions two addresses, label both.
- If the caller corrects themselves mid-call, cross out the first version completely. Most wrong-address dispatches keep the first number the caller said, not the corrected one.
- Nearest cross street or a landmark for anything rural, industrial, or new construction.
3. Access — the address is not the door
- Apartment, suite, or unit number. Ask even when the caller does not offer it.
- Gate code, callbox, or lockbox code — and which entrance it opens.
- Parking and entry notes: loading dock, back entrance, floor, elevator or stairs.
- Pets, tenants, or anyone the tech should know about on arrival.
4. The problem — in the caller's own words
- What is happening, quoted as said. Do not translate "it makes a clicking noise and the air is warm" into "AC broken" — the tech loses the detail that matters.
- Which equipment: brand, rough age, location in the building if known.
- What the caller already tried. Saves the tech the first twenty minutes.
- Is this urgent or can it wait — their words, not your guess.
5. Scheduling and expectations
- Offered window, agreed window, and who will be on site during it.
- Quote expectations: diagnostic fee, trip charge — say it now, not on the invoice.
- How they heard about you (one question, big marketing value).
6. The read-back
Before hanging up, read the whole ticket back: name, callback, full address with unit, access notes, the problem, the window. Twenty seconds. It feels redundant right up until the day it catches a wrong street name — and it will.
The one-glance version
| Field | Ask it like this | Why it matters |
|---|---|---|
| Callback number | "Best number if the tech needs to reach you?" | Unreachable customer = dead visit |
| Street number | Read back digit by digit | "Fifteen hundred" vs "five hundred" |
| Address role | "Is this where the tech should go?" | Service vs billing mix-ups |
| Unit / gate code | "Apartment or unit? Any gate code?" | Right building, locked out anyway |
| Symptoms verbatim | "What exactly is it doing?" | Tech arrives prepared |
| Mid-call corrections | Cross out the first version | First-said number sticks by default |
| Full read-back | Repeat the whole ticket | Catches everything above |
Print this page (Ctrl+P — it prints clean), tape it next to the phone, and hand a copy to every new hire on day one. If your calls are recorded, the checklist also becomes your audit tool: pull three recordings a week and score them against it.
Where software fits
A checklist gets the right questions asked; it still depends on a human hearing the answer correctly on a noisy line. HearLoc is the tool that back-checks the address part automatically: it takes your existing call recordings, extracts every spoken address, validates each against Google, captures unit numbers and gate codes, and flags only the uncertain ones for review. The checklist and the software cover for each other.
Frequently asked questions
What should a dispatcher capture on every service call?
Six things: a working callback number, the full address read back digit by digit with its role (service vs billing), access details like unit numbers and gate codes, the problem in the caller's own words, the agreed time window, and a complete read-back before hanging up.
How do I make sure the address is right on a phone call?
Read the street number back digit by digit, confirm the ZIP, ask whether it is the service or billing address, and if the caller corrects themselves keep only the corrected version. For recorded calls, software like HearLoc can validate the spoken address against Google automatically.
What is the difference between a service address and a billing address?
The service address is where the technician goes; the billing address is where the invoice goes. Callers often give both in one call, and dispatching to the billing address is one of the most common — and most avoidable — failed dispatches.
Is there a printable version of this checklist?
Yes — this page prints cleanly. Use your browser print function (Ctrl+P or Cmd+P) and keep a copy at the intake desk.
Related
Turn your recorded calls into verified addresses
HearLoc extracts and validates every address mentioned in a call recording, with confidence scores and review flags — by API or straight from your phone provider.
Start free trial