Proposed capability · not available
Proposed call summaries
A short, structured record of every call — who called, what they need, what they were told and who owns the next step — delivered where your team already works.
A call that was answered well but summarised badly still fails. The dispatcher has to call the customer back to ask for the address again, the technician arrives without knowing about the dog in the yard, or the comfort advisor walks into an estimate that the caller thought was a repair visit.
Vendors emphasise summaries for good reason. Smith.ai’s HVAC page says every interaction produces a detailed call summary delivered by email, Slack or text, and its call-intelligence page lists caller type, priority and disposition among the metadata captured. Avoca’s ServiceTitan page describes jobs arriving on the board with customer name, address, service type and call notes. Those are vendor claims; we have not tested them.
What a useful HVAC call summary contains
The proposed summary would use one fixed order, so a reader always knows where to look:
| Field | Example (placeholder) | Why it is there |
|---|---|---|
| Call type and priority | No cooling · urgent under after-hours rule 2 | Tells the reader what kind of action is needed and why. |
| Next owner and deadline | On-call tech · acknowledge within 10 min | Every call has one owner. |
| Caller and callback number | Name · number read back and confirmed | Callback failures are the most common rework. |
| Service address and access | Street address · gate code on file · dog in yard | Saves a call on arrival. |
| Relationship to property | Tenant; property manager to approve work | Determines who can authorise the job. |
| Caller’s words | “Upstairs is warm, unit outside is running” | Preserves meaning. |
| Structured details | System type, approximate age, plan member, prior visits | What your checklist asked for. |
| What the caller was told | “Office will confirm a time by 9 a.m.” | So nobody contradicts it. |
| Safety question answer | No gas odor, CO alarm, burning smell or smoke reported | Proves it was asked. |
The same call, summarised two ways
A weak summary reads like a message slip:
Customer called about AC. Wants someone to come out. Call back.
It leaves the dispatcher to find out the address, whether it is urgent, whether the caller owns the home and what they were promised. Every one of those is a second phone call.
A usable summary of the same call, in the fixed order above:
No cooling · standard priority (rule: occupied home, no vulnerable occupants reported, daytime). Next owner: dispatch, schedule today or first slot tomorrow. Caller: homeowner, callback number confirmed. Address and gate code confirmed; dog in back yard. Caller’s words: “Upstairs is warm, the outside unit is running.” Existing customer, maintenance-plan member per caller. Told: “Dispatch will text you a window by 4 p.m.” Safety question asked: none reported.
Nothing in the second version requires judgement the receptionist should not make. It records what was asked, what was said and which of your rules applied.
Every call gets an outcome, not only the good ones
A summary log that only contains booked jobs hides the calls that went wrong. Smith.ai’s call-intelligence page describes tagging each call with a caller type such as new lead, existing customer or spam, plus a priority and a disposition, and shows whether a call was handled by AI or escalated to a person. Whatever tool you use, the useful discipline is the same: every call ends with one outcome from a short fixed list.
| Outcome | What it means for the office |
|---|---|
| Job request created | Dispatch owns scheduling; caller was told when to expect contact. |
| Handed to a person live | Name of the person who took it, and whether they accepted. |
| Callback owed | Owner, deadline and the reason it could not be completed on the call. |
| Information only | Question answered from approved information; no action owed. |
| Not a customer call | Spam, sales, wrong number; logged, no action. |
| Incomplete | Caller hung up or the line dropped; what was captured before it ended. |
“Callback owed” and “Incomplete” are the outcomes to review first each morning. They are where calls quietly get lost, and they feed the callback queue, the proposed missed-call follow-up and your missed-call measurement. Where summaries sit in the overall call flow is shown in how HVAC Reception would work.
Summary, transcript and recording are three different records
- The summary is for acting. It should be readable in under a minute.
- The transcript is for checking what was said, word for word, when the summary is disputed or unclear.
- The recording is for tone and anything the transcript missed.
Ask any provider how long each is kept and who can access it. Retention differs by vendor: Smith.ai’s recording page, for example, says recordings and transcriptions stay in its dashboard for 90 days. If your office needs older records — for a warranty dispute or a complaint — plan to export them, and check your own obligations before recording calls at all. We do not give legal advice on call recording; rules differ by location.
New caller or existing customer
A summary that creates a second customer record for someone already in your system causes quiet damage: split service history, missed plan benefits, a technician who does not know the equipment was replaced last year. Avoca’s ServiceTitan page says its integration recognises existing customers and matches new bookings to their profiles to avoid duplicates; that is the vendor’s description of its own product.
Without any integration, the proposed summary would simply record what the caller said — “says they are an existing customer”, “says they have a maintenance plan” — and leave matching to your office. Stating the source of the fact is what matters. “Plan member (per caller)” and “plan member (confirmed in system)” are different claims.
Delivery, by receiver
A summary is only useful if it lands where the receiver already looks. The handoff templates set out formats for each receiver: a short text for the on-call technician, a job-ready record for the dispatch board, a lead record for the comfort advisor, and an owned task for the callback queue.
What the concept proposes
- A summary for every call, including spam and wrong numbers, so the log is complete.
- Fixed field order per call type, drawn from the call-intake checklists.
- The caller’s own words kept alongside structured fields.
- A clear record of what the caller was told.
- No invented details: fields the caller did not provide are marked as not captured rather than guessed.
What it would not do
- It would not claim a job was booked unless it was booked under your rules.
- It would not write summaries directly into field-service software; the concept has no integrations.
- It would not infer equipment faults from what the caller described.
How to evaluate summaries from any provider
Ask for five real summaries from HVAC calls, with personal details removed. Check whether each one tells you the next owner, what the caller was told, and the callback number, without opening the recording. If you have to listen to the call to act, the summary is not doing its job.
Then ask:
- Is there a summary for calls that did not book — hang-ups, spam, wrong numbers — or only for leads?
- Does each summary show whether a person was involved, and who?
- Which fields are required, and what happens when the caller will not give one?
- How are facts the caller stated distinguished from facts checked in your records?
- Where are summaries delivered after hours, and who is expected to read them?
- How long are summaries, transcripts and recordings kept, and can you export them?
More questions for comparing providers are in questions to ask answering-service vendors.
Sources for vendor descriptions
Vendor statements above are those companies' own descriptions of their products, read on the dates shown. They are not verified by us and may have changed. Check current details with each vendor.
- Smith.ai — Receptionist services for HVAC companies — read 2026-09-26
- Smith.ai — Call analytics and call intelligence — read 2026-09-26
- Smith.ai — Call recording and transcription — read 2026-09-26
- Avoca — ServiceTitan integration — read 2026-09-26
Frequently asked questions
What is the difference between a call summary and a call transcript?
A transcript is everything that was said. A summary is the handful of facts someone needs to act, in a fixed order. Transcripts are useful for review and disputes; summaries are what dispatchers and technicians actually read.
Where would HVAC Reception send summaries?
In the proposed design, to the channels your team already uses — email, text, a shared inbox, or a field-service system if a supported connection existed. The concept has no integrations today, so we do not claim any.
Would summaries include the caller's own words?
Yes, for the problem description. Paraphrase can change meaning — 'no heat' and 'not enough heat' lead to different decisions — so the proposed summary keeps a short quote alongside the structured fields.
Is this available?
No. Call summaries are a proposed capability of a concept. The format on this page is useful for any answering service or in-house team.