Step 3: Account Owners – If You're Utilizing Ponds in Follow Up Boss
If your team uses Ponds in Follow Up Boss, the assigned Pond account must also have a RealScout seat, or your leads will not sync correctly.
What This Means
In Follow Up Boss, a Pond typically holds unassigned leads, allows agents to claim them, and is managed by an ISA or team account that temporarily nurtures leads before reassignment.
When integrated with RealScout:
The assigned Pond user in FUB must also have a RealScout account
All Pond leads initially sync into that assigned RealScout seat
When reassigned in FUB, ownership moves in RealScout
Important: RealScout mirrors ownership from Follow Up Boss. If the Pond account does not exist in RealScout, the integration cannot assign leads properly.
Step 1: Confirm Your Pond Structure in FUB
Log into Follow Up Boss and go to Admin > Ponds
Identify which user is assigned to the Pond (ISA, support account, or shared team email)
Common examples: isa@yourteam.com, support@yourteam.com, or a "Team Leads" placeholder account
Step 2: Ensure the Pond User Has a RealScout Seat
The Pond account email must:
Exist in RealScout
Have an active seat on your RealScout team account
Match exactly with the email in Follow Up Boss
Without a RealScout seat, leads will not sync properly and ownership logic may fail.
Step 3: Understand Where Pond Leads Live
When a lead enters the Pond in FUB, it syncs to the assigned Pond user's RealScout account. This includes:
Listing Alerts
Home Value Alerts (if Auto Nurture is enabled)
Engagement tracking
Messaging activity
Step 4: Reassigning Leads from the Pond
Reassign the lead inside Follow Up Boss
The integration updates ownership in RealScout automatically
All prior activity, alerts, and engagement history transfer with the contact.
Best Practice: Always reassign in Follow Up Boss. Do not manually move contacts inside RealScout.
Seat Planning for Teams Using Ponds
Include seats for:
All licensed agents
ISAs assigned Pond ownership
Any shared team account that owns leads in FUB
Skipping the Pond seat causes leads to accumulate incorrectly and creates ownership mismatches.
Quick Reference
Scenario | What Must Happen |
ISA assigned to Pond | ISA must have RealScout seat |
Shared support email assigned | That email must have RealScout seat |
Lead reassigned in FUB | Ownership updates automatically in RealScout |
Alerts created under Pond user | They transfer when reassigned |
Best Practices
Keep Pond ownership consistent in FUB
Ensure the assigned Pond user has a RealScout seat
Always reassign leads in FUB, not in RealScout
Audit seat allocation before scaling
Confirm Auto Nurture settings are intentional for Pond accounts
Frequently Asked Questions
Do ISAs need RealScout seats?
Yes, if they are assigned as the Pond owner in Follow Up Boss.
What happens if I reassign a lead in FUB?
Ownership moves in RealScout automatically, along with alerts and RealScout history, to the active teammate in RealScout.
Should Pond leads have Auto Nurture enabled?
That depends on your team's workflow. If ISAs are qualifying leads first, you may want controlled alert behavior rather than immediate automation, using tag-based automation for templates over Auto Nurture's email campaign you can preview here.