Is Your Follow Up Boss Admin Tab Actually Working for You? Groups, Teams, and Ponds

A lead comes in. It sits for six hours because nobody knew it was theirs to claim. Or worse, three agents call the same person on the same afternoon, and the lead unsubscribes before anyone books an appointment.

If that sounds familiar, the problem is rarely the lead source. It is almost always lead routing, and inside Follow Up Boss, lead routing lives in three places most teams never fully configure: Groups, Teams, and Ponds.

This is the second part of our walkthrough of the Follow Up Boss admin tab. The first one covers the Overview and Lead Flow settings, the two screens that decide where a lead goes the moment it hits your system. This post picks up where that one left off.

Why This Matters More Than It Looks

Follow Up Boss gives every team the same three tools. Almost none of them use all three the same way, because almost none of them have stopped to ask which one solves which problem. Groups distribute. Teams organize. Ponds store and share. Confuse the three and you end up with a CRM that is technically set up and still is not being used the way it should.

That gap between "we have the CRM" and "the CRM actually runs the business" is the whole reason an operating system matters more than a tool.

Groups: How Leads Actually Get Distributed

A Group in Follow Up Boss is a bucket of agents who share a lead source. Buyer agents in one group. Listing agents in another. Lenders kept separate from both.

Groups solve one problem: when a lead comes in, who gets it first, and what happens if that person does not respond?

Two distribution styles do the work:

• Round robin. The lead rotates through every agent in the group in order, so everyone gets an equal share regardless of how fast they respond.
• First to claim. Every agent in the group is notified at once, and whoever claims the lead first works it. This rewards speed to lead, which is the single biggest predictor of conversion in real estate.

First to claim comes with a timer, one to thirty minutes, after which the lead reassigns automatically. Teams that are serious about speed to lead usually set this short and route unclaimed leads to a dedicated response team rather than letting them sit.

If you are a solo agent, Groups are not something to worry about. Every lead is already yours. This setting exists for the moment your business stops being one person, which is exactly the moment most operator-founders lose visibility into who is actually working what.

Teams: The Setting Everyone Skips, and Why It Breaks Reporting

The Teams tab is where every person on the account lives, tagged as an admin, an agent, or a lender. Admin access opens the lead flow, lead sources, and stage configuration. Agent access is scoped to what that person needs to do their job. Lender access is separate again.

Larger brokerages use Teams to split people into offices or markets. For most operator-founder teams, the real value of this tab is not the org chart. It is one setting almost nobody checks: whether each agent's email and calendar are actually connected.

An unconnected email shows up as an orange flag next to that agent's name. If it is not fixed, every email that agent sends lives outside Follow Up Boss entirely. No record. No timeline. No way for you, a manager, or an AI reviewing activity to confirm the follow-up actually happened.

This is the gap between having a CRM and having a system of record. A team can be fully "set up" in Follow Up Boss and still be operating blind, because the one connection that makes activity visible was never turned on.

The fix takes under a minute per agent.

Go to My Settings, scroll down, and toggle both Share My Email and Share My Calendar. Have every agent on the team do the same. It is worth pausing here and checking your own account before reading further.

Ponds: The Most Underused Tool on the Admin Tab

A Pond is a shared list with restricted access. Think of it as a folder that only certain people can open. A Pond for stale leads worth revisiting. A Pond for vendors. A Pond for listings waiting on a specific milestone.

Ponds matter most for teams with an ISA or an admin function, because they let a group of people work one shared list without opening it to the whole team. An ISA pond, a VIP-lead pond for anything unclaimed after thirty days, a vendor pond shared with three people and nobody else. Mass-update a batch of contacts into the Pond and only the assigned agents can see or touch them.

One detail catches almost every team off guard: every Pond requires a Pond Lead, and any automated email or text sent from that Pond goes out under that person's name, not the agent working the contact. Some teams solve this by creating a generic address, something like admin@yourcompany.com, so outreach from a shared list reads as coming from the company rather than one specific person, with someone on the operations side monitoring replies.

Solo agents generally will not need Ponds. Follow Up Boss will not even let you save one without an assigned lead, which is its own signal that this tool is built for teams, not individuals.

The One Filter to Run Every Setting Through

Groups, Teams, and Ponds can all be configured a dozen different ways, and that is exactly where teams get into trouble. More options is not the same as more leverage.

Before turning any of this on, run it through one question: does this make the business run, or does it just add a setting nobody remembers why they built?

If a configuration is not going to change how a lead gets worked or how clearly you can see what is happening in the pipeline, it is not worth the complexity. The best Follow Up Boss setups are simple enough that a new hire could understand the routing logic in five minutes. If yours is not, that is not a technology problem. It is an operating system problem.

Where This Fits Into the Bigger Picture

Groups, Teams, and Ponds are configured. They tell Follow Up Boss where a lead goes. They do not tell your team what to do once it arrives, how fast a response is expected, or who is accountable when a lead sits untouched. That layer, the operating rhythm sitting on top of the CRM, is what actually determines whether the system gets used.

If you want a clear read on where your own account stands today, from lead routing to email connection to Pond structure, that is exactly what a system audit is built to show you.