What do you lose when a coaching enquiry waits until tomorrow?
A coaching enquiry is rarely a request for information. It is a request for a seat. Somebody has seen an ad or a reel, they have a particular batch in mind, and they are trying to book a place in it before it fills. If you reply on Thursday to a message sent on Monday, you are not asking them to reconsider. You are telling them the thing they wanted has been taken and the next one is a long way off. That makes response time unusually direct in this trade, and unusually easy to lose to a full inbox.
Presets are illustrative starting points, not industry benchmarks. Replace every number with your own.
- Extra deals per month
- +11.0
- Close rate today → target
- 6.0% → 11.5%
- Deals per month today → target
- 12.0 → 23.0
- Lead intent gone cold before your first reply
- 50%
How it works: close rate at a given wait = your instant-reply close rate × 0.5^(wait ÷ cool-off time). Cool-off time is your assumption for how fast a lead loses interest; the low and high figures use double and half of it. This is a planning model, not a measured result. To find your real cool-off time, compare the close rates of leads you answered fast against leads you answered slowly in your own CRM.
Where coaching enquiries come from, and when
In this trade enquiries arrive in bursts and in public: a paid ad, a reel, a form off a landing page, a webinar signup, a referral message from a past student. A burst is a poor time to reply, because a class is running and the person who could answer is teaching. That is the structural version of the problem, and it is the reason a response-time promise made on Monday quietly stops being true by Friday. The interval the calculator measures is from the enquiry to the first reply from a human being, and it is the one you are most likely to shorten without hiring anyone.
A close rate in coaching does more work than it should
You are asked what fraction of enquiries you would close if somebody replied within a few minutes. Most centres can only answer that for the whole funnel, because the honest answer in coaching is that much of the selling happens over a sequence: a reminder before the batch, a nudge after the demo, a call in the evening. If that describes you, a four-hour delay will look harmless in this calculator, and the calculator is not wrong. It is telling you that response time is not your binding constraint, which is useful to establish before spending money on it.
The window is short and the buyer is in a hurry
Somebody looking for exam coaching, a career change, or help with a business that is going wrong is not browsing. They have a date: the exam, the joining date, the quarter they promised themselves. That is the case for treating your cool-off assumption as a real input rather than a default to accept. The only honest way to set it is to compare leads you answered quickly with leads you answered slowly, in your own records, and look at what actually happened to them. If nobody has ever done that comparison, the number in the box is a guess and should be read as one.
When the extra deals are a queue, not revenue
This model assumes that every deal you would win by replying faster is one you can actually deliver. In coaching, seats are the constraint. Batches have a size, a start date and a timetable that is already full. If yours are full, the rupee figure is describing demand you would have had to turn away rather than revenue you would have earned, and the sensible response to that number is a different price, a larger batch or a second batch, not a faster inbox. If capacity is not your constraint, the same figure is a fair description of what is otherwise going out of the door.
The same model, opened on a different trade
Questions buyers ask first
Most of our leads book a free demo class themselves. Does the same logic apply?
Not to those leads, and this is where the model has to be used carefully. Somebody who has booked a demo has already acted on their own, so the first reply is no longer the moment that decides anything. Run the calculation on the enquiries that need a conversation and look at the self-booked ones separately, or the answer you get will be a mixture of two different things with no way to tell them apart. What the model does establish for the self-booked group is that their clock is already close to zero, so any remaining loss sits somewhere else in your funnel and this tool will not find it.
We reply quickly and still lose people. What does that tell us?
It tells you the delay is not your problem, and it is worth believing that rather than arguing with it. This model measures one thing: how many enquiries stop being live while they wait. It has nothing to say about price, batch timing, whether the demo itself was good, or whether anybody followed up afterwards. A centre with a fast first reply and a weak close rate has nothing to fix here, and a rupee figure would only be a way of feeling busy about it.
Should I put the full course fee or a monthly instalment in the deal box?
Whatever you would genuinely book as revenue in the month you are describing, and keep it consistent from month to month. If customers pay a single fee, use the fee. If they pay over a few months, either use the fee and accept that you are modelling a booking rather than a cash month, or use the instalment and accept a smaller number. Mixing the two across months is what makes these figures impossible to compare with last quarter, and comparison is most of what a number like this is for.
Does slow reply matter more near the start of a batch than in the middle?
It is worth running the calculation twice rather than averaging, because the value of an answer depends on whether a seat exists and how close the buyer's decision is. Near a start date, an unanswered message is a decision you did not get to make. Mid-cycle, the buyer may already be committed, in which case a delay costs you nothing you could have had. A single number taken across a whole month averages those two situations together and describes neither, so treat the month a batch starts as the more informative one.
Make the first reply a recorded event
In NoxOrigin an enquiry becomes a lead with a source rather than a note in someone’s notebook. It gets an owner, and the next action is a dated work item on the opportunity rather than a calendar entry in one person’s account. Shared customer conversations stay attached to the customer record, so a reply waiting on someone is visible to the business rather than to one phone.