A referral programme that lives in WhatsApp
Education institutes in India win most of their students through word of mouth — but the people doing the recommending will never install an app or visit a portal. So this platform gives referrers no screen at all: they message an institute's WhatsApp number, get one permanent link, and get paid. Everything else happens in two dashboards behind the scenes.
How a tap becomes a payout
Anyone who messages an institute's WhatsApp number becomes a referrer and receives one permanent short link. The link redirects each visitor into the institute's AI admissions chat, carrying attribution. From then on, the admissions chat reports every stage of that student's journey to a webhook — which stores each event append-only, prices the reward the moment enrolment is confirmed, and messages the referrer at milestones.
Nothing is ever recomputed behind anyone's back: the funnel is an event ledger, each reward row freezes the rate and fee it was priced from, and a month's payout report is the same every time it is opened.
“Hi”
Any message mints a referrer + their permanent link
/r/kQ3vX9aZ
Visitor lands in the institute's admissions chat, attributed
9-stage funnel
The chat reports each stage; stored append-only, idempotent
Reward minted
Priced from the rate card at enrolment, then frozen
Monthly CSV
Institute pays referrers; WhatsApp tells them the good news
Walk through the institute dashboard
Each institute signs in to its own workspace. Click through the eight screens below — every number you see was produced by replaying real funnel events through the live system, not by mocking the UI.
Sixty seconds, end to end
Recorded against a locally running instance seeded with fictional data — no real students, referrers or phone numbers appear anywhere on this page. Click any screenshot to enlarge it.
Under the hood
Append-only funnel
Stage reports are events with idempotency keys, not mutable state. A duplicate delivery is dropped at intake; history can always be replayed and audited.
Rewards frozen at earn time
Each reward row stores the rate, basis fee and amount as they were the moment enrolment confirmed. Later rate-card changes never rewrite anyone's money.
Fail-closed webhook intake
Deliveries are accepted with 202 into an inbox ledger and processed asynchronously — unknown codes and failures are recorded, never silently lost.
Monthly payouts that never drift
A payout month cuts on when the reward was recorded, so a report re-opened later shows the same figures — no double-pay, no missing rows.
Three security perimeters
Google OAuth (domain-restricted) for platform staff, session-auth per institute workspace, and shared-secret token auth for machine webhooks — each in its own filter chain.
Multi-tenant by design
Institutes are hierarchical tenants with their own WhatsApp number, programmes, rate cards and users; a credential sees its own subtree and nothing else.