Agent accountability KPIs
The BrokerFold Team — Product + Engineering
Last reviewed
Accountability KPIs are the small set of numbers that tell a team lead whether leads are being worked, without requiring anyone to hover. They exist because lead distribution is a contract: the team spends money and brand to generate the lead, the agent receiving it owes a measurable standard of effort in return. Teams that skip the measurement half of that contract end up arguing from anecdote — and routing by whoever complains loudest — while the leads themselves die politely off-camera.
The five that matter
Speed to lead — median minutes from lead arrival to first human response, the number with the steepest documented decay curve. Claim-to-contact — on claim-based teams, the gap between grabbing a lead and actually attempting contact; it separates hustle from hoarding, as covered on first to claim leads. Contact rate — the share of assigned leads reached in conversation within the first week; it exposes both weak effort and weak lead sources, and you need to know which. Follow-up coverage — the share of open leads with a next touch actually scheduled; the leads with nothing scheduled are your churn in advance. Appointments held — not booked, held; the KPI closest to money that an agent still directly controls.
The metrics that mislead
Dial counts reward theatre: forty calls to voicemail beats four real conversations on that scoreboard, and agents optimize what you post. Raw conversion rate, read at agent level on team-sized samples, is mostly noise wearing a percentage sign — a dozen leads decided by one luxury close. Pipeline value predicts optimism, not income. And any metric measured but never discussed decays into wallpaper within a month. The test for keeping a number on the board: an agent can move it this week by behaving better, and you’re prepared to act on it. Five numbers that pass that test beat fifteen that impress a spreadsheet, because agents can hold five in their heads on a Tuesday afternoon, and the whole point is that they do.
Reviewing without micromanaging
The ritual that works is short, scheduled and symmetrical. Same five numbers for every agent, visible to every agent, reviewed together weekly — then the consequences run through systems rather than speeches: follow-up coverage feeds the routing rules as an eligibility condition, so falling behind pauses an agent’s spot in the rotation automatically and catching up restores it. That keeps the team lead out of the referee role. The symmetry matters too: the same review that holds agents to response times should hold the team lead to lead quality, because agents stop trusting KPIs the moment the numbers only ever point downhill. Publish the source’s contact rate next to the agent’s, and half the defensiveness leaves the room — sometimes the number is telling you to fire a lead vendor, not to coach an agent.
The data has to collect itself
None of this survives manual logging — an agent who just finished a hard call will not also journal it accurately, and a KPI built on self-report measures diligence at paperwork. The numbers above fall out as a by-product only when capture, routing, messaging and follow-up happen inside one system. That is how BrokerFold’s team CRM produces them: assignment and claim events are stamped when they happen, email rides Gmail sync onto the contact record, and each contact carries a behaviour timeline of what they viewed and when — so Monday’s meeting starts from the record, and the coaching conversation can be about what to do next instead of what really happened.
Frequently asked questions
How often should a team review these KPIs?
Weekly, briefly, and in the open. A fifteen-minute Monday review of last week's response times, contact rates and appointments keeps the numbers ambient instead of punitive. Monthly reviews arrive too late to change behaviour, and daily scrutiny reads as surveillance and poisons the room.
Should KPIs decide who gets leads?
Yes — that is the fairest use of them. Tying lead eligibility to measured follow-up converts accountability from a lecture into an incentive: work your leads, stay in the rotation. The alternative is distributing by seniority or feel, which punishes your most disciplined agents invisibly.
What's a reasonable speed-to-lead target for a team?
An automated response within a minute and a human response within minutes during working hours, with an honest promised window after hours. The precise threshold matters less than the trend line — a team whose median first response drifts from 4 minutes to 40 has a problem no target number fixes.
Keep reading
- 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.
- 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.
- First to claim leads How claim-based lead distribution works, why it wins on response time, the ways agents game it, and the guardrails that keep a claim system fair.
- What is speed to lead? Speed to lead is the time from inquiry to your first response. Research puts a 5-minute response at roughly 21x the qualification odds of a 30-minute one.