Every new inquiry on a team should have one named owner, one dated next action and a written fallback for when that owner is away. Set this up first with the assignment, task and stage tools in the CRM you already use. Automation is only worth examining if a specific gap keeps recurring once the routine is in place.
How inquiries can slip on a team
On a team, an inquiry can slip even when everyone is trying. Several people can see it, and each may assume someone else has it. Round-robin might assign it to an agent who is out at showings all afternoon. A shared inbox might show it to five people at once.
The inquiry is your demand. Your agents' time and attention is your capacity. Clear ownership links the two.
Start with what your CRM already does
If your team uses Follow Up Boss, its Action Plans can create tasks, change stages, add notes, collaborators and tags, and send drip emails. Plans can start automatically for new leads from the Lead Flow page, so that is where to see which plan each new lead gets.
Pausing a plan when someone responds is an optional setting. When it is switched on, these pause the plan:
- email or text replies from the lead, or from a relationship on their record
- calls longer than 2.5 minutes, logged through Follow Up Boss's calling feature or mobile app
Shorter calls don't count, and calls logged manually on desktop need a manual pause. (Product check: November 1, 2026.)
That has three practical consequences:
- Don't assume a plan stops itself after a conversation. Make “check the plan” part of the owner's next action.
- Don't assume reassignment happens on its own. If you want an inquiry reassigned automatically when nobody acts in time, ask your admin or Follow Up Boss support whether your setup offers that. This guide doesn't assume it does.
- This guide uses plans for internal tasks only. Whether any automated message reaches a consumer, and how opt-outs are handled, is a decision for your broker or compliance lead, under the contact permissions that apply to that channel and location.
Using a different CRM? Look for the same four things: assignment, tasks with due dates, stages, and a record of who changed what.
Four rules for the team
- One owner. Collaborators can help, but only one name sits on the next action.
- A dated next action. “Follow up” is not a next action. “Call back Tuesday 10am” is.
- A fallback. If no next action is logged within your agreed window, a named person reassigns the inquiry and notes why.
- Written exceptions. Reassignments, requests for a specific agent and manually paused plans each get a one-line note.
A copyable ownership check
These columns are our suggestion for a weekly review, not fields in any CRM. Keep the person's details in the CRM itself; the review only needs a reference.
| Column | What to record |
|---|---|
| CRM reference | Record link or ID, not the person's details |
| Source | Website form, portal, sign call, referral |
| Owner | One name |
| Assigned at | Date and time |
| Next action and due | A specific action at a specific time |
| Fallback owner | Who reassigns if the window passes |
| Plan checked | Yes or no, after each conversation |
| Exception note | Reassigned, agent requested, paused or closed |
Synthetic example, not a customer result
A six-agent team sets its own rule: a new inquiry needs a logged next action within four office hours, and office hours are 9am to 6pm, Monday to Saturday. That rule is this team's choice for the example, not a recommended standard.
- A website inquiry arrives Friday at 4pm. Round-robin assigns it to Jordan, who is off on Saturday. Under the team's rule, a next action is due by 11am Saturday.
- At 11am Saturday, no next action has been logged. The operations coordinator, who is the named fallback, reassigns the inquiry to Sam, the on-duty agent, with the note “Jordan off until Monday.”
- Sam calls the number given on the form, within the contact rules the broker has set for the team, and logs the call manually from a desk phone. A manually logged call doesn't pause the plan, so Sam pauses it and sets the next action: “Send showing times Monday 9am.”
- On the call, the person asks to work with Jordan. Sam records that request.
- On Monday, the coordinator moves ownership back to Jordan with every note intact.
Team lead or brokerage operations?
Where a team lead runs their own agents, the response window and the fallback may sit with them. At brokerage level, an operations director also needs to settle three things:
- who has permission to reassign inquiries across teams
- who can see which records
- what happens to open inquiries when an agent leaves
Write those down before changing any routing settings.
What this routine does not decide
It records who owns an inquiry and when the next step happens. Everything else stays with the licensed agent and broker: what the agent advises, where a buyer looks, how a property is valued, anything about negotiation or contracts, and what messages go to consumers.
When automation is worth a look
Run the routine for a few weeks. Then read the exception notes. If the same handoff keeps failing in the same way, and neither your CRM settings nor vendor support can close it, that specific gap is worth examining. A one-off miss still deserves a look at what went wrong, but on its own it doesn't point to a missing tool.
Next step
This week, open your ten most recent inquiries in your CRM, without exporting them anywhere, and answer three questions:
- Was there one owner?
- Was there a dated next action?
- What happened when the owner was unavailable?
If one gap keeps repeating after you've checked your assignment and plan settings, Abundance Applied is happy to talk it through. We only need a description of the process, not client records.
Sources
Product documentation checked 1 November 2026. Features depend on the current plan, permissions and setup.