Software training institutes · Follow up systems
Turn the demo class crowd into admissions with a follow-up the counsellors can keep.
A follow-up system for a software training institute is the set of messages and calls that run between an enquiry, the demo class and the admission decision. GullySales works on who gets contacted, when, and in what words.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What follow up systems means
A follow-up system is the set routine for calling, messaging or emailing an enquiry more than once, since most buyers do not decide on the first conversation. GullySales sets the number and timing of follow-ups so an undecided buyer keeps hearing from you until they decide either way.
Also for software training institutes
- Lead generation for software training institutes
- CRM for software training institutes
- SEO for software training institutes
- Local SEO for software training institutes
- Social media marketing for software training institutes
- Content marketing for software training institutes
- Buyer personas for software training institutes
- WhatsApp marketing for software training institutes
Sales and marketing for software training institutes, the overview.
Last updated 14 Nov 2026.
For software training institutes
Where it usually goes wrong, and what we would do.
“Half the demo crowd goes silent”
Learners attend a demo, say they will think and then stop replying. Without a plan, the counsellor calls everyone once and then loses track.
“Not every attendee is equal”
A learner who asked about batch timing and fees is closer to joining than one who sat quietly. A simple mark of hot, warm or cold lets the counsellor spend time where it counts.
“The message must match the doubt”
A learner worried about the job link needs a different note from one worried about the fee. A single reminder sent to all reads as noise.
“Seat dates create honest urgency”
A batch starts on a date and the seats are limited. Saying so plainly is useful to the learner and needs no pressure or invented deadline.
What we do
What we deliver for software training institutes.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
Demo follow-up plan
A sequence of messages and calls for each of hot, warm and cold attendees.
Result: Each attendee is marked and has a next step.
Message templates
Short notes on WhatsApp, SMS and email for common doubts such as fee, timing and support.
Result: The team sends approved notes, not improvised ones.
Call scripts
An outline for the follow-up call with questions to ask and notes to record.
Result: A counsellor can run a follow-up call from the sheet.
Missed-lead recovery list
A list of enquiries that went quiet, with a reason to reopen each.
Result: Dormant enquiries are checked and contacted once more.
Stop rules
A rule for when to stop contacting a learner who has said no.
Result: Nobody receives a message after asking to stop.
How the result is measured
- Follow-up completion rate
- Average number of follow-ups before close
- Enquiries closed after repeat follow-up
Recorded as a baseline before work starts, so every later report has an honest comparison.
What to capture or send
Record what each demo attendee said, so the next message answers that doubt.
After a demo class the counsellor holds a room of names. These notes decide who gets which message.
- Doubt raised at the demo
- Fee, job link, batch timing or difficulty. The trainer or counsellor writes it down so the follow-up message answers it.
- Demo attendance mark
- Present, left early or did not come. A learner who missed the demo gets the recording link, not a seat reminder.
- Batch start date and seats left
- Stated to the learner as a fact in the message, so the reason to decide is the date and not a pushed offer.
- Parent or sponsor to be called
- Name and best time to call. The second call is held when that person is free and not when the counsellor is.
- Reason for a stop
- Joined elsewhere, postponed, fee too high or no reply. Recorded so a stopped learner is not messaged again.
Who it is for
This is written for these software training institutes.
- Classroom institutes in IT hubs such as Hyderabad, Bengaluru and Pune
- Online and hybrid software course providers
- Institutes for non-IT graduates changing careers
- Software testing and QA training institutes
- Full stack and web development bootcamps
- Cloud and DevOps training institutes
- Weekend courses for working IT professionals
- Institutes that teach in a college as a campus programme
Before you decide
When this may not be the right fit.
- No counsellor owns the demo list, so reminders would go out to people nobody has spoken to
- The batch fee is not fixed, so the messages would quote a number the counsellor must later correct
- You have no demo class yet, so the enquiries have nothing to follow up from
Before you decide
Agree the work. Know how to judge it.
Follow-up systems for software training institutes: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
Trace recent enquiries from arrival to the last recorded action. Include a won enquiry, an unsuitable one, and one that went quiet, with personal details removed for the initial discussion.
Make the scope clear
Agree who accepts each enquiry, what makes it qualified, and how ownership changes. Include a rule for missed replies and a clear reason for closing an enquiry.
Check the work in use
Pick an enquiry at random and ask the team to find its owner, latest conversation, and next action. Check that the record agrees with what actually happened.
Know when to change course
If no one has capacity to respond, assign that responsibility before buying more leads. Automation can support the owner, but it cannot replace an unresolved handover.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from software training institutes. Anything missing is noted in the written scope, with who will supply it.
- Demo attendance sheets for recent batches
- Signed or logged lists of who attended each demo, with the course and date. They show who is warm. Without them we cannot tell attendees from enquirers, and follow-up goes to people who never saw the class.
- Counsellor notes from earlier calls
- Whatever was written or remembered about what each learner said. The notes can be rough. Voice notes recorded by a counsellor after a call are as useful as typed ones, and we can transcribe them. If they are missing, we use the first round of calls to collect them, and the groups form later.
- The seat calendar for coming batches
- Start dates and seats for each course. Honest urgency rests on it. A message that mentions a deadline the institute does not have breaks trust, so without a calendar we write no urgency at all.
- Who calls and who sends messages
- A clear split of work among counsellors, with a named owner for each learner. Follow-up fails when two people call or nobody does. Include the head counsellor's view on which learners deserve a senior call, such as a parent with a loan question. Without it, we propose a split and ask the head counsellor to confirm.
- Learners who asked not to be contacted
- Everyone who said no, stop or not now, taken from notes and WhatsApp. It protects them and you. If it is not kept, a message to the wrong person does damage that no template repairs, and the head counsellor checks the list against the notes before every new round of messages begins.
How it works
How the follow up systems work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Pull the demo attendance list and call notes
We start from the demo attendance sheets and the counsellors' call notes of the last few batches. You show us what was said to learners who went quiet. Where a counsellor left and notes went with them, we mark the gap instead of guessing what was said. What exists afterwards is a record of each attendee, the course, the counsellor and the last contact, which becomes the starting point for every later reading.
- 2
Sort attendees by what they asked
We read the notes and group attendees by the question they raised: fee, timing, placement support, prior knowledge or a parent's view. You tell us which group is worth the greatest number of calls. The product is a sorted list where each learner has the doubt that probably stands between them and joining.
- 3
Decide who is contacted and who is left
Together we write the rule for who gets a call, who gets a message and who is left alone, including learners who said no clearly. The director signs it. This protects the institute's name and gives counsellors a stop rule they can quote when they are unsure.
- 4
Write the messages and call prompts
For each doubt we write a short message and a call prompt in your counsellors' voice, using true facts about seat dates and support. You read every line and strike what you would not say. Nothing about jobs is promised. We also check that a task closes when a learner joins, so nobody calls a person who has already paid. After this step each group of attendees has a message set ready to test.
- 5
Test the tasks with two counsellors
Two counsellors use the reminder tasks on a small group of past attendees while we watch where the messages feel wrong or the reminders pile up. You decide when the flow goes to the full team. Edits to wording and task rules are made here, and the counsellors get a one-page guide.
- 6
Compare replies and admissions with the first list
We set the replies, demo rebookings and admissions of the followed-up groups beside the record taken in the first step. Counsellors tell us which messages brought a reply and which brought an opt-out. We cut the steps that gained nothing and keep those that did, and the rule is rewritten.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 2, qualification. The audit comes before it, and sales management keeps it running.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2 · you are here
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
How often should we contact a learner?
Can this be automated?
Should we message a learner who said no?
Can a learner be told the batch is almost full?
Should the owner or the counsellor send the follow-up message?
What if an attendee joined a different batch from the one they attended?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for software training institutes
Related work to consider.
Closest to this: leads and follow-up
Also for software training institutes
Or start from the overview: sales and marketing for software training institutes.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.