Playbooks · 5 min read
Referral Programmes Without Codes, Links or Any Tracking
A referral programme has three moving parts. The ask, the tracking, the reward.
We do one of them, partly.
There is no referral code generator here, no unique link per customer, no click attribution, no way to tell that this new customer came from that old one, no rewards ledger, no points, no payouts, and no analytics of any kind to report on it with. If you are choosing a tool to run a referral programme, this is not the tool, and you should know that in the first thirty seconds rather than after the trial.
What we do is replies. Which turns out to matter at exactly one point in a referral, and it is the point most programmes handle worst.
The moment a referral actually reaches you
Referrals do not arrive as tracked clicks in the businesses this product serves. They arrive as a sentence.
"Hi, Neha ne aapka page bataya."
"My sister got her mehendi done by you last month."
"Saw your work at a friend's wedding, do you do Bangalore?"
That message is the highest-intent thing that will land in your inbox all week. The sender is not researching. They have already been sold by somebody they trust, and they are checking one or two practical things before committing. And they will very often get the same reply your automation gives a cold stranger who typed price.
A referred customer arrives pre-sold. The only way to lose them is to answer as though they arrived cold.
Build the one automation that is worth building
Keywords first, because referral language is unusually predictable within a business. Look through six months of your inbox and pull the actual phrases. For most Indian accounts the set includes some of: referred, referral, friend, bataya, recommend, recommended, saw at, cousin, sister.
Matching folds case and punctuation, so Referred? and referred are one thing. It does not fold Indic vowel signs — if your customers write in Devanagari, the forms they actually type each need listing, because two words that differ only by a vowel sign stay two different words.
The reply itself has one job and it is not selling.
A version that works: "Arre, that is lovely to hear — kaun bheja aapko? Bata dijiye toh main unko thank you bolungi. Aapko kis date ke liye chahiye?"
It asks who, which you need. It asks for a date, which is the practical question. And it ends with something easy to answer, which is the only mechanism that reopens the twenty-four hour window for a second turn.
The ledger is yours, and it is a spreadsheet
Here is where honesty costs something. When the referred person answers "Neha bheja", nothing in this product records that as a link between two customers. There is no referrer field. There is a lead record with a note somebody types.
So the workflow is: a human reads the answer, opens the lead, and types ref: @neha_makeup. Later you export leads as a CSV, sort by that note, and see who has sent you people. That is the whole reporting layer. No dashboard, no attribution model, no automatic reward.
It is unglamorous and it is also what most small programmes were doing anyway, badly, in WhatsApp. Doing it deliberately in one place is a real improvement over doing it accidentally in five.
Never automate the reward
Even if you had a way to, do not. Two reasons and both are practical.
An automated reply cannot verify a claim. If typing referred earns a discount, the discount belongs to anybody who reads your caption carefully, and by next month it belongs to a screenshot in a deals group.
And a reward promised in public is a promise with no expiry date. A public reply sits under a post for years and keeps being read. If it says "tag a friend and both get 20 off", you are still honouring that in 2028 or explaining why you are not. Volatile facts belong in a private reply a person can change, or on a page you control.
Making the ask, which is not a software problem
The reason your referral programme is small is almost never the tracking. It is that nobody was asked, or they were asked to remember a code.
What travels between two people on a phone is a screenshot or a forwarded Reel, not an alphanumeric string. So the thing to build is a post worth forwarding, with a caption that tells the friend what to do when they land: comment BOOK and I will send dates. The referrer forwards it, the friend comments, the automation answers, the lead is captured with a note. No code survives that journey, and none is needed.
Two adjacent posts if you are working this seam properly: customers posting about you and the longer-term version with people who advocate repeatedly.
