Follow-ups for Counselling Teams: A Role-Based Playbook
Follow-ups for counselling teams break when four roles share one student. Fix it with role-based follow-ups, stage policies and calendar-day Overdue/Today.
Most problems with follow-ups for counselling teams are not discipline problems. They are data-model problems. When a telecaller, a counsellor, an application officer and a visa officer all work the same student, a single "next follow-up date" on the lead cannot hold four people's promises. Someone overwrites someone else's date, a due call slips off every list, and the manager's overdue count stops meaning anything.
This guide covers the fix: each role owns its own follow-up, every stage has a written follow-up policy, and Overdue, Today and Later are counted in local calendar days. It is written for counsellors, team leads and consultancy owners in India, and it works whether you use a CRM, a spreadsheet or a whiteboard.
Key takeaways
- One follow-up date per lead fails once more than one role works the student. Give each role its own follow-up per lead, and per university application.
- For every stage, decide whether a follow-up is needed and how many days after entry it is due.
- Count Overdue, Today and Later in IST calendar days. "Today" includes the 11 am call you have not made yet.
- Manager views should sum the team by person and role, and every number should open the list behind it.
- On reassignment, start the new owner today and hand over the promise, not just the lead.
Why one "next follow-up date" breaks on a shared student
Take an illustrative student, Riya, enquiring about a master's in the UK. Over three months, four people touch her file:
| Role | Waiting on | Next action |
|---|---|---|
| Telecaller | First contact, basic qualification | Call back Thursday evening (she was in college) |
| Counsellor | Agreed shortlist, documents | Review the SOP draft on Monday |
| Application officer | Two university applications | Chase the offer decision in 10 days |
| Visa officer | Financial documents | Check the bank statement on the 20th |
All four dates are real commitments. With one "next follow-up" column, only the last one saved survives. The visa officer sets the 20th, and the counsellor's Monday SOP review silently disappears.
The damage is predictable:
- Overwritten promises. Nobody notices until the student complains.
- False overdues. The telecaller's old callback date lingers after the counsellor takes over, so the lead looks overdue for someone who no longer works it.
- Invisible work. A manager cannot tell whether the counsellor or the application officer is behind.
- No accountability. A field that belongs to everyone belongs to no one.
Teams on spreadsheets often add columns such as "Counsellor FU" and "Visa FU" that nobody maintains. The instinct is right. It just needs structure.
The role-based model: each role owns its own follow-up
A follow-up belongs to a role on a lead, not to the lead. Each role working the student keeps exactly one live follow-up of its own. Four people means four dates, and none of them overwrites another.
Four rules make it work:
- One live follow-up per role per lead. Extra reminders go in the note. The follow-up is the next moment that role must act.
- Only roles doing hands-on work at that stage carry one. A telecaller should not hold a follow-up on a lead in Visa, and a branch manager supervises rather than holding a personal follow-up on every lead.
- Applications get their own follow-ups. If Riya applies to two universities, treat each application as its own record (a "deal") with its own stage, owner and follow-up, so the offer chase on one does not hide the deposit chase on the other.
- Completing a follow-up means setting the next one. "Done" with no new date is how leads go quiet. The exception is a stage or status that needs no follow-up, such as Enrolled or Not interested.
A typical study-abroad matrix, to adapt to your own stages:
| Stage | Telecaller | Counsellor | Application officer | Visa officer |
|---|---|---|---|---|
| Inquiry | Yes | — | — | — |
| Qualify | — | Yes | — | — |
| Application | — | Yes | Yes | — |
| Deposit | — | Yes | Yes | — |
| Visa | — | Yes (light touch) | — | Yes |
| Enrolled | — | — | — | — |
The counsellor stays on through Visa on purpose: a weekly check-in prevents drop-offs while the visa officer handles the paperwork.
Set a follow-up policy for every stage
A stage policy needs just two answers:
- Is a follow-up needed here? Statuses like "Not interested" or "Enrolled" should not generate one.
- When is the first one due? This is the number of days after the lead enters the stage or status. Zero means the same day.
An example:
| Stage / status | Needed? | First due | Why |
|---|---|---|---|
| Inquiry: new | Yes | Same day | Reach the student before a competitor does |
| Inquiry: not reachable | Yes | Next day | Retry at a different time of day |
| Qualify: documents pending | Yes | 2 days | Give the family time to find marksheets |
| Application: in progress | Yes | 3 days | Check the portal, chase missing items |
| Application: offer received | Yes | Same day | Deposit deadlines are tight |
| Visa: submitted | Yes | 7 days | Mostly reassurance, so weekly is enough |
| Not interested / Enrolled | No | — | Closed or handed over |
Put each rule at the most specific level that needs it. A stage default (Application: 3 days) with a status override (Offer received: same day) beats a dozen special cases in people's heads. If leads age badly in one stage, shorten its days, or add a hard requirement: no move to the next stage without a scheduled follow-up.
Overdue, Today, Later: count in local calendar days
Teams define these buckets differently, and the difference matters. Use India time (IST) calendar days, anchored at midnight:
- Overdue: due on any previous day.
- Today: due at any time today, including items whose time has already passed.
- Later: due after tonight's midnight.
Why not call anything past its time "overdue"? Because then an 11 am callback turns overdue at 11:01, the Today list shrinks as the day goes on, and at 5 pm a counsellor with forty calls due sees "Today: 2". The dashboard and the board start to disagree about the same lead, and people stop trusting both.
Calendar days give each counsellor a clean daily contract: clear Overdue first, then work Today, and leave Later alone. An item earlier today is still today's job. It becomes overdue only if the day ends without it.
If your software runs on UTC, check where "midnight" falls. UTC midnight is 5:30 am in India, so a system that changes the day on UTC puts late-night calls in the wrong bucket.
Manager views that add up
A manager's view should be the sum of the team's lists, in three cuts:
- By person: overdue, today and later for each counsellor and officer. This is your stand-up screen.
- By role: if application officers are behind while counsellors are fine, that is a capacity problem, not a discipline problem.
- By branch: a growing backlog usually means someone is absent or overloaded.
Two tests tell you whether to trust it. First, the parts should add up to the total. If they do not, something is double-counted, often a lead with two applications. Second, every number should open its list. If "Overdue: 37" opens 41 leads, the next meeting will be about the software, not the students.
A manager who also counsels should see "my follow-ups" and "my team's follow-ups" as separate views.
Reminders that people do not mute
Reminders should fire at the due time and go only to the person who holds the follow-up, as a browser popup at the desk and a phone notification on the move. Keep them separate from team chat so people can mute the chatter without muting the job, and keep an inbox of reminders for the alert that went off while someone was on another call.
Date-only follow-ups suit telecallers working through a list. Timed follow-ups suit counsellors with booked calls. Pick one approach per team so Today means the same thing to everyone.
WhatsApp follow-ups have a catch. On the WhatsApp Business Platform, a message from the student opens a 24-hour customer service window, and once it closes you can send only pre-approved template messages (Meta for Developers: service messages). For follow-ups due days out, keep an approved "checking in" template ready. More in our guide to a WhatsApp CRM for education.
Handling reassignment without losing the thread
When a counsellor leaves or a branch reshuffles, the lead moves, but the promise made to the student often vanishes. A handover checklist:
- Keep one owner per role. When Meera takes over as counsellor, the previous counsellor comes off the lead.
- Start the new owner today, and carry the promise in the note. Make the new counsellor's first follow-up due today so they introduce themselves on day one. If Monday was promised, write it in the handover note and set the next follow-up for Monday after that first call.
- Leave other roles alone. A counsellor change must not touch the visa officer's follow-up.
- Write a two-line handover note saying where the student is and what was promised. If calls are recorded, point to the last relevant one; see CRM with call recording.
- Keep the history. End the old assignment rather than deleting it, so disputes, incentives and reviews can see who owned the lead and when.
- Check Today after a bulk reshuffle. Moving 300 leads can land 300 same-day follow-ups on a new team. Spread them out or let the manager triage.
A weekly follow-up hygiene routine
Thirty minutes every Monday keeps the lists honest:
| Who | Task | Time |
|---|---|---|
| Each counsellor and officer | Deal with anything more than 7 days overdue: act, re-date with a reason, or close | 10 min |
| Each counsellor and officer | Set dates on leads that have none but sit in stages needing one | 5 min |
| Team lead | Review overdue by person and role, and rebalance | 10 min |
| Team lead | Spot-check five leads: does the latest note explain the date? | 5 min |
| Owner or admissions head (monthly) | Revisit the stage policy's days for this intake | 15 min |
Watch for four warning signs:
- Follow-ups re-dated three times with no note.
- A stage where most leads have no follow-up.
- Live follow-ups on closed statuses.
- Different screens counting "Today" differently.
Track overdue at the start of the day rather than "follow-ups done". Completions reward re-dating.
How Xale handles this
Shared students are normal in study-abroad and admissions teams, so we built follow-ups in Xale around this model:
- Role-based follow-ups. Each role on a lead or deal keeps its own follow-up, and only roles doing hands-on work at that stage carry one. Each university application can be its own deal with its own stage, owner and follow-ups.
- Stage policies. Per-stage Follow-ups permissions decide which roles carry a follow-up, and statuses such as "Not interested" can be switched to need none. A stage requirement can block a move until a follow-up is scheduled.
- Calendar-day buckets. Overdue, Today and Later follow IST calendar days.
- Reminders. A check every minute alerts the holder of a due follow-up by web popup, Android app push and an inbox entry.
- Manager views and permissions. The dashboard shows follow-ups with branch and per-user load. Per-stage permissions decide who can edit follow-ups and who can only view them.
- Clean handovers. One active owner per role per lead or deal; old assignments are revoked, never deleted. When a role changes hands, the old owner's follow-up is closed and the new owner starts their own. Automations can set follow-up dates, and a time-based trigger can catch leads with no follow-up.
See the follow-up management CRM page for the full tour, or how it fits a wider study abroad CRM with branch- and role-based access.
Frequently asked questions
Should every role on a lead have a follow-up at all times?
No. Only roles doing hands-on work at the current stage should hold one, and a stage or status such as Enrolled or Not interested should generate none. A telecaller's follow-up should close when the lead moves into Qualify and the counsellor takes over, and supervisors should not carry personal follow-ups on every lead; they watch the team's lists instead. Fewer, deliberate follow-ups are easier to trust than one on everything.
Does "Today" include items whose time has already passed?
Yes. Today means due at any time today in India calendar days, so an 11 am callback that has not happened yet still shows under Today at 5 pm. An item becomes Overdue only once the day ends without it. That keeps the Today list stable through the day, gives each counsellor a clean daily contract, and stops the dashboard and the board disagreeing about the same lead.
How many days after a stage change should the first follow-up be due?
Base it on how quickly the student must act. New enquiries and offers received should be due the same day, since a competitor or a deposit deadline will not wait; document chasing suits one to three days; waiting periods such as a submitted visa need only a weekly check-in. Set a default per stage, override it per status where needed, and review the numbers each intake as leads age differently.
What is the best metric for follow-up discipline?
Overdue at the start of the day, by person and by role, together with the share of active-stage leads that have no follow-up at all. Both are hard to game, unlike follow-ups completed, which rewards re-dating. Check the two numbers every Monday, look for follow-ups re-dated three times with no note, and make sure any number a manager reads opens the exact list of leads behind it.
We use one follow-up column in a spreadsheet. Where do we start?
Add one column per role, not per person, and write your stage policy on one page: which roles carry a follow-up at each stage and how many days after entry the first one is due. Agree that Today is a calendar day. When the sheet gets hard to maintain, usually by the second branch or the third role, move to a CRM that tracks follow-ups per role and opens the list behind every count.