Playbooks · 5 min read
There Is No Loyalty Feature Here. What to Do Instead
We do not have a loyalty product. Not a small one, not a partial one, not one behind a paid plan.
There are no points. No tiers, no stamps, no rewards balance, no member IDs, no coupon generation, no discount codes issued or validated, no purchase history, and no lookup of any kind against a customer record that lives somewhere else. There is no integration with your loyalty platform, your POS or your store — captured leads leave as a CSV file and that is the whole of the export story.
If you came here looking for a way to run a rewards programme through Instagram DMs, this product does not do it and no amount of clever template writing will make it. Read the first two sections and then decide whether the rest is useful to you.
The questions still arrive
Here is the part that is real. You may run a loyalty programme elsewhere — a card, a spreadsheet, an app, a Shopify plugin — and the moment you announce it on Instagram, the questions about it land in your DMs.
"Mere kitne points hain?" "Is my coupon still valid?" "Am I still a gold member?" "I bought three times, do I get the discount?"
Every one of those is a lookup against a record the automation cannot see. And the failure mode is specific and bad: a confident automated reply that guesses. A template that says "yes, your discount is active!" to somebody whose code expired last month has made a promise on your behalf that a human now has to break at the counter.
Build the refusal list first
Before you write a single loyalty-adjacent template, write the list of words that must produce silence and a routed conversation.
points, balance, member, membership, coupon, code, voucher, expired, redeem, reward, discount code, refund, invoice, bill, charged, plus the Hinglish your customers actually type: points kitne, code nahi chal raha, paisa kat gaya, discount nahi laga.
Matching folds case and punctuation, so you are listing words rather than spellings of words. Put all of them in the negative keyword field of every automation that could plausibly catch a customer with an account problem — which is most of them.
The result is that those people get no automated reply and reach you. That is not a degraded experience. For this category of question it is the only correct one.
What is genuinely automatable: the programme, not the person
Split loyalty questions into two piles and the useful half becomes obvious.
About the programme — templatable
About this person — must route
The left column is static, identical for everyone, and asked constantly. Those are templates, and templated replies are free and unlimited, so answering the same six programme questions four hundred times costs nothing.
The single most useful template you can write is the one that tells people where to check their own balance. A link to the account page, an app name, a phone number for the shop. It answers the question the person actually had, without pretending to know anything about them.
The honest substitute for a loyalty CRM
You will want some way to recognise a repeat customer. Here is what exists, and it is manual.
A lead record holds a stage, tags, a replied flag, interaction counts and notes. None of it knows anything about purchases. What it gives you is a place to write, in your own words, "bought twice, always asks about restocks" or "regular, prefers COD" — and the interaction count tells you this is not the first conversation.
That is not loyalty software. It is a memory, and it works the way a good shopkeeper's memory works: the second conversation does not start from zero. The nurturing post argues the record-keeping habit properly, and it is the closest thing to a loyalty motion this product supports.
You cannot reward a customer here. You can remember them, which is most of what a loyalty programme is actually buying.
And you cannot message your loyal customers
Worth saying because it is the feature people most expect. There is no broadcast. No way to message your best customers about early access, a members-only drop, or a points expiry. The DM window is twenty-four hours and is restarted only by their message, so you can reply to a loyal customer, warmly and fast, but you can never start the conversation.
Every loyalty campaign that works on email or SMS assumes the sender picks the moment. On Instagram the customer picks it. That is not a limitation we chose and it is not one any tool on the official API gets around.
Which means the only outbound you have is your posting. A members-only drop gets announced in a post, people comment, and the automation catches them. That path works. The one where you push a notification to a segment does not exist.
Where this leaves you
If your loyalty programme is real and lives in another system, the useful job for automation here is narrow: explain the programme to everyone who asks, refuse every question about an individual account, and route those people to a human quickly. That is genuinely worth building, and it takes an afternoon.
If you were hoping to run the programme itself in the DMs, build it somewhere that can hold a balance. What leaving with your data looks like is a CSV, and the subscription-business post covers the same shape of problem for recurring customers.
