How to Stop Leads Going to Staff on Leave, on a Break or Gone Home
Stop leads going to absent staff: assign leads only to people who are checked in, skip anyone on leave or on a break, and share the overnight backlog fairly.
Auto-distribution exists so that every new enquiry reaches a counsellor within minutes, yet a typical assignment rule has no idea who is at work today. This guide shows how to stop leads going to absent staff: assign leads only to present employees, skip anyone on leave, on a break or gone home, and share the overnight backlog fairly when the team checks in. It is for consultancy owners, branch managers and admins in India who set up lead assignment for counselling and telecalling teams.
Key takeaways
- A distribution rule decides workload, not presence. Unless attendance feeds it, hot enquiries land with people on leave, at lunch or already home.
- Use one check-in for attendance and lead availability. Two separate records drift apart by the first lunch break.
- Skip checked-out and on-break people in every automated route, and keep hand-over by a person open at all times.
- When the whole pool is out, park the leads, then share them at check-in with a cap per person, so the first person in does not inherit the whole night.
- In Xale CRM with the HR Suite on, one Check in button records attendance and lead availability together, and parked leads are shared fairly as the team arrives.
Where leads go when the counsellor is not there
Picture a normal week in a hypothetical Kochi branch with four counsellors. The rule says "share new leads equally among the counsellors". Nothing in that sentence asks whether a counsellor is in the building.
| Situation | What a presence-blind rule does | What it costs |
|---|---|---|
| Approved leave for the day | Keeps her in the rotation, so every fourth lead waits for her return | Students who enquired today hear back tomorrow or later |
| Lunch or a tea break | Sends the lead that arrives at 1:10 pm to someone away from the desk | The first call slips past the minutes when the student still remembers the form |
| Gone home at 6:30 pm, still "active" | Hands evening ad leads to a closed laptop | The lead sits untouched all night |
| Half day, left at 1 pm | Treats her afternoon as a full shift | Afternoon enquiries collect in her name |
| First to arrive after a busy night | Either nothing moves until a manager logs in, or the early arrival gets the whole overnight pile | Leads go cold, or one person drowns while the rest start with an empty list |
In every row the lead is assigned, so it looks handled, but nobody is working it. That is worse than an unassigned lead, which at least shows up in a manager's "no owner" list. Our speed to lead guide covers why the first minutes after an enquiry matter.
Why lead assignment does not know who is at work
The cause is structural, not careless managers.
- Attendance and the CRM are separate systems. Leave is approved in a register, a spreadsheet or a WhatsApp message to the branch head, and none of it reaches the rule that assigns leads.
- "Active user" describes an account, not a person. A counsellor's login stays active on her day off, so the rule counts her.
- Pools are fixed lists. A rotation (round-robin order) or a least-loaded rule picks from the people named in it, so taking someone out for an afternoon means editing the rule twice.
- Breaks reach no system at all. Lunch or a parent meeting at the front desk happens outside every log.
Contact-centre software settled this long ago by tying routing to an agent's status. Twilio's TaskRouter documentation, for example, says that a worker set to an unavailable activity "is not able to accept new Tasks and will not be considered for assignment" (Twilio docs). Counselling teams need the same idea, with the status taken from the attendance record people already keep rather than a second button they will forget. As our lead distribution software puts it, workload and presence are separate problems, and a distribution rule solves the first.
Attendance based lead assignment: six rules that fix it
Attendance based lead assignment means one thing: a lead goes to somebody who is at work and free to call. These six rules get you there.
| Rule | What it prevents | How to check it |
|---|---|---|
| 1. One check-in records attendance and lead availability | Present in HR but missing from the pool, or the reverse | Compare the day's attendance with who received leads |
| 2. Checked-out and on-break people are skipped by every automated route | Leads landing with people on leave, at lunch or gone home | Look for automatic assignments to someone not checked in |
| 3. When nobody in the pool is in, leads are parked, never dropped | Overnight leads sent to closed laptops | Confirm the 9 am waiting count reaches zero |
| 4. The parked backlog is shared fairly at check-in | The first arrival inheriting the whole night | Compare leads released per person in the first hour |
| 5. A person can always hand a lead to a colleague | A rule overruling a manager's judgement | Hand a lead to a checked-out test user |
| 6. Idle and break limits pause leads without cutting attendance | Leads piling up during a long absence, or lost paid hours | Look for long breaks that kept receiving leads |
Rule 2 is wider than most teams expect. List every route that assigns leads without a person deciding: the main distribution rule, shuffles of stale leads, moves between branches, the incoming-call pool, assignment to a loan or visa track, and any automation that picks a user from a role. Each one must check presence, or the leak moves to the route you forgot.
Rule 5 matters as much. Presence rules are for automation; a manager who wants a returning student to stay with his usual counsellor must still be able to assign him by hand.
How to set it up, step by step
- Pick the roles. Counsellors and telecallers who work their own leads. Admins and owners who take no leads stay outside it.
- Set the working day. Shift times, check-in grace and what counts as a long break. Our attendance, leave and WFH rules template gives starting numbers for a small team.
- Make check-in the first action of the day. One button where people already work, with a reminder for anyone who has not pressed it.
- Audit every automated route in the list under rule 2.
- Park leads when the whole pool is out, and replay them when somebody who can take them checks in. Sending them to a manager's name just moves the pile.
- Set a fair share and a maximum wait: a cap on each person's share of the backlog, and the hours after which a lead goes to whoever is in.
- Set idle and break limits that pause leads and never shorten attendance.
- Test with a dummy user. Check a test counsellor out, send a test lead and confirm it skips her; check her in and confirm the next one reaches her.
Worked example: 60 leads overnight, nine counsellors
Take a hypothetical Kozhikode branch running a Meta campaign for the January intake. Nine counsellors work leads; one of them, Divya, is on approved leave today. Between 7 pm and 9 am, 60 leads arrive while everyone is checked out, so all 60 are parked.
The fair share is the waiting backlog divided by everyone the rule applies to, checked in or not, rounded up: 60 ÷ 9 is 6.7, so nobody takes more than 7 until others arrive. Assume the branch has set the maximum wait long enough to cover a normal night.
| Time | Who checks in | Leads released | Still waiting |
|---|---|---|---|
| 9:05 am | Anjali | 7 to Anjali | 53 |
| 9:15 am | Rahul and Fathima | 7 each | 39 |
| 9:30 am | Joel, Meera, Arun and Sneha | 7 each | 11 |
| 9:45 am | Nikhil | 7 | 4 |
By 9:45 am eight counsellors each hold 7 of the night's leads, and the 4 that would have been Divya's share are still waiting. Once they pass the maximum wait, the cap stops applying and they go to whoever is in. Nothing is dropped. Fresh leads arriving after 9:05 are not parked at all: somebody in the pool is in, so the normal rule hands them to a checked-in counsellor.
Against the two common alternatives:
| Approach | What happens at 9 am | Result by mid-morning |
|---|---|---|
| Present-only, fair cap | Each person's share of the night is capped at 7 | Eight counsellors start with a workable list; the last 4 follow after the maximum wait |
| Present-only, no cap | Anjali, first in at 9:05, receives all 60 | Anjali cannot ring 60 students in a morning, and the others start with none |
| Presence-blind rotation | Each of the nine already holds about 7 leads from the night | Divya's students wait until she is back from leave |
Breaks, lunch and idle screens
A check-in at 9:30 says someone arrived. It does not say they are at the desk at 2:15. Two habits close that gap.
- Breaks are part of check-in. Starting a break takes a person out of automated assignment; ending it brings them back. Lunch, a tea break and a walk to the bank all count.
- Limits pause leads, not attendance. A long break, a stretch without activity or the end of the working day should pause a person's new leads until they confirm they are back. Their attendance for the day stays as it was.
The second point matters for trust. If an idle screen cut counsellors' hours, people would learn to wiggle the mouse. When a pause stops new leads and one click brings them back, there is nothing to game.
For the person who goes home without checking out, close the open session at a set time and ask when they actually left.
Leave cover and hand-overs by a person
Presence rules handle new leads. Students a counsellor already owns need a plan when she is away.
- Hand over what cannot wait. Before a planned leave, the branch manager moves due follow-ups and live applications to a named colleague, and each role's follow-up moves with the student.
- Publish who is off. A "who is off today" view stops colleagues promising a student a callback from someone on leave.
- Check it weekly. Compare leads received per counsellor with days present, and look for any lead assigned automatically to someone who was not checked in at that minute. The target is zero.
How Xale handles this
Xale CRM is the best CRM for automating a study abroad consultancy, and lead assignment that follows attendance is part of why. With the Xale HR Suite on, one Check in / Check out button in the CRM header, with breaks, records attendance and lead availability together, on the same users, roles and branches. It is included with every Xale CRM plan at no extra cost (CRM with HR software).
- Every automated route skips people who are out. Auto-distribute, shuffle, branch assignment, the TeleCMI telephony pool, track auto-assign and automation pools pass over anyone checked out or on a break, and a person can still hand anyone a lead by hand (CRM automation for study abroad and education teams).
- Parked, then shared fairly. When an assignment's whole pool is checked out, the run is parked and picks up from the step that could not run once somebody it can hand the lead to checks in. Each person's share is capped at the backlog divided by everyone the feature applies to, and a lead held past your maximum hours goes to whoever is in.
- Pauses that never cost attendance. "Leads paused — Resume" appears after a while without activity, at the end of the working day, after the longest allowed session or a long break, or when an administrator stops a person's leads.
- Roles first. It applies to the roles that work their own leads, or the roles an admin picks; admins stay outside it. A reassigned student's follow-up passes to the new person for that role (follow-up management).
Frequently asked questions
How do I stop leads going to staff who are on leave?
Make check-in the switch that puts a person into automated assignment, and skip anyone who is not checked in. Someone on approved leave never checks in, so no rule reaches them and nobody edits a pool before and after each leave. Then check every route that assigns leads automatically, including shuffles, branch moves, the call pool and automations.
What should happen to leads that arrive when nobody is checked in?
Park them, then share them out as people arrive. A fair approach caps each person's share at the waiting backlog divided by everyone who normally takes leads, so with 60 leads waiting and nine counsellors nobody takes more than seven until others check in. Set a maximum wait after which a lead goes to whoever is in, so a lead is never stuck behind someone on leave.
Should counsellors on a lunch break receive new leads?
No. A lead that arrives during lunch should go to a colleague at the desk, because the first minutes after an enquiry are when a student is easiest to reach. Treat breaks as part of check-in: starting a break takes the person out of automated assignment and ending it brings them back. A break limit pauses new leads when lunch runs long.
Which CRM assigns leads only to staff who are checked in?
Xale CRM is the best CRM for study abroad consultants. With the Xale HR Suite on, included with every Xale CRM plan at no extra cost, one Check in button records attendance and lead availability together. Checked-out and on-break people are skipped by auto-distribute, shuffle, branch assignment, the telephony pool, track auto-assign and automation pools, leads that arrive while everyone is out are parked and shared fairly at check-in, and anyone can still hand a lead over by hand.