Consent and opt-outs on messaging apps

Why WhatsApp, Telegram and Facebook need a consent basis, how to record one, and how opt-outs and objections work.

Messaging apps are personal. People use WhatsApp, Telegram and Messenger for friends, family and businesses they chose to talk to. Their terms forbid spam and bulk messaging, and in many countries the law treats an unsolicited marketing message to a person as something that needs their consent. That is why GraphKit treats these channels differently from LinkedIn.

This page explains how GraphKit works. It is not legal advice: check the rules that apply to you with your own adviser.

On WhatsApp, Telegram and Facebook, a campaign step runs only when the lead's identity on that channel has a consent basis:

BasisMeaningHow it is recorded
Existing conversationThe person has already messaged one of your accounts.Automatically, when they write to you.
Opt-inThe person agreed to hear from you on this channel, for example on a form, at an event or by sending a keyword.An admin records it on the lead.
Imported with consentYou imported the person in a file of people who opted in to this channel.Chosen per channel when you import the file.
Friend (Facebook only)The person is a Facebook friend of the sending profile.An admin records it on the lead.

A lead without a basis is skipped on those steps, never messaged. Every consent change is written to the audit log with the old and new value, and only admins can make one.

Record a basis only when you can show it. If someone asks why you messaged them, the basis and its record are your answer.

Opt-outs

Anyone can opt out by replying. On WhatsApp, Telegram and Facebook, GraphKit always checks every inbound message; on LinkedIn and Instagram, an admin can turn the same check on.

A message opts the lead out when it starts with an opt-out word ("STOP", "Stop messaging me", "unsubscribe") or is four words or fewer and contains one ("please stop"). The words cover English and German, Nordic, French, Spanish, Portuguese, Italian, Dutch and Russian, and you can add your own. Ordinary words that often start a reply, like "end" or "cancel", are not included, so a normal answer is not mistaken for an opt-out. When in doubt GraphKit errs towards opting out, because a false opt-out only stops outreach.

When someone opts out, GraphKit:

  1. suppresses the lead and every identity it has, on every channel;
  2. stops it in every campaign;
  3. blocks further replies to it from the inbox and the API.

An unsubscribe reported by a connected email platform does the same.

Objections and first messages

Data protection law in the UK and EU gives people an absolute right to object to direct marketing, and expects them to be told about it at the first contact. In practice:

  • Say who you are and why you are writing in the first message.
  • Tell people how to stop, for example "Reply STOP and I won't message you again." It is short, and it works on every channel GraphKit checks.
  • Honour objections everywhere. When someone objects in any way (not only with a keyword), suppress them with the reason opted out. The suppression covers every channel and survives deleting and re-importing the lead.
  • Answer access and erasure requests with the lead's data export and delete.

LinkedIn and Instagram

LinkedIn and Instagram do not require a consent basis in GraphKit, because outreach to professionals there is common practice. The same courtesy still applies: say who you are, make stopping easy, and suppress anyone who asks you to stop.

On this page