Funeral Home First-Call Intake: A Practical Checklist

Start with a clear, unhurried opening

For an owner or managing director, the first-call script is an operating agreement: what your answering team may say, what it needs to learn, and when your staff takes over. It is not a substitute for a licensed professional or a complete arrangement form. Start by choosing one coverage window and reviewing the language with the director responsible for that window.

Identify the funeral home and, when an AI assistant answers, make that role clear. Give the caller space to explain why they are calling. A brief acknowledgment is more useful than a long speech. Avoid cheerful sales language, assumptions about family relationships, or claims to understand exactly how someone feels.

An illustrative opening is: “Thank you for calling [funeral home]. I’m the AI assistant helping the team answer calls. How may I help you?” If the caller reports a loss: “I’m sorry for your loss. I can help reach the director on call.” These are review prompts, not a universal script or a promise that a director is immediately available.

Collect the minimum useful handoff

When a callback is needed and the caller is willing, confirm their name, callback number, and reason for reaching the team. Read the number back. If a facility is calling, capture the facility name and the staff contact needed for the director to return the call. Let the caller correct any detail without restarting the conversation.

Only ask further questions when the director has approved them and they are necessary for the immediate handoff. A family should not have to provide a complete history before speaking to someone. Do not use a general answering flow to collect Social Security numbers, payment-card details, or signed authorizations. Keep sensitive information out of marketing analytics.

• ✓ Caller’s preferred name and callback number, when a callback is requested.
• ✓ Reason for the call, recorded without speculation.
• ✓ Relevant facility or location only when needed for the handoff.
• ✓ Named staff owner or approved on-call destination.
• ✓ The next step explained to the caller and its actual status.

Use different paths for different calls

A first call about a loss, a question about tomorrow’s service, an existing family asking for a director, and a person exploring advance planning are different requests. Give each a named destination and a clear rule for when to interrupt the on-call person. Do not classify every inquiry as a new arrangement opportunity.

Public directions or service times can come from current, approved information. A request for a director should reach the approved contact path. Advance-planning conversations can be offered an appropriate staff appointment when requested; they should not trigger unsolicited follow-up merely because a number was captured.

If the caller describes an immediate medical or safety emergency, use the organization’s approved emergency response language and appropriate emergency services. The answering assistant must not give medical instructions, decide whether death has occurred, authorize transport, or promise when a removal team will arrive.

Do not turn a price question into an intake gate

FTC guidance says callers can request accurate price information without providing identifying details or visiting in person. Use the current approved price lists; refer questions that need a director rather than inventing answers. The guidance distinguishes ordinary after-hours calls from at-need calls when the provider normally makes arrangements after hours. Review that distinction, along with applicable state rules, before setting your workflow.

Close the loop, not just the conversation

A transfer attempt is not a completed handoff. Decide what happens when the first number rings unanswered, reaches voicemail, or is out of service. The approved fallback might be a backup director or a staff callback queue. Tell the caller what actually happened; never announce that someone is on the way or will call within a specific time unless that commitment is authorized and supportable.

The handoff record should distinguish “transfer attempted,” “staff answered,” and “callback acknowledged.” Keep the original callback owner visible until responsibility is explicitly accepted. A summary delivered to a device does not prove the director has read it.

Before launch, have staff test an interrupted caller, an unclear callback number, an unanswered transfer, a routine service question, a price inquiry, and a caller who requests a human immediately. Use fictional details for testing. Review whether each caller reaches an honest next step, then record the director’s approval and the script version.

• ✓ Can the caller ask for a person without arguing with the assistant?
• ✓ Does an unanswered transfer reach the approved fallback?
• ✓ Are price questions handled without forcing contact capture?
• ✓ Can a director see what was attempted and what remains open?
• ✓ Is there a documented owner for corrections and script changes?