Key takeaways
- A summary is what your office acts on; the transcript and recording are the evidence behind it.
- Check a daily sample of summaries against recordings, focusing on address, ZIP code, phone number, urgency and the problem described.
- Good summaries save dispatcher time; the median dispatcher wage was $24.20 an hour in 2025[1].
- Set a written retention period for recordings and transcripts, and know your state's call-recording consent rule[2].
Three records from every call
AI call handling usually produces three things after each call. The recording is the audio. The transcript is the audio turned into text, word for word, with each speaker labelled. The summary is a short structured note of what matters: who called, where, what is wrong, how urgent it is and what was agreed. They serve different purposes, and treating them as interchangeable is where most problems start.
Your office should work from the summary. Nobody has time to read a four-minute transcript for every job, and nobody should have to listen to a recording to find an address. The transcript and recording exist to check the summary when something looks wrong, to settle a dispute about what was promised, and to coach. That makes the summary the record that needs the most attention, and the one whose accuracy you should measure.
It also means the summary format is worth designing deliberately rather than accepting whatever a vendor produces by default. A summary written for a dispatcher planning tomorrow's board needs different things at the top than one written for an owner reviewing complaints.
What a useful plumbing summary contains
- Urgency flag at the top: urgent, routine or information only, and the reason in a few words.
- Caller name, callback number and whether they are the owner, tenant or property manager.
- Service address with unit number and ZIP code, read back and confirmed during the call.
- The problem in the caller's own words, plus any detail that changes the job: which fixture, how long, whether water is still running.
- What was agreed: booked window, request for a callback, transfer to the on-call tech, or handover to the office.
- Anything promised: fees mentioned, callback times, instructions given such as turning off the water heater.
- Open questions the office needs to resolve.
- Language used on the call, if not English.
Keep it to what a dispatcher needs in fifteen seconds. Long summaries get skimmed, and skimmed summaries miss the one line that mattered.
Where summaries go wrong
AI summaries are usually fluent, which makes errors easy to miss. The common failures in plumbing calls are predictable:
- Numbers: a misheard house number, a swapped digit in a ZIP code or callback number.
- Names: street names, brand names and model numbers spelled phonetically.
- Urgency: a calm caller describing a serious leak recorded as routine.
- Merged problems: a caller who mentions a slow tub and a leaking water heater ends up with only one in the summary.
- Added detail: a summary that states something the caller never said, such as a cause or an age of the equipment.
- Wrong outcome: a request recorded as a confirmed booking, or the reverse.
A ten-minute daily accuracy check
Pick the sample
Each morning choose five calls: every urgent call from the night, plus a random selection of the rest.
Check the hard facts
Compare the address, ZIP code, callback number and outcome in the summary with the transcript. These four must be exactly right.
Check the meaning
Listen to the first and last minute of the recording. Does the summary's problem and urgency match what you hear?
Log errors by type
Keep a simple tally: numbers, names, urgency, merged problems, added detail, wrong outcome.
Fix the cause
Two errors of the same type in a week means a rule, script or knowledge base entry needs changing, not just a correction to that one record.
Target for the hard facts: zero errors. A summary can be clumsy and still useful; a wrong address cannot.
Why accurate summaries are worth the effort
The value of a summary is the time it saves the people who act on it. The median wage for dispatchers outside emergency services was $50,340 a year, or $24.20 an hour, in 2025, ranging from $36,030 at the 10th percentile to $78,140 at the 90th[1]. If a dispatcher has to re-listen to recordings because summaries cannot be trusted, that is paid time spent repeating work the system was meant to do.
Example: a shop handling 40 calls a day finds its dispatcher re-listening to about a third of them, three minutes each, because summaries often miss unit numbers. That is roughly 40 minutes a day. After the read-back script is changed to ask for the unit number on every apartment address, re-listening falls to a handful of calls. The time goes back into planning the board and calling customers with arrival updates.
Getting summaries into your CRM
Summaries are most useful where your team already works. Whether they arrive by email, in a shared inbox or directly in your field-service software, map each part of the summary to a field so it can be searched and reported on.
| Summary item | CRM or job field | Who uses it |
|---|---|---|
| Urgency flag | Job priority | Dispatcher, on-call tech |
| Caller and role | Customer and contact record | Office, billing |
| Address and ZIP | Service location | Dispatcher, tech |
| Problem description | Job notes or complaint field | Tech before arrival |
| Outcome | Job status: booked, request, handed over | Office |
| Promises made | Job notes, highlighted | Tech, office |
| Recording and transcript link | Attachment on the job | Manager, for checks |
Ava sends a job summary with the recording and transcript to your AssistCall account and inbox after each call, with urgent jobs marked urgent; direct job creation in field-service software is a Planned feature, so for now the office copies booked work across or works from the inbox.
Recording consent and retention
Federal law allows a call to be recorded when the person recording is a party to the call or one party has given prior consent, but some states require the consent of all parties[2]. If you take calls from all-party consent states, a short notice at the start of every call is the simple way to stay covered. Check your state's rule with your attorney if you are unsure.
Recordings and transcripts contain personal information: names, addresses, phone numbers and sometimes details about who is home. Keep them only as long as you need them. Larger businesses face specific duties; the California Consumer Privacy Act, for example, applies to for-profit businesses in California with gross annual revenue over $25 million, among other thresholds[3]. Smaller shops should still write a retention rule:
- Summaries: keep with the job record as long as you keep job history.
- Transcripts and recordings: a fixed period, often 90 days to a year, unless tied to a complaint, claim or warranty issue.
- Disputed calls: keep until the matter is closed, then apply the normal period.
- Access: limit who can listen to recordings and record who does.
When a customer disputes what was said
Sooner or later a customer will say they were promised something: a free visit, a morning arrival, a price. The records turn an argument into a quick check. Use them in this order:
- Read the summary's promises line to see what the system recorded as agreed.
- Search the transcript for the words in dispute, such as free, morning or the amount.
- Listen to that part of the recording to hear tone and context, which transcripts can lose.
- If the customer is right, honor it and fix the script or knowledge base entry that allowed it.
- If the record shows no promise, explain calmly what was said, offer to send the relevant part of the transcript, and still look for a fair way to keep the customer.
Tell staff that records exist to get facts straight, not to win arguments. A customer who misremembered and is treated respectfully often becomes loyal; one who is proved wrong in a cold email rarely does.
Using records to coach and improve
The Bureau of Labor Statistics lists communication as a key quality for plumbers because they talk to customers regularly[4]. Transcripts give you a library of real conversations to learn from: how customers describe problems, what questions they ask before booking, and which explanations calm them down. Share good examples with technicians before ride-alongs and with new office staff during training, and add recurring questions to your knowledge base.
Frequently asked questions
Is an AI call summary accurate enough to dispatch from?
It can be, once you have checked a sample for a few weeks and fixed the causes of errors. Always confirm address, ZIP code and callback number are read back during the call.
Should we keep call recordings forever?
No. Set a fixed retention period, keep recordings longer only when tied to a complaint, claim or warranty issue, and limit who can access them.
Do we need consent to record calls?
Federal law requires at least one party's consent, and some states require all parties' consent. A short recording notice at the start of each call covers both.
What is the difference between a transcript and a summary?
A transcript is the full word-for-word text of the call. A summary is a short structured note of the facts and outcome that your office acts on.
References
O*NET OnLine (U.S. Department of Labor), BLS 2025 wage data (2025). National Wages 43-5032.00 - Dispatchers, Except Police, Fire, and Ambulance (opens in a new tab) โ
Legal Information Institute, Cornell Law School (2026). 18 U.S. Code ยง 2511 - Interception and disclosure of wire, oral, or electronic communications prohibited (opens in a new tab) โ
State of California Department of Justice, Office of the Attorney General (2026). California Consumer Privacy Act (CCPA) (opens in a new tab) โ
U.S. Bureau of Labor Statistics (2025). Occupational Outlook Handbook: Plumbers, Pipefitters, and Steamfitters (opens in a new tab) โ