> ## Documentation Index
> Fetch the complete documentation index at: https://docs.marro.si/llms.txt
> Use this file to discover all available pages before exploring further.

# Contact preferences

> One page where each person chooses which marketing they get from you, by email, WhatsApp and SMS.

Every marketing email you send links to the person's own preference page. There they choose what you may send them:

* **Marketing email**: campaigns and email sequences.
* **WhatsApp marketing**: marketing templates, from broadcasts, automations or a person on your team.
* **SMS marketing**: automated texts.

The page also says what always reaches them: replies to messages they send you, receipts, invoices and payment
messages, and appointment confirmations and reminders. Opening the page changes nothing; their choice counts once they
press **Save**, or **Unsubscribe from all marketing**.

## What each choice stops

* **Marketing email off**: no campaign and no email sequence goes to that address. The unsubscribe link in sequence
  emails opens the same page.
* **WhatsApp marketing off**: templates in the Marketing category are not sent to that number. Utility and
  authentication templates, and your replies in an open chat, still go.
* **SMS marketing off**: automations send no SMS to that number. A message a person on your team sends still goes.

Someone who replied **STOP** on WhatsApp or by SMS gets nothing on that channel until they reply **START**; the page
says so instead of offering a switch.

## For your team

Each lead's page, on the web and in the Marro app, has a **Marketing** section in the record panel on the left (it opens on click): email, WhatsApp and SMS, allowed or stopped (when and how), and the campaign
emails they were sent. When someone asks you to stop, press **Stop** beside the channel there, or ask Marro to record
it ("Asha asked to stop marketing email"); both ask you to confirm. Only the person can turn marketing back on, from their
own page. Ask Marro what a lead has stopped and
which campaigns they were sent.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.