miatzSign in

Personalising outbound messages your consent records already permit

Draft a per-recipient variant of an outbound message from the account details you already hold, and release it only to those numbers your registered consent and preference records still allow you to contact at all.

Effort
Weeks of work
Skill level
Comfortable with software
Organisation size
Small business
Value
Time saved, Revenue

Tools named for this

  • A drafting model working only from account fields you already store
  • Your sender registration and consent records on the operator platform
  • A suppression check that runs immediately before anything is released

What to check before you ship it in India

  • Regulation 32 of the TCCCPR 2018 bars any business or legal entity not registered with an access provider for the purpose of sending commercial communications from making one, causing one to be sent, or authorising it. Personalisation changes nothing here: an unregistered sender is unlawful whoever or whatever wrote the words.
  • Section 6(1) of the DPDP Act 2023 requires consent to be free, specific, informed, unconditional and unambiguous, and limited to the personal data necessary for the specified purpose — so details collected to service an account do not by themselves license selling into it.
  • TCCCPR regulation 2 defines a promotional content template as fixed content, common across all communications sent to different recipients on the same subject — unlike a transaction template, which may combine fixed and variable parts. A per-recipient promotional variant therefore does not fit a registered promotion template at all. Confine per-recipient wording to channels TCCCPR does not govern, or to variation a registered template actually permits.

Sources

Every claim on this page traces to one of these, on the date it was read.