To measure WhatsApp lead-to-enrolment rate, choose a fixed group of valid course enquiries, follow each to a verified outcome, and divide confirmed enrolments by eligible enquiries. Keep unresolved prospects until the cohort cut-off.
Define the cohort before the formula
A rate misleads when teams mix intakes, channels or time windows. Start with a clear cohort rule, such as: valid WhatsApp enquiries for the January data course received between 1 September and 15 October.
Define a valid enquiry. Questions about dates, entry requirements, price or availability may qualify. Spam, duplicates, staff tests and messages for another institution do not. Document exclusions before seeing results.
The denominator is the eligible enquiry cohort, not the number of messages. One prospective learner may send twenty messages and still represent one enquiry. The course enquiry queue can help keep the person, intake, owner and next action together while the decision remains open.
Keep each funnel stage distinct
Do not compress interest, application and enrolment into one vague “converted” state. A useful measurement record separates stages and names the evidence required for each one.

- 1Fix the cohortName the course, intake and window.
- 2Remove duplicatesApply one written eligibility rule.
- 3Verify stagesUse authoritative evidence for each move.
- 4Keep unresolvedDo not drop open prospects.
- 5Confirm enrolmentCheck the admissions source.
- 6Report maturityLabel provisional and final rates.
| Stage | Evidence to accept | Do not count as proof |
|---|---|---|
| Valid enquiry | Person, course or intake, contact route and received time | Message count or an automated greeting |
| Qualified enquiry | Fit rule checked and next step agreed | Agent opinion without recorded criteria |
| Application started | Application identifier or authoritative application event | A promise to apply later |
| Offer or acceptance | Recorded decision from the admissions source | A positive chat reaction |
| Enrolled | Authoritative enrolment status for that intake | Payment screenshot, lead stage or campaign click alone |
Google Analytics distinguishes recommended events from automatically collected activity. Apply the same principle here: record meaningful stage changes instead of treating all activity as one conversion.
Calculate a small set of honest rates
The main calculation is:
Enquiry-to-enrolment rate = confirmed enrolments ÷ eligible enquiries × 100
If 120 eligible people enquired and 18 enrolled in the named intake, the mature rate is 15%. This is arithmetic, not an industry benchmark.
Add stage rates only when useful. Application rate is verified applications divided by eligible enquiries. Enrolment yield is confirmed enrolments divided by applicants or accepted applicants. Never switch denominators without saying so.
Use the lead qualification measurement guide when qualification is a separate gate. Use the same cohort ID in every export so records do not silently move between periods.
Protect unresolved and late outcomes
An open prospect is not a loss. Publish three numbers together: enrolled, confirmed not enrolled and unresolved. Add a maturity date based on the real admissions process, such as seven days after the last enrolment deadline.
If the cohort is still young, label the figure “provisional”. Do not compare a two-week-old intake with a fully matured one. Late payments, deferred starts and transfers should follow a written rule: either remain attached to the original cohort or move to a named later intake, never both.
This discipline also exposes missing follow-up. Compare the rate with meaningful lead response time, but do not claim that a faster reply caused enrolment without stronger evidence.
Segment without inventing certainty
Useful cuts include course, intake, market, source and owner. Show raw counts beside every percentage. A 50% rate from two enquiries is not stronger than 16% from two hundred.
Keep descriptive attribution separate from causation. Google’s conversion reporting guidance explains that attribution models distribute credit among touchpoints. A WhatsApp conversation can be the recorded enquiry source without proving that WhatsApp caused the learner’s final decision.
For source analysis, use the click-to-outcome guide. Preserve consent and source history when one learner returns through another channel.
Build a repeatable review
Create one cohort table with a stable person key, intake, first enquiry, source, stage timestamps, final outcome, outcome source and verification time. Give one owner the duplicates and unknown outcomes.
A configured DripTell CRM can keep conversation, source, lead stage and ownership together. Its controlled-pilot Customer Journey report can show recorded enquiry sources and checked events, but it explicitly does not infer verified sales or revenue. Your student system or another authoritative admissions source must still confirm enrolment.
Review weekly while admissions are open and once at maturity. Record corrections without overwriting history. Aim for a rate another person can reproduce from the same evidence.
Frequently asked questions
Should every WhatsApp message count as a lead?
No. Count one eligible person-course-intake enquiry under the rule. Messages are activity, not extra leads.
When should the rate be final?
After the cohort’s stated maturity date and after unresolved records have been checked against the authoritative admissions source. Until then, label it provisional.
Can DripTell verify that a student enrolled?
Not from conversation activity alone. DripTell can keep useful source, stage, ownership and conversation context together. A verified enrolment must come from the institution’s authoritative admissions record or a separately configured and tested integration.
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy



