ISA vs automation
The BrokerFold Team — Product + Engineering
Last reviewed
An ISA is a person you pay to call, qualify and book your leads; automation is software doing the mechanical share of that job for a fraction of the cost. For a team, the real question is rarely either/or — it’s sequencing. Human calling priced at salary levels only pays for itself once the cheap layers underneath it exist: capture without leaks, routing that resolves in seconds, and automated follow-up covering every lead. Hire before that foundation and you’re paying professional wages to compensate for missing plumbing.
What the money actually buys
The cost gap is roughly an order of magnitude — in-house hires at real-salary levels, virtual services in the hundreds-to-thousands monthly, software in the tens — and we keep a surveyed, dated cost table on the dedicated ISA services vs automation page rather than repeating numbers here. The structural point matters more for teams: a human sells you capacity, which you must keep fed to justify, while automation sells you coverage, which costs the same whether the month brings forty leads or four hundred. Teams with spiky volume — which is most Canadian teams, given how seasonal our markets run — feel that difference hardest, because the ISA’s slow February costs exactly what their frantic May does.
An ISA can’t fix broken routing
Here is the team-specific trap the generic comparison misses. Teams often hire an ISA to solve what is actually a distribution problem: leads sit untouched, so someone proposes paying a person to touch them. But if your routing rules are unwritten, an ISA becomes a human router with a salary — triaging inbox chaos, deciding by feel who gets what, and creating a single point of failure who takes vacations. Fix distribution first, in software, where it costs nothing per decision. The honest test: if every lead already reaches an owned seat in under a minute and still isn’t getting called, you have a calling problem, and a caller is a rational purchase. If leads are reaching the wrong seats, or no seat at all, you have a fifty-dollar problem wearing a fifty-thousand-dollar costume.
When the human genuinely wins
Automation cannot run a live qualification call, and pretending otherwise is how teams end up with pipelines full of politely nurtured strangers. A skilled ISA converts the ambivalent: the seller “just wondering” about value, the buyer spooked by rates, the lead who answers questions on the phone they’d never type into a chat box. If your team buys expensive leads in volume, minutes of human voice on each one is defensible math. The discipline is aiming that expensive attention only at demonstrated intent — re-engaged contacts, alert clickers, valuation requesters — which your system should surface, and measuring the ISA on appointments held rather than activity.
The order of operations for a Canadian team
Run the sequence: first, capture and routing in one system, so no lead waits on a human decision. Second, automated coverage — instant response plus nurture sequences that respect CASL consent from the moment of capture, since a caller working non-consented lists inherits Canada’s telemarketing rules along with the dial tone. Third, protected calling time from your existing agents aimed at the intent layer, which is where team follow-up either happens or doesn’t. Only then price a hire, against the volume that remains. BrokerFold’s contribution is steps one and two as a single product — capture, routing, nurture and the behaviour timeline inside one team CRM — so the hire, if you make it, starts on plumbing that already works.
Frequently asked questions
Can an ISA and automation share the same leads?
They should — sequentially, not simultaneously. Automation answers first and keeps the long-arc touches running; the ISA calls the slice showing intent. What fails is parallel operation without a system of record, where a lead gets an automated text and an ISA call that contradict each other within the hour.
Who should an ISA report into on a team?
Whoever owns pipeline numbers — usually the team lead or ops manager — with appointments held as the primary metric, not dials. An ISA measured on dial volume will produce dials. Give them explicit routing authority too: an ISA who qualifies a lead needs a defined, instant path to hand it to the right agent.
Is an ISA worth it before a team has a CRM?
No. An ISA without a shared system works out of a personal spreadsheet, and every conversation they have is invisible to the agents who inherit the lead. The CRM is the cheaper purchase and the prerequisite — it is where the ISA's work becomes the team's asset instead of their private notebook.
Keep reading
- ISA services vs automation The honest cost table — $55k+ in-house, $720–2,000/mo virtual, $2–6k/mo outsourced vs software — and the cases where a human caller genuinely wins.
- Team lead follow up Why shared leads die faster than solo leads, the single-ownership rule that fixes it, and the automation layer a Canadian team should run under CASL.
- Real estate lead routing rules The routing criteria that hold up on Canadian teams, the ones that cause fights, and a starter rule set a five-agent team can write down this week.
- Real estate CRM Canada What a real estate CRM has to handle in Canada: CASL consent, instant lead response, and behaviour from your own website. How BrokerFold CRM covers all three.