Skip to content
FinnleyAI

What complete phone intake actually captures: a field-by-field guide

By FinnleyAI Team · Builders of FinnleyAI

Most teams think they have phone intake because someone writes down a name and a callback number. What they actually have is a promise to have the same conversation twice. Complete intake means the first conversation produces everything the next person needs to act — without calling back to ask what the caller already said.

Here is the record a well-run intake process produces, field by field, and why each one earns its place.

Who called — claimed vs. verified

There’s a difference between “the caller said they were Dana from Unit 4B” and “the caller was verified as the tenant of record for Unit 4B.” The first is a claim; the second is a fact you can act on. Complete intake records both the identity and how it was established — because sharing account details with, or opening work for, an unverified caller is how impersonation and fraudulent requests get through. Verification isn’t paranoia; it’s what makes every downstream field trustworthy.

What they need — in their own words

The request should be captured close to verbatim, then summarized. Paraphrase-only records lose the details that turn out to matter (“it’s leaking through the ceiling” is different from “there’s a leak”). A good record keeps the caller’s phrasing alongside a plain-language summary the next person can scan in five seconds.

How urgent it is — by your rules, not the caller’s voice

Every caller sounds urgent at 2 AM. Severity should come from written rules — active water gets on-call; a dripping faucet books for business hours — applied the same way on every call. Recording which rule fired matters as much as the severity itself: it’s the difference between a defensible triage decision and a guess.

The context to act without a callback

Whatever the next person needs so they don’t dial the caller back before starting: the site or unit, the equipment involved, access instructions, the affected system, business impact. The specific fields vary by industry — an MSP needs client and asset names; a property manager needs the unit and access notes — but the test is the same: could someone act on this record alone?

What was already done

If the intake step took an action — opened a ticket, booked an appointment, walked the caller through shutting a valve, paged the on-call — that belongs in the record, stated precisely. “Escalated” is not an action; “paged the on-call engineer at 2:19 AM with the summary attached” is.

The disposition — what happens next

Every call should end in exactly one of a small set of outcomes: work created, appointment booked, escalated to a named person, message routed, or safely declined (for callers who couldn’t be verified). If a record can’t say which one occurred, the call isn’t finished — it’s pending, and pending calls are where things fall through.

The receipt — timestamps and transcript

The full transcript with timestamps is the field that makes every other field auditable. When there’s a dispute about what was said, or a triage decision to review, the record settles it. This is also what makes intake improvable: you can’t tune rules you can’t replay.

What does that look like on a real call?

Here’s the shape, on a hand-crafted example (labeled as such — this is an illustration, not customer data):

Example — inbound call, 11:48 PM Caller: Priya S. — verified as tenant of record, Unit 4BRequest (caller’s words): “Water is leaking from under the kitchen sink and spreading fast.” Severity: Urgent — rule: active water intrusion Context: Unit 4B, under-sink supply line; tenant home; no pets; lockbox not needed Actions taken: Work order logged with unit and severity; caller walked through closing the shut-off valve; on-call maintenance notified with summary Disposition: Escalated to on-call maintenance, 11:54 PM Transcript: attached, 6 min 12 sec

Compare that against the alternative that most “answered” calls produce: “Priya called about a leak — please call back.” Both count as answering the phone. Only one of them is intake.

How do you audit your current intake?

Pull the last ten after-hours calls your business received and score each record against the fields above. Three questions expose most gaps:

  1. Could someone have acted on the record alone, without calling the customer back?
  2. Was the caller verified, or just believed?
  3. Was urgency decided by a written rule, or by whoever picked up?

If the answers are mostly no — that’s the gap between having your phone answered and having phone intake. It’s also exactly the record format Finnley produces on every call: see the product overview for how each field gets captured, or how it plays out in a full after-hours emergency call.

Hear Finnley handle your calls.

Book a 15-minute demo and we’ll run your scenarios — your rules, your edge cases — live.