# AI Receptionist Message Taking: What 46 Real Messages Showed Us (2026)

Author: Kris Hubbard
Published: October 30, 2026
Updated: October 30, 2026
Canonical: https://wrkless.com/blog/ai-receptionist-message-taking

**Short answer:** An AI receptionist takes a good message when it captures five things (who's calling, a callback number, what they need, where the job is, and who the message is for), reads them back before hanging up, and sends the message to the right person within minutes. On the two lines of a fence and gate contractor we support, 46 calls from October 12 to 29, 2026 ended with a finished message. The assistant read the details back on 43 of them, and twice the caller caught a mistake. The weak spot came earlier in the call. When callers asked for someone by name and heard that person was in the field, 10 of 34 hung up, and 8 of those 10 left within 21 seconds.

Below is what we pulled from those calls, the fields we capture, the routing we use, and a checklist you can test against.

## What does an AI receptionist message need to include?

A message is only useful if the person who gets it can act without calling back to ask questions. We capture these on every message-taking line:

| Field | Why it matters | How we capture it |
|---|---|---|
| Caller name and company | Builders, pool companies and vendors call as often as homeowners | Ask once, early. Spell back uncommon names |
| Callback number | The whole point of the message | Read it back digit by digit in groups. Confirm it's the number they want called back |
| Reason for the call | "Call me back" doesn't tell the owner whether it's a new job or a sales pitch | One plain question: "What do you need [Name] to help with?" |
| Job address | Field businesses route and quote by address | Ask only when the reason is a quote, repair or install |
| Who it's for | Calls for the owner, the office manager and the bookkeeper shouldn't land in one inbox | Match the name the caller asked for to a staff list |
| Urgency | A gate stuck open isn't a Tuesday callback | Ask "Is anything unsafe or stuck right now?" when the reason sounds like a repair |

Retell, the voice platform we build on, can pull these out after the call as structured fields. Its Post Call Extraction supports text, number, boolean and selector fields, and the results arrive on the `call_analyzed` webhook under `custom_analysis_data`. The `call_ended` webhook doesn't include them, which trips up a lot of first builds. Our [Retell integrations and webhooks](/retell-ai-integrations-and-webhooks.php) page covers the handoff.

## What we saw in 46 real messages

We review every call on the lines we manage. From October 12 to 29, 2026, the contractor's business and owner lines had 46 calls that ended with the assistant wrapping up a completed message. The median one took 79 seconds, and they ranged from 36 to 187.

What the callers wanted:

- **33 were about jobs.** Quotes, repairs, gate problems, builders and pool companies checking on installs, a crew member updating the owner on posts left to set.
- **3 were vendors or billing.** An accounts payable clerk, a supplier chasing past-due invoices, a store following up on an order.
- **4 were the owner's own accounts.** Insurance renewals and bills, season tickets.
- **4 were sales pitches.** Ads, mailers, software.
- **2 didn't say enough to tell.**

So roughly 1 in 4 finished messages wasn't about a job. If every message goes to the owner's phone the same way, the job calls get buried. Sorting them is cheap, because the assistant already asked why they called.

**The readback earned its keep.** The assistant read the details back on 43 of the 46 calls. Two callers corrected it. One fixed a name on an insurance policy. The other said "the number is incorrect" after the assistant read back a callback number that was only 8 digits long. Without the readback, that message would have gone to the owner with no way to call back.

**Urgent calls need more than a message.** Three messages were about something stuck or broken right now, including an electric gate stuck open. One caller with a gate stuck halfway open called twice, 7 minutes apart. A message is fine for a quote. It isn't enough when someone can't get into their driveway.

## Why do callers hang up before leaving a message?

The biggest loss wasn't a bad message. It was a message that never started.

On the same two lines, 34 calls followed one pattern: the caller asked for someone by name, and the assistant said "[Name] is out in the field right now, but I'll get your message straight to [them]. What's your name?" Then:

- 24 stayed and finished the call.
- 10 hung up.
- 8 of those 10 left within 21 seconds, right after hearing the person was out and being asked for their name.

Those callers wanted a person, not a form. A few ideas we use to keep more of them:

1. **Say when they'll hear back.** "[Name] checks messages between jobs and usually calls back the same day" gives a reason to stay. Only promise what's true.
2. **Lead with what they asked for.** "I can get this to [Name] right now" before "What's your name?"
3. **Offer the human path for the right calls.** At an accounting office we support, staff are at desks, so most callers who ask for someone get transferred. That office had 27 transfers in the same period. Our [transfer-to-human guide](/blog/ai-receptionist-transfer-to-human) covers when that's the better design.
4. **Treat the hang-up as a missed call.** The number is still in the log. Our [missed-call text-back rules](/blog/missed-call-text-back-tcpa-2026) cover when a follow-up text is allowed.

The first few seconds matter too. Our [AI receptionist greeting script](/blog/ai-receptionist-greeting-script) covers what to say before the caller decides whether to stay.

## How should messages get to the right person?

On this build, Retell sends the finished call to an n8n workflow. The workflow checks that the message isn't empty, sorts it by who it's for, and emails it to the owner, the business inbox or the office admin. Every call is logged as well. That's the pattern we'd start with on any field business:

- **Wait for `call_analyzed`.** Read the extracted fields there, not from `call_ended`.
- **Drop empty messages.** Retell doesn't fill custom extraction fields when no conversation took place, so check that a field exists before you send anything.
- **Route by name and reason.** Jobs go to whoever quotes and schedules. Vendors and billing go to the office. Sales pitches go to a low-priority digest.
- **Page for urgent calls.** Anything stuck, broken or unsafe goes out right away as a text or a transfer, not in a morning summary.
- **Flag repeat callers.** Two calls from the same number in an hour means the first message didn't land. Our [caller memory post](/blog/ai-receptionist-remembers-callers) shows how to spot them.
- **Acknowledge the webhook fast.** Retell retries if it doesn't get a 2xx response within 10 seconds, so deduplicate on the event and call ID.

If you'd rather the message become a CRM task, gate it on the extracted reason so a 4-second call doesn't create a hot lead. Our [post-call task workflow](/blog/ai-create-tasks-after-seller-calls) walks through it. Spam is its own problem, and our [AI receptionist spam calls post](/blog/ai-receptionist-spam-calls) covers filtering it before it reaches anyone.

On HighLevel, the same idea runs through Voice AI actions. Use Trigger Workflow or the Transcript Generated workflow trigger to send the summary and transcript to the right user. That trigger lets you set a minimum call duration to skip short calls.

## Settings that make the readback reliable

- **Turn on echo verification.** Retell's Agent Handbook has an Echo Verification preset that repeats back names, phone numbers and other key details, and spells uncommon names letter by letter. It's off by default.
- **Read numbers in groups.** Retell's prompt guidance reads 415-892-3245 as "four one five - eight nine two - three two four five." Grouped digits are easier for callers to check.
- **Count the digits.** If the callback number isn't 10 digits, ask again before the readback, not after.
- **Offer the keypad.** In a noisy truck or job site, ask the caller to type the number. Retell captures keypad (DTMF) input, with settings for digit limit, a termination key and a timeout.

## Message-taking checklist

- [ ] The assistant captures name, company, callback number, reason, address and who it's for
- [ ] It reads the details back and waits for a yes before ending the call
- [ ] Callback numbers are checked for 10 digits before the readback
- [ ] Callers who ask for someone hear when they can expect a callback
- [ ] Urgent repairs go out as a text or transfer, not a queued message
- [ ] Messages are routed by person and reason, not all to the owner
- [ ] Sales pitches go to a low-priority digest
- [ ] Empty or no-conversation calls don't send a message
- [ ] Repeat callers within an hour are flagged
- [ ] Hang-ups during the greeting are treated as missed calls
- [ ] You've placed five test calls, including one with a wrong number on purpose, and checked each message that arrived

## Want messages your team can act on?

We'll review your recent calls, fix where callers drop off, and set up message routing so the right person gets each call. [Book your AI systems assessment](https://cal.com/kris-hubbard-wrk-less/ai-systems-assessment). You can also see how our [missed-call capture](/missed-call-capture.php) and [AI receptionists for small businesses](/ai-receptionist-for-small-businesses.php) work, or read how we handle [after-hours calls for trades](/blog/after-hours-answering-service-plumbers-hvac).

## Questions people ask

### Can an AI receptionist take messages?

Yes. A well-built AI receptionist asks for the caller's name, callback number, reason for calling, job address and who the message is for, reads those details back, and sends the message to the right person after the call. On the contractor lines we reviewed from October 12 to 29, 2026, 46 calls ended with a completed message, and the assistant read the details back on 43 of them.

### What should an AI receptionist ask when taking a message?

Ask for the caller's name and company, the best callback number, what they need, the job address if it's a quote or repair, and who the message is for. Ask whether anything is unsafe or stuck right now when the reason sounds like a repair, so urgent calls go out as a text or transfer instead of waiting in a queue.

### Why do callers hang up on an AI receptionist when the person they want is out?

They wanted a person, not a form. On the contractor lines we reviewed, 34 callers asked for someone by name and heard that person was out in the field. 10 of them hung up, and 8 of those left within 21 seconds, right after being asked for their name. Telling callers when to expect a callback, and transferring the calls that need a person, keeps more of them on the line.

### How does an AI receptionist send messages to the right person?

After the call, the voice platform sends the call data to a workflow. On Retell, wait for the call_analyzed webhook, which carries the extracted fields. The workflow then checks that the message isn't empty and routes it by who it's for and why they called. Jobs go to whoever quotes, billing goes to the office, sales pitches go to a digest, and urgent repairs go out right away.

### Should an AI receptionist read the message back to the caller?

Yes. In the 46 completed messages we reviewed, callers corrected the readback twice, once for a wrong name and once for a callback number that was only 8 digits long. Retell's Echo Verification preset, which is off by default, makes the agent repeat names and numbers back. Read phone numbers digit by digit in groups so callers can check them.

## Sources

- https://docs.retellai.com/features/post-call-analysis-overview
- https://docs.retellai.com/features/post-call-analysis-create
- https://docs.retellai.com/features/post-call-analysis-consumption
- https://docs.retellai.com/features/webhook-overview
- https://docs.retellai.com/build/agent-handbook
- https://docs.retellai.com/build/prompt-situation-guide
- https://docs.retellai.com/build/user-dtmf
- https://help.gohighlevel.com/support/solutions/articles/155000005267-separate-during-call-and-post-call-actions-in-voice-ai
- https://help.gohighlevel.com/support/solutions/articles/155000006632-workflow-trigger-transcript-generated
- Wrk Less call review, Retell API pull of the voice lines we manage, Oct 12-29, 2026 (18 days; pulled Oct 30, 2026). Fence and gate contractor, two lines (business and owner): 46 calls ended with the assistant completing a message (median 79 seconds, range 36 to 187 seconds). Assistant read the details back on 43 of the 46. 2 readbacks corrected by the caller (a name on an insurance policy; a callback number only 8 digits long, caller said the number is incorrect). Message types: 33 about jobs, 3 vendors or billing, 4 owner's own accounts, 4 sales pitches, 2 unclear; roughly 1 in 4 not about a job. 3 messages about something stuck or broken right now; one caller with a gate stuck halfway open called twice, 7 minutes apart. 34 calls where the caller asked for someone by name and the assistant said the person was out in the field: 24 stayed and finished, 10 hung up, 8 of the 10 within 21 seconds. Accounting office line: 27 transfers to staff in the same period
- Wrk Less build notes, contractor message line (checked Oct 30, 2026): Retell post-call webhook to an n8n workflow; filter for non-empty message; switch by recipient; Gmail to owner, business inbox or office admin; every call logged to a shared call log workflow
- Retell webhook overview, checked Oct 30, 2026: webhook timeout 10 seconds, retried up to 3 times if no 2xx; deduplicate on event plus call_id; call_ended excludes call_analysis; call_analyzed includes it
- Retell Agent Handbook, checked Oct 30, 2026: Echo Verification preset, default disabled, repeats back names, phone numbers and other critical details, spells uncommon names letter by letter. Prompt guide: 415-892-3245 becomes four one five - eight nine two - three two four five
- HighLevel Transcript Generated trigger, modified Feb 19, 2026: optional minimum call duration filter (e.g., greater than 30 seconds); Voice AI During the Call actions include Trigger Workflow
- Wrk Less message-taking rules: about 10 digits for a US callback number; flag 2 calls from the same number within an hour; 4-second calls should not create a hot lead; five test calls including one with a wrong number on purpose