Repli keeps a consent record for every contact. When someone replies STOP, they are opted out and blocked from campaigns, template sends and follow-ups — with the reason shown — until they reply START or you opt them back in.
Consent is enforced inside every campaign — see how sends work on the WhatsApp broadcast softwarepage.
Each contact carries an opt-in status with its source and when it changed, visible on their record.
A clear opt-out reply such as STOP marks the contact opted out. A START reply opts them back in. No manual list cleaning.
Campaigns and CRM template sends check consent before sending. An opted-out contact is excluded and the report shows why.
Consent changes are recorded, so you can see when a contact opted out and how — a reply, or a change your team made.
Before a spreadsheet audience can be sent, you confirm those contacts opted in. Repli will not send without that confirmation.
Your team can opt a contact in or out from their record — for example when someone asks in their own words rather than typing STOP.
The contact is marked opted out immediately. Your next campaign excludes them and the report lists the exclusion reason. If they later reply START, they are eligible again.
Customers tick “send me offers on WhatsApp” at checkout. You upload the sheet, confirm opt-in, and only then can the campaign send.
A customer asks in their own words to stop receiving messages. A teammate opens the contact and opts them out by hand; the change is recorded.
WhatsApp requires businesses to have opt-in before messaging people, and Meta can limit or pause numbers that receive many blocks or reports. Consent is not just a legal checkbox — it is what keeps your number able to send.
Repli’s job is to make the consent state of every contact explicit and enforced, so a mistake cannot slip through a campaign.
Automated: clear opt-out and opt-in commands such as STOP and START update the consent record, and every campaign and template send checks that record first.
Not automated: a customer who phrases the request differently — “please stop messaging me” — is not keyword-matched. Your team changes consent from the contact record, and the change is recorded. You remain responsible for the opt-in being real when you upload contacts.
They are two separate rules. The 24-hour window decides whether you can send a free-form reply or need an approved template. Consent decides whether you may message the person at all. Repli enforces both: templates outside the window, and opt-in before any business-initiated send.
Repli marks the contact opted out and blocks them from campaigns, template sends and follow-ups. The exclusion reason is shown in campaign reports. They can opt back in by replying START, or your team can change consent from the contact record.
No. Clear commands such as STOP are detected automatically. Requests phrased in other words need a teammate to opt the contact out from their record — the change is recorded either way.
You can upload a spreadsheet, but Repli requires you to confirm those contacts opted in before sending, and WhatsApp’s own rules make you responsible for that permission being real. Purchased lists usually are not opted in.
Consent records and enforcement are part of WhatsApp CRM and Marketing, which unlock on Growth at ₹999/month. Pro+ and Commerce include them too.
No. Consent decides whether you may message someone at all; the 24-hour window decides whether the message can be free-form or must be an approved template. Repli enforces both.
Pricing · All features · How it works · Blog