A Practical Consent Checklist for Customer Messaging in India
Consent is channel-specific and context matters. This checklist separates India’s telecom commercial-message rules from platform policies and helps teams keep better records of customer preferences.
Consent is not one universal checkbox
Businesses often collect a phone number or email address during a purchase and later treat that as permission for every kind of message. Those are different things. A person may expect an order update but not a recurring offer; they may agree to email but not WhatsApp; and a request for help in a social DM does not automatically invite unrelated campaigns.
For WhatsApp, the current WhatsApp Business Messaging Policy requires businesses to have the person’s number or username and opt-in permission before contacting them, and to respect requests to stop. Businesses are responsible for ensuring their collection method also complies with applicable local law.
In India, TRAI’s TCCCPR framework concerns commercial communications sent using telecom resources, particularly SMS and voice. Its requirements should not be casually described as the rule for every Instagram DM or email. Check the relevant channel policy and get qualified legal advice for your specific campaign and data use.
Keep channel rules distinct
Write down what the person is agreeing to receive, from which business, on which channel, and for what purpose. Make the choice easy to understand before the customer submits a form. Do not hide marketing permission inside a general terms checkbox or suggest that a purchase requires promotional messages unless that is genuinely necessary and lawful.
Different channels have different controls. WhatsApp has its own business messaging policy; Instagram and Messenger have platform rules for business conversations; email sending has its own provider and applicable legal requirements; telecom SMS and calls are subject to TRAI’s framework. One recorded choice should not silently be copied across these channels.
- Separate transactional updates from promotional communication.
- Explain the channel and message purpose at collection time.
- Keep required platform templates and approved pathways current.
- Do not use a new channel as a workaround for an opt-out elsewhere.
Record choices and opt-outs
Keep a concise record of the source and date of a preference, the wording shown, the channel and purpose selected, and any later change or withdrawal. Restrict access to these records and retain only what your process needs. A timestamp without context may not tell your team what the person actually agreed to.
Make opt-outs easy to recognize and route. When a customer asks to stop, record that choice promptly, stop the relevant sends, and prevent later imports or duplicate records from re-enabling them by accident. If a person opts out of promotional messages but still needs an essential service update, handle that separately and explain the distinction clearly.
TRAI provides official guidance on sender obligations and customer consent management. These pages are useful starting points for telecom commercial communications, not a substitute for reviewing other applicable rules.
Build a reviewable process
Before a campaign, check the audience source, selected channel, message purpose, and suppression list. Sample a few records and verify that each has the right permission. After sending, review complaints, blocks, bounces, and opt-outs as signals that your targeting or wording may not match customer expectations.
- Name the team member accountable for preference changes.
- Keep permission records close to the customer record but limit who can view them.
- Test that opt-outs suppress future sends across connected workflows.
- Ask counsel to review campaigns when the regulatory scope is unclear.
Samyoj can help organize customer conversations and records, but a CRM does not create consent or determine legal compliance for a business. Configure channel rules around your actual collection process and current platform terms.
Takeaway: record a clear, purpose-specific choice and honor it on the channel it covers; do not rely on one “consent” flag for every message.
A simple preference record
A useful record might say: “On 30 October, the customer selected WhatsApp order updates on the checkout form; promotional messages were not selected.” Keep the form wording or version, source, date, and any later withdrawal with the record. This is more informative than a lone consent=true field, which does not say what the person agreed to.
When a customer opts out, test the suppression path from end to end: remove them from the relevant audience, stop scheduled messages, and prevent later imports from re-adding them automatically. For telecom SMS or voice campaigns in India, consult TRAI’s current sender guidance; for social messages and email, also review that provider’s rules and the laws that apply to your business and audience. This article is operational guidance, not legal advice.
