What an AI Answering Service Handoff Packet Should Contain (2026 Field Standard)

The fourth piece in the 2026 buyer's bar series. The previous three covered the standards to evaluate, the 5-call audit to run, and the per-minute trap to do the cost math on. This one is the operational artifact: what the handoff to your on-call tech must contain when the AI is done with the call.

The handoff is the entire point. Everything else is preamble. If the tech receives a handoff packet that lets them roll the truck without a second call, the answering service worked. If the handoff is a callback list with a name and phone number, the answering service failed and the AI was a $49 voicemail with extra steps.

The 11 fields a passing handoff packet contains, in order

Every field below is non-negotiable. Listed in the order a dispatcher reads on a real ticket, so the tech can scan-and-go on a phone screen at 2am.

1. Trade and urgency tier. "HVAC / Emergency" or "Plumbing / Same-day" or "Roofing / Scheduled tomorrow." First line of the handoff. Drives whether the tech rolls now or sleeps.
2. Service address. Full street, city, ZIP. Repeat-back confirmed by the caller on the call. Linked as a Google Maps URL so the tech taps once to start navigation.
3. Callback number. With area code. Repeat-back confirmed. The tech calls this number from the truck if anything is unclear.
4. Caller said (verbatim). One or two sentences in quotes, the caller's own words. "Water coming through the basement ceiling. I think a pipe burst. It's getting worse." This is the field that lets a good tech sketch the failure picture before they get there.
5. Trade-specific symptom capture. Whatever the trade's intake script asks. HVAC: current indoor temperature, unit make and model, last service date, gas-smell yes/no, medical-dependence yes/no. Plumbing: active flow yes/no, shutoff valve status, water color, electrical proximity. Electrical: smoke/sparks/burning-smell yes/no, panel brand, age, water near electrical. Roofing: active entry yes/no, roof material, storm event, tarp status. Garage door: door state, vehicle trapped yes/no, broken-spring loud-bang yes/no.
6. Safety branches fired. Explicit yes/no for each safety question the script asked. "Gas smell: no. Smoke: no. Medical dependence: yes (infant)." If any are yes, the urgency tier in field 1 reflects it.
7. Guidance the AI gave on the call. "Caller was walked to the main water shutoff valve and confirmed it is closed." Or "Caller was told to shut off the breaker at the panel and they confirmed." The tech needs to know what state the home is in when they arrive, so they do not redo guidance the caller already followed.
8. Access notes. Pets, gate codes, lockbox locations, who is home, after-hours rate already confirmed. Tech safety + time-on-site.
9. Unit context. Brand, model, approximate age, last service date. So the tech can pull parts before they roll or confirm scope on the drive.
10. Insurance carrier (if relevant). For roofing-storm, plumbing-water-damage, and fire-restoration calls, the carrier and a claim number if one has been opened. Captured during the call so the homeowner does not have to repeat it.
11. Call recording / transcript link. A signed URL that opens the full recording and the structured transcript. The tech listens to the last 30 seconds during the drive if the handoff is ambiguous.

If your AI answering service does not deliver all 11 fields on a real call, the architecture is wrong. You can script your way to one or two missing fields; you cannot script your way past four.

The failure mode every contractor should refuse to accept

The single most common bad handoff a live answering service delivers is the callback list: a row in a CSV or an email with caller name, phone number, and one sentence summary. The tech has to call the homeowner back to ask the actual operational questions before they can dispatch.

This is the failure mode contractors most often tolerate because it is what voicemail did. A 21st-century AI answering service that delivers the same handoff as 1995 voicemail-to-email is not progress. It is a more expensive voicemail.

Refuse to forward your business number to any vendor whose handoff is "name + phone + one-sentence." Run the 5-call audit and ask explicitly: "Send me the handoff packet I would receive from this exact call." If the packet is not all 11 fields, the vendor failed.

Handoff delivery channels

The packet itself can ship over multiple channels. The minimum-viable contractor configuration in 2026:

• Priority-1 SMS to the on-call tech with fields 1–4 inline (trade, urgency, address, callback) and a link to fields 5–11. SMS guarantees the tech sees the alert; the link guarantees the tech can read the full packet on the drive.
• Email to a shared dispatch inbox with the full packet inline plus the recording / transcript URLs. Email is the audit trail.
• Calendar event dropped into the on-call tech's Google Calendar or equivalent if the dispatch tier is "Scheduled tomorrow" rather than "Emergency tonight."
• Optional webhook into your dispatch software (ServiceTitan, Housecall Pro, Jobber, Field Edge) so the call also appears in your normal ticket queue with all 11 fields attached.

The redundancy is the point. SMS for the tech, email for the audit trail, calendar for the schedule, webhook for the ticket system. A handoff that ships on only one channel will eventually be missed by a tech who already cleared their inbox.

How to apply this on a real demo call

Use this as the field-by-field grading rubric when you run the 5-call audit on any vendor:

1. Play the test call.
2. Receive the handoff.
3. Open it on a phone (this is the real form factor; the tech is on a truck).
4. Count the fields present. 11 of 11 passes. 9 or 10 is a discussion. 8 or fewer is a fail.
5. Read the verbatim "caller said" field. If it is paraphrased rather than quoted, the AI rewrote the homeowner's words, which means subtle symptom signals are lost in translation. Fail.
6. Check the safety-branches-fired field. If any branch shows "not asked," the AI missed a safety question. Fail.
7. Click the call-recording link. If it requires login, password, a 24-hour delay, or a separate dashboard, the tech does not have it on the truck and the field does not count. Fail.

The same rubric applies to OnCrew. If our handoff is missing a field on your real call, we want to know about it. The bar in this piece is the bar we hold ourselves to, and we publish it specifically so contractors can use it against every vendor in the category, including us.

Free 60-question intake checklist that drives the trade-specific symptom capture in field 5: oncrew.ai/tools/contractor-call-intake-questions. Machine-readable JSON version of the same dataset (CC-BY-4.0): oncrew.ai/api/triage-questions.