Key takeaways
- Every message needs seven fields: who it is for, the caller, the callback number, the address, what happened, the urgency and the promise made.
- Read back the number, the address and the promise at the end of every call, in one go.
- Flag urgency on facts, not tone. A water damage and freezing claim averaged $15,400[2].
- Expect voicemail on the callback: 67% of Americans let unknown numbers ring out but check the voicemail[3].
Messages are handoffs
Every phone message hands a problem from the person who heard it to the person who has to fix it, often hours later and from the cab of a truck. The two may never speak. Everything the second person needs has to survive the trip, and “Lady called about a leak, call her back” survives nothing.
Talking to customers is part of the trade; BLS lists communication among the important qualities for plumbers because they deal with customers regularly[4]. Much of that talking starts with a message someone else took. This guide is for whoever takes them: CSRs, dispatchers, an owner's spouse, a tech covering the office on a quiet morning.
Booking a job on the first call is a different task with a longer list, covered in the information to capture on every plumbing call. A message is what you take when the job can't be booked yet: the caller wants a particular person, needs a price you can't give, or rang while the person who books is out.
The seven fields
| Field | What to write | Why it matters |
|---|---|---|
| 1. For | A name or a role: the owner, the on-call tech, billing | A message for “someone” is a message for no one |
| 2. Caller | Full name, spelled back; company name if commercial | The callback opens with their name, and correct spelling avoids duplicate records |
| 3. Callback number | Mobile number, read back in groups; whether texting is OK | One wrong digit and the job is gone |
| 4. Address | Street, number, unit and ZIP; a cross street if unsure | Tells the reader whether you even cover it |
| 5. What happened | The problem in the caller's own words, and when it started | Lets the reader judge urgency and the likely part |
| 6. Urgency | Now, Today or Can wait, with the reason | Decides who reads it first |
| 7. Promise made | What the caller was told, and by when | The reader has to keep it, or call to change it |
The callback number deserves the most care. Nearly every adult carries a phone: 98% of US adults own a cellphone and 91% a smartphone, and ownership is high among people 65 and older too[1]. Ask for the mobile first, because it reaches the caller at work, in the car or standing in the flooded basement.
- All adults
- Ages 65 and older
Source: Pew Research Center, 2026[1]
Show the data
| Device | All adults | Ages 65 and older |
|---|---|---|
| Own a cellphone | 98% | 96% |
| Own a smartphone | 91% | 79% |
Field 5 is where most messages fall apart. Write what the caller said, not what you think it means. “Water coming through the kitchen ceiling under the upstairs bathroom since this morning” tells a plumber far more than “leak”. If the caller is upset, write the facts, not the mood, and leave diagnosis to the person who will see the job.
Field 7 is the one most message pads leave out, and it causes the angriest callbacks. If the caller was told “Dave will call before 2”, Dave needs to know that, because at 2:05 the customer is already annoyed and may have phoned someone else.
The read-back
Read back three things on every message: the number, the address and the promise. Do it at the end, in one go, so the caller can correct you without being interrupted while they explain the problem.
- The number in groups: “That's 555, 014, 2238, a mobile, and texting is fine?” Pause after each group so a wrong digit gets caught.
- Names and streets spelled where there's any doubt: “Marsh, M-A-R-S-H?” Use a word for letters that sound alike: “B as in boy, D as in dog.”
- The address with unit and ZIP: “14 Mill Lane, the rear unit, ZIP 4-0-1-5-8?”
- The promise in plain words: “Dave will call you back before 2 today. If water starts coming through again, call this number and say it's urgent.”
Example close: “Let me read that back. Linda Marsh, mobile 555-014-2238, texting OK. 14 Mill Lane, rear unit. A water stain on the kitchen ceiling that's growing, started this morning, and the upstairs toilet keeps running. You'd like Dave. He'll call you before 2 today. Have I got all that right?”
The read-back takes about twenty seconds. Callers rarely mind; most hear it as a sign that somebody was listening. The callers who do correct something are the ones whose message would otherwise have been wrong.
The urgency flag
Mark urgency on facts, not tone. A calm caller can have water running into a basement, and a furious one can be calling about an invoice. Use three levels with yes-or-no tests:
- Now: water that can't be stopped, sewage coming up, no water at all, or a gas smell, which gets your safety script before anything else. Someone acts within minutes.
- Today: a problem getting worse but contained, such as a slow leak into a bucket or the only toilet blocked. Called back within the hour you set.
- Can wait: estimates, maintenance, billing and dripping taps. Called back by the end of the next working day.
Misjudging a Now call is expensive for the customer: the average homeowners insurance claim for water damage and freezing was $15,400 over 2019 to 2023[2]. When unsure, flag it Today and write the reason in field 5. A dispatch priority matrix turns the three levels into an order of work, and the emergency triage questions cover what to ask when a call sounds like Now.
Good and bad messages, side by side
| Bad message | Good message | |
|---|---|---|
| For | Dave? | Dave (owner); she asked for him by name |
| Caller | Linda | Linda Marsh, M-A-R-S-H, new customer |
| Number | In caller ID | 555-014-2238, mobile, read back, text OK |
| Address | Mill Lane | 14 Mill Lane, rear unit, ZIP read back |
| What happened | Leak | Growing ceiling stain under upstairs bathroom since 8 am; toilet keeps running |
| Urgency | (blank) | Today: contained, getting worse |
| Promise | Said someone would call | Told Dave calls before 2 pm |
Example message for a fictional caller. The right column takes about a minute longer to write.
Read the left column as Dave would at 11:40, between jobs. He doesn't know whether Linda is a customer, where she lives, whether it's urgent or what she was promised, and “in caller ID” assumes the number was captured and belongs to her rather than the neighbor whose phone she borrowed. Every gap means a call to ask, and each extra call is another chance she has already booked somebody else.
Gaps that survive all the way to the truck cost more. Average hourly earnings at plumbing, heating and air-conditioning contractors reached $42.38 in September 2026[5], so a trip to the wrong unit or a locked gate is paid time with nothing to show for it. And the office pays twice: dispatchers at those contractors earned a median $22.83 an hour in May 2025[6], and a message that needs a second call to fill a gap spends their time again.
When seven fields aren't enough
Some callers need one more line. Add it under field 5 rather than inventing a new form for every case.
- Tenants: the landlord or property manager's name and number, and whether the tenant can approve work. See handling tenant calls.
- Commercial accounts: the PO number, the site contact and access hours. The commercial contractor example shows how a missing PO can stall a job.
- Existing jobs: the invoice or job number, and which tech was there last.
- Callers more comfortable in another language: which language, and whether someone in the household speaks English.
Getting it to the right person
- Caller
- Your team
- System
01Caller
Caller asks for Dave
Dave is on a job, so the call taker offers to take a message.
02Your team
Seven fields written
For, caller, number, address, what happened, urgency, promise.
03Your team
Read-back
Number, address and promise confirmed with the caller.
04System
Flag and send
Flagged Today and sent to Dave's queue, not left on a sticky note.
05Your team
Callback logged
Dave calls at 12:15 and leaves a voicemail if she doesn't pick up.
Example. A message is closed only when the callback is logged.
Messages die in three places: on paper that never leaves the desk, in a text thread that scrolls away, and in a shared inbox where everyone assumes someone else has it. Pick one place, give every message an owner, and close it only when the callback happens.
When you call back, expect voicemail. 67% of Americans say they don't answer unknown numbers but check the voicemail if one is left[3]. Leave your name, the company, what they called about and when you will try again. The morning handoff after overnight calls applies the same discipline to messages taken at night.
Turning a voicemail into a message
Voicemails are messages too, just badly formatted ones. Whoever clears the mailbox should copy each one into the same seven fields rather than forwarding the audio and hoping someone listens.
- Play it twice: once for the gist, once with the form in front of you.
- Take the number from the recording as well as from caller ID; people often leave a different, better number.
- Fill field 5 with their words, and write “not given” in any field the caller skipped, so the person calling back knows what to ask.
- Set the urgency flag from what was said. A voicemail that mentions water on the floor is Now, however calmly it was left.
- Field 7 is empty by definition, so write down what your voicemail greeting promised, such as a callback by 9 am.
Voicemail greetings for plumbers covers the other end: a greeting that asks callers for the details these fields need.
When an SI Employee takes the message
If the calls you can't answer go to an SI Employee, it takes down the same core fields: the address and ZIP code, the problem, how urgent it is and the best callback number, all read back to the caller. The message arrives as a summary in your account and your inbox, with the recording and transcript, and urgent jobs are marked urgent. Because the recording is attached, field 5 is never a paraphrase you have to take on trust.
- Answered2 events
- Job captured4 events
- Urgency set2 events
- On-call routing2 events
- Booked or requested3 events
- Summary sent2 events
Activity
- Call
Incoming call, 9:42 pm
Ava answers as Clearwater Example Plumbing on the after-hours schedule.
- Call
Problem described
Water dripping through the kitchen ceiling from the upstairs bathroom.
- Call
Address and ZIP code checked
Inside the example service area. Address and callback number read back and confirmed.
- Call
Marked urgent
Matches an approved trigger: active leak. No diagnosis given.
- Call
Approved safety wording read
Ava reads the shut-off wording your team approved, word for word.
- Call
Trying the on-call technician
Example: Marco is on call tonight. No answer after the agreed ring time.
- Call
Trying the backup
Example: Dana answers and accepts the job. The caller is transferred.
- Call
Urgent job summary sent
Recording, transcript and job summary sent to the office inbox, marked URGENT.
- Call
Next morning, 7:55 am
The office line is busy, so the call overflows to Ava.
- Call
Water heater estimate
Homeowner wants a quote to replace a 12-year-old tank water heater.
- Call
Estimate visit booked
Thursday, 10 am to 12 pm window, from the tested schedule. Read back to the caller.
- Call
Summary sent
Booking details and transcript in the AssistCall account for the estimator.
- Web form
Booked online
A customer picks a drain-cleaning slot on the business's booking page.
- Call
Appointment moved
An existing customer moves Friday's service call to Monday. Ava finds it by phone number.
- Call
Out-of-area caller
The ZIP code is outside the approved area. Ava explains and gives the approved next step.
- 41Calls answered after hoursExample
- 9Urgent jobs routed to on-callExample
- 23Routine jobs bookedExample
- 96%Summaries with a full addressExample
- 1 min 52 sMedian time to capture a jobExample
Example only. Fictional business, people and numbers; not a recording or a live account.
Summaries can also be sent on to your other systems through webhooks, and a person still owns each callback. Train the people who take messages to the same seven fields, so a message reads the same whoever, or whatever, took it.
Train it in a week
Day 1: the form
Print the seven fields on a pad, or make them required fields in your software. Remove everything else.
Day 2: read-backs
Practice numbers in groups and spelled names with five made-up calls each, swapping roles.
Day 3: urgency
Hand out ten one-line problems and have each person flag them Now, Today or Can wait. Compare answers and agree the rule.
Day 4: live messages
Take real messages on the form. Whoever receives them marks any field they had to call back about.
Day 5: review
Look at the marked fields. Fix the form or the habit, not the person, and add message quality to your CSR call scorecard.
After the first week, check five messages a week against their recordings or the caller's own account. The fields that keep coming back blank tell you what to fix in the greeting or the script, which is where the phone greeting examples help.
Frequently asked questions
Should I write down exactly what the caller says?
For the problem, yes: in their words, as close as you can manage. For everything else, use the standard fields so the reader finds each detail in the same place every time.
What if the caller won't give an address?
Take the ZIP code and a cross street, note that they declined, and flag it for the person calling back. Without an address nobody can tell whether you cover the job.
Paper pad or software?
Either works if the fields are the same and every message ends up in one place with an owner. Software wins once several people take messages, because nothing sits on a desk waiting to be seen.
Should a message include a price?
Only if the call taker gave one from an approved script, and then write the exact words in field 7. Otherwise write “asked about price” so the reader knows what the callback is for; handling price shopper calls covers what to say.
How fast should messages be returned?
Set it by the flag: Now within minutes, Today within the hour you choose, Can wait by the next working day. Whatever you set, tell the caller and write it in field 7.
References
Pew Research Center (2026). Mobile Fact Sheet (opens in a new tab) ↑
Insurance Information Institute (2019-2023). Facts + Statistics: Homeowners and renters insurance (opens in a new tab) ↑
Pew Research Center (2020). Most Americans don't answer cellphone calls from unknown numbers (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2025). Occupational Outlook Handbook: Plumbers, Pipefitters, and Steamfitters (opens in a new tab) ↑
U.S. Bureau of Labor Statistics, Current Employment Statistics (2026). Average hourly earnings of all employees, plumbing, heating, and air-conditioning contractors, not seasonally adjusted (CEU2023822003) (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (Public Data API) (2025). Occupational Employment and Wage Statistics, May 2025: Dispatchers, Except Police, Fire, and Ambulance (43-5032), hourly median wage, NAICS 238220 (opens in a new tab) ↑