Copy this missed-call rule first
This rule should be specific enough that an assistant, answering service, or AI receptionist can follow it without deciding who deserves attention. It also needs a backup so a call does not remain assigned to someone who is unavailable.
After every missed call, [person or system] posts a summary in [one handoff destination]. The summary includes the caller’s name, callback number, reason for calling, property or area, requested next step, timing stated by the caller, and preferred language. [Primary owner] calls back by [deadline]. Calls that match [priority conditions] go to [priority owner] and must be called back by [priority deadline]. If the call is not marked Called or Attempted by its deadline, [backup owner] takes responsibility for the callback. The person who calls updates the status in [tracking location].
- Primary callback owner: [name or role]
- Backup callback owner: [name or role]
- Immediate summary destination: [channel, inbox, or queue]
- Long-term contact record: [CRM or other system]
- Normal callback deadline: [your chosen target]
- Priority callback deadline: [your chosen target]
- After-hours rule: [owner and deadline]
- Statuses the team will use: [New, Claimed, Attempted, Called, Scheduled, Closed]
Our users learned that a tag is part of the rule. A team's missed-call summaries post to its calls channel in Slack, and the agent asked Reddy to tag two teammates on every post there, including every missed-call summary. The two were not members of that channel, so Reddy added them to it, because a tag does not reach a person who is not in the channel. The tags started with the next call.
Write the caller questions
Keep the opening questions short. Ask the core questions first, then use a buyer, seller, or existing-client branch. The person returning the call can gather anything that is not needed for routing.
Thanks for calling [agent or team name]. [Agent name] is unavailable, but I can take a few details and make sure the right person follows up. May I have your name and callback number? What are you calling about? Is there a particular property or area involved? What would you like the agent to help you do next? Is there a time you need a response by? Which language would you prefer for the callback?
Add only the branch questions that affect ownership or the next action.
- Buyer or renter: Which property or area interests you? Are you asking a question or requesting a showing? Are you already working with an agent? What is your approximate timeline? If relevant to your process, what budget range and financing or pre-approval status should the agent know?
- Potential seller: What is the property address and type? What would you like help with? What is your tentative selling timeline? Is there anything about the property’s condition the agent should know before calling?
- Existing client: Which property or transaction is this about? What happened? Who is waiting for an answer? Did the caller mention an appointment, decision, or deadline?
- Agent, lender, title contact, or vendor: Which transaction or property is involved? What information or action is requested? Who should receive the response?
- General inquiry: What is the question? Is the caller asking for a conversation, information, or an appointment?
Assign every call type to an owner and a deadline
The table below is a hypothetical example for a small team with an agent and an assistant. Its times are operating choices, not industry requirements. Replace them with targets your team can consistently follow.
| Call type | Primary owner | Summary goes to | Callback due | Backup rule |
|---|---|---|---|---|
| Specific listing or showing request | On-duty buyer agent | Calls channel; contact added to CRM | Within 10 minutes during coverage hours | Assistant assigns the backup agent if no attempt is recorded by the deadline |
| Potential seller asking for a consultation | Listing agent | Calls channel; contact added to CRM | Within 30 minutes during coverage hours | Assistant sends it to the team lead if no attempt is recorded |
| Existing client with a same-day issue | Assigned agent | Transaction channel or designated client queue | Within 10 minutes | Assistant calls the assigned backup or team lead |
| General market or service inquiry | Assistant or on-duty agent | Calls channel | By the team’s chosen daily cutoff | Move it to the next coverage block if the owner is unavailable |
| Vendor or solicitor | Assistant | General call log | During the next review block, if a response is needed | No escalation unless the call concerns an active transaction |
| After-hours call | After-hours owner | Calls channel | By the after-hours target or next business opening, according to the call type | Named weekend or next-morning backup takes ownership |
For a solo business, the agent may be both the primary and backup. The backup rule can instead change the alert method: for example, an assistant calls the agent, or an unclaimed item moves to a separate priority queue.
Do not use vague labels such as urgent unless the rule defines them. Write the conditions your team can recognize, such as an existing client reporting a same-day issue, a caller requesting a showing today, or another transaction participant waiting for an answer.
Compare answering options with the same test
Keep the script and routing table independent from the tool. That lets you test a human answering service, an AI receptionist, and your current voicemail process against the same requirements.
| Setup | What to test | What the handoff rule must specify |
|---|---|---|
| Keep the current voicemail process | Leave test messages for a buyer inquiry, seller inquiry, and existing-client issue. Check whether the messages provide enough information to route the calls. | Who checks messages, how often they check, where they copy the summary, who calls back, and when the backup takes over |
| Human answering service | Give the service your exact script. Make test calls with incomplete answers, a caller who changes topics, and a caller who prefers Spanish. | Which questions the service asks, what it may say, where it sends summaries, and which conditions trigger a transfer or alert |
| AI receptionist | Call it yourself and test each branch. Ask about a specific listing, decline to answer one question, change languages, and request a person. | Which information it may use, which answers it must leave for the agent, how it routes calls, and where its summaries appear |
Dialnote’s guide describes an AI receptionist setup that asks qualifying questions, routes calls under configured rules, and sends written summaries. Treat each item as a feature to verify in the particular service you are considering, along with its transfer, language, CRM, and notification behavior.
On an agent’s Reddy line, every call rings the agent’s phone first and Reddy answers the calls the agent misses. Reddy asks the agent’s own questions after its intake, keeps a call record, and posts the call to the Slack channel the agent picked; it does not quote prices, commissions, or availability.
Run three calls before putting the rule into use
Test the workflow from the caller’s first word through the completed callback. Use a different person to place each call if possible, and do not tell the answerer which branch is coming.
- Place a buyer call about a specific property and request a showing. Confirm that the summary contains the property, requested action, contact details, owner, and callback deadline.
- Place a seller call without giving every requested detail. Confirm that the answerer records what was said without inventing missing information.
- Place an existing-client call that mentions a same-day concern. Confirm that the correct owner and backup receive it in the designated handoff location.
For each test, follow the item until someone marks it Attempted or Called. If the first owner does nothing, let the deadline pass and confirm that the backup rule activates as written.
- The caller was asked only approved questions.
- The summary separated the caller’s statements from verified information.
- The call type produced one clear owner.
- The summary appeared in the designated handoff queue.
- The callback deadline was visible.
- The backup knew when to take over.
- The person making the callback updated the status.
- Any CRM entry matched the handoff summary.
Once the three tests pass, save the caller script, routing table, and backup rule together. Review them whenever team roles, coverage hours, lead sources, or communication tools change.
