# Answering Telephone Calls: A Practical Guide for Intake

> [llms.txt](https://www.lighthouselegal.ai/llms.txt)

Learn answering telephone calls step by step: open the call, identify caller needs, confirm callback details and direct the next step clearly.

URL: https://www.lighthouselegal.ai/learn/answering-telephone-calls

[Learning center](https://www.lighthouselegal.ai/learn)

October 29, 2026

## Answering Telephone Calls: A Practical Guide for Intake

Learn answering telephone calls step by step: open the call, identify caller needs, confirm callback details and direct the next step clearly.

-   answering telephone calls
-   telephone etiquette
-   call intake
-   phone answering tips
-   intake calls

It's 8:40 p.m., and someone who was just in a crash is on your line, talking fast and unsure anyone is there. Answering telephone calls well means more than a pickup. The caller needs to feel heard, and you need facts you can use without promising something the firm has not agreed to do.

### The Four Stages of Answering Telephone Calls

The [Lighthouse Chandler Conway case study](https://www.lighthouselegal.ai/case-studies/chandler-conway) reports that the caller tried four other firms before Lighthouse answered. Being reached is the first measure of good answering. A missed ring is not a short delay. It is a person who may never get another chance to tell you what happened.

A usable call then has four stages. Each stage has one job and a **done-when** signal, so you know when to move on.

1.  **Answer and open.** Pick up promptly, greet the caller with the firm name, and give the reviewed recording notice. Done when the caller knows they reached the firm and what the call is for.
2.  **Understand.** Let the caller explain, acknowledge what was said, and ask only for missing facts. Done when the main account and the key gaps are clear.
3.  **Secure.** Confirm the name and a callback number early enough to reconnect if the line drops. Done when the firm can reach this person again.
4.  **Direct.** Escalate, transfer under the firm's configured process, or explain the next step. Done when the caller knows exactly what happens next.

![A four-step infographic illustrating best practices for effectively answering business telephone calls to ensure good service.](https://cdnimg.co/11a2db61-834c-48a5-b6b6-a28a4c32e2c5/e2cdb143-634d-4133-987f-2202ae3627eb/answering-telephone-calls-customer-service.jpg)

That sequence is what turns a live answer into intake, not a greeting that dies in voicemail. The short guide on [what legal intake is](https://www.lighthouselegal.ai/learn/what-is-legal-intake) sets the boundary: you are collecting facts for review, not deciding the case on the phone.

> **Practical rule:** If you can't say what happens next in one sentence, the call isn't finished.

### Opening the Call Without Losing the Caller

A caller hears the first few words before deciding whether to stay on the line. Give them the firm name and a clear, brief opening, then let them speak. A [Texas Legislative Budget Board staff report](https://www.lbb.texas.gov/Documents/Publications/Staff_Report/2019/4729_Contact_Centers.pdf) found that consumers calling customer-service centers were willing to wait an average maximum of **13 minutes**, yet **49%** abandoned before the 10-minute mark. About **22%** hung up in less than five minutes, and another **27%** hung up within 10 minutes. A caller who disconnects may leave the team without the facts needed for a useful callback.

A widely used contact-center benchmark, described by [Nectar Desk](https://www.nectardesk.com/call-center-statistics-2026/), is the **80/20 standard**: answer at least **80%** of inbound calls within **20 seconds**. Track abandonment by hour in 15- or 30-minute blocks. An average speed of answer can conceal a brief queue at lunch or after 6 p.m., especially when one person is covering the line.

#### What the opening actually says

Use distinct wording for the greeting, any AI introduction, and the recording notice. The notice should be the wording the firm has reviewed for the caller's jurisdiction.

| Element | Example wording | When to adjust |
| --- | --- | --- |
| Firm greeting | Thank you for calling [Firm]. | Keep it in every call |
| AI introduction | I'm the firm's AI assistant. | Keep separate from the recording notice |
| Recording notice | This call is being recorded. | Use only if this wording has been reviewed for the caller's jurisdiction |
| Offer to help | I can take some details for the team. | Skip if the caller is already explaining |
| Open question | What happened? | Drop if the caller has begun the account |

Federal law generally permits recording when at least one participant consents, but the [Reporters Committee for Freedom of the Press](https://www.rcfp.org/introduction-to-reporters-recording-guide/) identifies about **11 states** with primarily all-party-consent rules, including California, Florida, Illinois, Pennsylvania, and Washington. Missouri and Oregon also treat telephone calls differently from in-person conversations. Use the notice the firm has reviewed for the caller's location; don't treat a sample line as legal approval. Keep the notice separate from the AI introduction.

#### When the caller won't wait for the script

If the caller is already explaining a crash, don't make them start over to finish the greeting. Acknowledge what you heard and move into the conversation. For example: "I understand this happened yesterday. Tell me what happened next."

Keep the opening brief enough to say naturally: "Thank you for calling \[Firm\]. I'm the firm's AI assistant, and I can take some details for the team." If the caller begins speaking, stop the script and listen. Done when the caller knows they've reached the firm and has room to explain why they're calling.

### Identifying What the Caller Needs

![A professional support agent wearing a headset taking a call from a distressed car accident victim.](https://cdnimg.co/11a2db61-834c-48a5-b6b6-a28a4c32e2c5/3505320e-548b-49b0-a1d1-8a74cb3f0158/answering-telephone-calls-support-agent.jpg)

A caller may begin with the whole story before you ask a question: "We got hit yesterday on the way home, the other driver ran the light, and I can't stop crying." The first task is to hear what they have already told you. Starting over with a scripted question makes the caller repeat themselves and weakens trust.

Secret-shopper testing of law firm phone lines has repeatedly found that many firms do not answer test calls. Answering is only the first stage. Each call is also an intake experience, and a promise the team cannot keep can undo the trust built in the opening.

#### Listen, name one fact, ask one gap

Let the caller finish the immediate thought. Acknowledge one fact they gave, then ask for one missing detail.

> I understand this happened yesterday. Where did it happen?

The done-when signal for this stage is simple: the caller has had room to explain, and your next question asks only for information you still need. Don't repeat an answer that is already clear. Re-asking turns a conversation into a form and can make a distressed caller feel unheard.

The [personal injury intake questions guide](https://www.lighthouselegal.ai/learn/personal-injury-intake-questions) covers common fields. On the call, prioritize the next relevant question over completing a list in order.

#### Pace when someone is upset

If a caller is crying or repeating part of the story, slow down. Use short sentences and allow a pause instead of filling the silence with another question.

"Take your time. I'm sorry this happened." After a moment, ask: "Are you safe to talk right now?" The done-when signal is that the caller has answered, or indicated they need time, and you know whether it makes sense to continue. Offer only a next step the firm can deliver.

Keep the questions within the role of intake:

-   **Don't guess fault.** "They ran the light" is the caller's account, not a finding.
-   **Don't predict an outcome.** The firm has not reviewed the case yet.
-   **Don't interrogate.** If the caller has already said where it happened, ask about the next gap.

Intake gathers information for review. It does not establish representation. The call goes well when the caller feels heard, the notes capture what they said, and the next step is stated without promising more than the firm can provide.

### Confirming Callback Details Early

"If we get cut off, I want a number that reaches you." Confirm the callback number after acknowledging the caller, before asking for the full account. A clear reason makes the question feel practical rather than abrupt.

A [published personal-injury intake framework from Hona](https://www.hona.com/guides/ai-receptionist-personal-injury) lists four or five initial questions as typically enough to get started. It includes a callback number alongside the incident date and location, what happened, injuries and treatment, and other involved parties. Establish a reliable way to reconnect, then gather the remaining details at a pace the caller can manage.

| Detail | When to confirm | Why it matters |
| --- | --- | --- |
| Caller name | After the first acknowledgement | Identifies the caller and anchors the notes |
| Callback number | Read back before deeper questions | Gives the team a way to reconnect if the line drops |
| Incident date | After the caller has finished the main account | Sets the timeline without repeating known facts |
| Incident location | When the caller pauses or after the date | Gives the firm a location to review |
| Injuries and treatment | After the story is clear | Gives the firm details for review, without pressing the caller |
| Other parties | Last, if the caller is still engaged | Completes the picture for the firm |

#### How to read a number back

1.  Repeat the digits in groups, as the caller gave them, rather than as one long string.
2.  Ask for confirmation: "Is that right?"
3.  Wait for a clear yes before moving on. If the answer is uncertain, ask once more, slowly.

For the name, keep the request simple: "How do you spell your last name, so I don't write it wrong?" If the caller spells it, read the spelling back once.

Document the confirmed number in the intake notes, not on a scrap of paper that might get separated from the inquiry. If staff also use a form to route follow-up details, [FormBackend's Twilio integration](https://www.formbackend.com/integrations/twilio) is one option for passing phone digits into that system.

The stage is done when the notes contain a number the caller has confirmed and someone at the firm can use to reach them.

### Directing the Caller to the Right Next Step

The instinct on a live call is to answer every question the moment it's asked. That instinct is what turns intake into an improvised consultation. A personal-injury telephone intake should stay a fact-gathering process. The [personal injury intake framework published by LegalVoice](https://legalvoice.app/resources/personal-injury-intake-script) says the agent should stop and escalate when a caller needs legal judgment, reports distress, asks for a person, or reaches another firm-approved boundary. Changing your wording does not authorize a legal conclusion, advice, a promise of a consultation, or skipping that escalation.

![A diagram outlining a decision tree for call handling: continue intake, escalate the call, or transfer the call.](https://cdnimg.co/11a2db61-834c-48a5-b6b6-a28a4c32e2c5/a3098ecb-8d10-49c9-9a9e-92b2c5e1fab3/answering-telephone-calls-call-handling.jpg)

#### Stop and hand it off

Stop the questions when any of these show up:

-   **Needs legal judgment.** "Do I have a case?" is not an intake field.
-   **Reports distress.** Safety and a human come before the next fact.
-   **Asks for a person.** Honor that. Don't talk them out of it.
-   **Asks about fault, outcome, or fees.** You don't have authority to answer those.
-   **Hits a firm-approved boundary.** Whatever your firm listed as a stop, treat it as a stop.

You can keep the tone warm while you stop. You can't keep going and "just give a sense" of the case. Teams that automate the handoff still need a human rule at this point. Writing on [improving reliability in automated legal workflows](https://matteralert.com/blog/legal-workflow-automation) is useful background for why a workflow fails when the exception path isn't defined.

#### What you say on each path

**Continue** when the caller is answering and you're still collecting the firm's criteria. "Thank you. The next thing I need is where this happened."

**Escalate and stop** when a trigger above is met. "I'm going to stop here and pass this to the team, because this needs a person, not more questions from me."

**Transfer** only under the firm's configured process. Name the daytime or after-hours contact the firm has set. "I'm connecting you to the contact set for this hour." Don't promise that an attorney is free. How that route is built is covered in [law firm call routing](https://www.lighthouselegal.ai/learn/law-firm-call-routing).

After hours, during overflow, or when nobody is available, follow the configured after-hours process. Take the details, confirm the callback number, and state only the review timing the firm has set. If no timing is set, don't invent one.

### Phone Etiquette Mistakes That Erode Trust

Polite wording doesn't save a call if the behavior underneath it is careless. The mistakes that cost trust are ordinary: talking over the caller, leaving a silence you never explain, asking again for something they already answered, guessing fault or an outcome, and promising an attorney callback that nobody has agreed to handle.

A [legal answering guide from AMBS](https://www.ambscallcenter.com/blog/answering-service-personal-injury-law-firms?hs_amp=true) warns that an agent should not promise an arrival time, a result, a legal outcome, a price, or a technical fix unless written instructions and a connected system support that promise. An unsupported "an attorney will call you back" is the same kind of promise. The caller hears a commitment. If no owner and no time exist, you have set them up to be let down.

| Mistake | What the caller hears | Better response |
| --- | --- | --- |
| Talking over the caller | Interruptions before the point is finished | Pause, then acknowledge what was said |
| Unexplained silence | Dead air with no sign the agent is still there | "One moment while I note that." |
| Repeating answered questions | "You already told me that" | Ask only for what is missing |
| Unagreed attorney callback | A promise with no owner or timing | Confirm the name and number, then state only what the firm will do |

#### The safer close on a callback

Confirm the name and the callback number. Note the request. State only the next step the firm can fulfill: the team reviews what you collected and decides whether it can help. That is slower to say than "someone will call you tonight." It is also the sentence you can stand behind at 9 p.m., when no attorney is on the rotation.

Silence needs a label. "One moment while I note that" tells the caller you're still there. A gap with keyboard noise does not.

Tone and pace are skills, not a script. The [communication skills advice from VoiceType](https://voicetype.com/blog/how-to-improve-communication-skills) is a useful refresher on speaking so the other person can follow you, which matters more when they're hurt and distracted. Every spoken promise should match a process the firm has set up. If the process isn't there, don't say the sentence.

### Ending Every Call With a Clear Next Step

The close is where unsupported promises usually sneak back in. A short routine, used on every call, keeps the last minute as clear as the first.

1.  Read the callback number back in groups of digits, and get a clear yes before you continue.
2.  Restate the key facts in one sentence: the caller's name, what happened, and the incident date and location.
3.  Explain the next step. The firm reviews the inquiry and decides whether it can help. Collecting intake is not case acceptance.
4.  Say plainly that the call does not establish representation.
5.  Attempt a transfer only if the firm's configured process allows it. Don't promise an available attorney or a callback time unless an owner and a timing have been agreed.
6.  Thank the caller and end the call.

#### Keep the close shorter than the story

A distressed caller who has already walked through the crash should get a calm summary, not a second intake. If they correct a fact, fix that one fact and stop. Don't reopen the whole account to "be thorough."

Full scripts and question templates belong in the separate practical guides. Use those when you're building the firm's question list. On the phone, you only need the six steps above.

Calls are recorded, transcribed, and graded so the team can review how each call was handled. In a demo, prospective customers can bring their current intake questions, try example calls with made-up case details, then review the transcript and report. That review is where you'll see whether the opening ran long, whether a question was asked twice, or whether the close promised a callback nobody owns.

Run three practice calls this week. Use a made-up crash, a crying caller, and a caller who asks "Do I have a case?" on the first breath. After each one, mark the four stages and note where the opening, the questions, or the close broke down. Fix the sentence that failed before you take the next live call.

* * *

Lighthouse Legal builds customizable AI voice agents that answer personal injury firms' calls, collect intake, and connect qualified callers with the team, including nights, weekends, and overflow. If you want that coverage to follow the same stages, boundaries, and next-step language you just read, bring your current questions and try a sample call. Visit [Lighthouse Legal](https://lighthouselegal.ai) to see how the agent would handle your line.

[Book a demo](https://www.lighthouselegal.ai/#book-demo) [See how it works](https://www.lighthouselegal.ai/#how-it-works)