Skip to main content
Consent decides which channels your organization can use to message an end user. Tars records consent separately for each outbound channel instead of one organization-wide flag. The web channel has no outbound-consent record.
Granted and withdrawn consent states tracked for the WhatsApp channel, with the import and keyword sources and the effect on campaign sends
Consent is not a field on the end user profile. The profile’s Identity and Additional attributes cards hold identity details, and the sidebar holds labels, tags, and metadata, but no consent toggle. The one consent control in the Users section sits in the Import users modal. Before you can start a CSV import, you must check a consent acknowledgement. The checkbox confirms that every imported end user opted in to receive outbound messages. The Import all and Start import buttons stay unavailable until you check it. Every consent change is stored on the profile record with its source and time. The source reads as an import, an API call, a manual change, an organic grant, a keyword reply, or a bounce. Each channel keeps the last 100 changes. The dashboard does not show this history.

​
Automatic updates from replies

When an end user replies STOP or UNSUBSCRIBE, Tars withdraws that channel’s consent. A START reply restores it. The whole message must be the keyword, so any extra text stops the match. Tars does not check these keywords on the web channel. An opt-out also resolves the end user’s open conversations on that channel, up to 200 of them, with the reason end_user_opted_out. Tars sends a confirmation message on the channel after an opt-out and after a START reply. An agent can require a data-consent step before a web conversation begins. The end user chooses Accept or Decline before the first message. The end user must answer before sending the first message. The answer is stored on the conversation and does not record channel consent.
A campaign eligibility check on consent per channel, sending to granted end users and excluding opted-out ones who remain members of the target segment
Audience campaign eligibility checks consent before sending. Only end users with granted consent on the channel receive a send. Opted-out end users and end users with no consent record are excluded, even when they are still members of the target segment. A webhook campaign checks consent on each API call. The call is rejected with consent_revoked only when the end user has opted out of WhatsApp. See Webhook campaigns API.
  • During a CSV import, after you check the consent acknowledgement, for the channels the end user’s email or phone can reach. A channel that already holds a consent record, granted or withdrawn, is left alone, so an earlier STOP survives a re-import.
  • Through a START reply on the channel.