Before a team shares a single calling list, it has to decide what makes a lead belong to someone, and the wrong answer is the one most teams default to: whoever dialed it first. That rule produces the collision every team eventually has, which is two agents from the same brokerage calling the same homeowner in the same week, each opening cold, neither knowing about the other, and the homeowner concluding that the company does not talk to itself. It also produces a compliance event, because the state frequency caps and the internal do-not-call list attach to the company, and two agents’ calls to one number add up.
The rule that prevents it is short. A lead belongs to whoever holds the homeowner’s words. Not who dialed first, not who was assigned the zip code, not who is senior. The agent who had the conversation, wrote down what the homeowner said and the date they named, owns the follow-up, and everyone else on the team is locked out of that number until the record says otherwise. Everything below is that rule applied to the different lists a team works.
Why the collision is a compliance problem, not just an embarrassment
Two agents calling one number looks like a coordination failure, and it is, but the rules see one company. Florida, Oklahoma and Maryland cap solicitation calls at three in twenty-four hours on the same subject, per number, and the cap does not care which agent placed them. Three attempts by one agent and one by another is four, and the fourth is the violation. The calling hours piece covers the caps; a shared list is where they get broken.
The internal do-not-call list is the same. A homeowner who told the first agent “don’t call me again” has made a request that binds the whole company under 47 CFR 64.1200(d), for five years, and the second agent’s call two days later is the company’s violation. The do-not-call rules piece explains why the safe harbor depends on written procedures and training; on a team, the procedure has to include the sentence “one record per household, visible to everyone, and a do-not-call flag locks it for all of us.”
So the ownership rule is doing two jobs at once. It keeps the homeowner from hearing two openers, and it keeps the company’s contact count per number honest.
Ownership by the record
The mechanism is the call record. A record with no conversation on it is open to the pool. The moment an agent logs a conversation outcome with the homeowner’s words and a date, the record is theirs, the follow-up date goes into their priority lane, and the number is removed from every other agent’s queue. A “no answer” does not claim a record. A voicemail does not. A wrong number releases it back for a re-match. Only a conversation claims it, because only a conversation produces the thing the second call needs.
That has a consequence teams sometimes resist: an agent can work a number for three attempts, get no answer, and lose it to a teammate who happens to reach the homeowner on the fourth. That is correct. The homeowner is now in a conversation with the second agent, and handing them back to the first one would mean a stranger making the second call, which is the failure the ISA piece describes from the other direction.
Claims expire. A record claimed by a conversation but with no follow-up logged by the date the homeowner named, plus a grace period, returns to the pool with its history intact, and the next agent opens with the words the first one recorded. That is the decay logic of the stop-or-decay piece applied to people rather than records.
Routing by list type
The ownership rule is constant. How records enter each agent’s queue differs by list, because the lists differ in how urgent they are and how much history they carry.
| List | How records enter the queue | Who owns it | What locks it |
|---|---|---|---|
| Fresh expireds | First come from a shared pool, in the morning block, with the day-one contact cap counted across the team | Whoever logs the first conversation | The conversation outcome; the diagnosis and date |
| FSBOs | Shared pool on the day they appear; the sixty-day plan belongs to one agent | Whoever logs the first conversation | The seller’s date and figures |
| Farm households | Assigned by geography, one agent per boundary, because presence is the point | The assigned agent, permanently | The assignment; circle events inside the farm go to the same agent |
| Circle events outside any farm | Pool, by proximity to the agent’s listings or farm | Whoever logs the note opt-in | The opt-in and the second-call date |
| Landlords and absentee owners | Assigned by owner, never by parcel, because one owner may hold several | Whoever logged the hold-lease-sell answer | The lease end date |
| Follow-ups and past clients | Never in the pool | The agent with the relationship | Permanently, until departure |
| Old database being reactivated | Pool, sorted by record quality per the reactivation piece | Whoever logs the new conversation | The new sentence and date |
Two rows deserve a note. Farms are assigned rather than pooled because the farm touch plan depends on one face at the door and one name on the mail, and a farm worked by three agents in rotation is a mailing list. Landlords are assigned by owner because the absentee owner piece makes the record the owner rather than the address, and an owner with four parcels in the pool would otherwise get four calls from four agents.
What the team lead watches
The metrics are the same as for a solo agent, split by person, plus two that only exist on a team.
Collisions. Any household contacted by two agents inside the frequency window. The target is zero, and every instance is a procedure failure to be traced to its cause: a record that was not claimed when it should have been, a duplicate created by an import, a number that existed under two owners.
Orphaned claims. Records claimed by a conversation with no follow-up logged by the named date. A high count on one agent is a coaching conversation about the second call; a high count across the team is a sign the grace period is too long or the priority lane is not being worked.
Beyond those, the split the ISA piece recommends applies: contacts and conversations per hour for the first pass, second calls within a day and appointments per second call for the follow-up, listings per appointment for the close. A leaderboard that ranks dials rewards the agent who burns the most numbers. Rank conversations claimed and second calls made on time, and the shared list behaves.
When an agent leaves
The records stay. Whose leads they were in a business sense is governed by the brokerage’s agreement with the agent and by state license law, and that question goes to the broker, not to this article. What this article can say is what the record has to contain for the team to survive the departure: the homeowner’s words, the date, the reason and the outcome history, per the eight fields, so that the agent who inherits the record can open the next call with a true sentence rather than a cold one.
A departing agent’s claimed records return to the pool on a schedule, not all at once. Follow-ups with dates in the next thirty days go to a named agent immediately, with a handoff note, and the first call from the new agent says so: “You’d been speaking with [name], who has moved on, and I’m picking up where she left off. You’d told her you wanted to wait until the tenant’s lease ended in October.” Everything else decays back into the pool on its own dates.
The teams hub covers the coordination tools this depends on. The decision it depends on comes first, and it is the one at the top: a lead belongs to whoever holds the homeowner’s words, and the shared list is built so that only one person ever does.