Audiences

On the Audience tab of a draft campaign, you can either upload a CSV or paste a list. The format is forgiving — RCSync accepts E.164 numbers (+15555550123), 10-digit US numbers, and most common formats. Anything that doesn't parse as a valid phone is dropped before send and surfaced as “invalid” on the audience preview.

Open campaigns are the exception: they don't have an audience tab because their audience is supplied per-request by the calling system. See Campaign types → Open.

• Deduplication — duplicate phone numbers within the list are merged into one recipient.
• Validation — anything that doesn't parse as a phone number is dropped.
• Suppression — recipients on your brand's suppression list (anyone who has sent STOP or been manually suppressed) are removed.

The audience preview shows each of these as a separate number — “X recipients, Y suppressed, Z invalid” — so you can spot a problem before sending. The brand's frequency cap is tracked separately (see Governance & compliance) and is not yet reflected in the preview.

Audience uploads and per-run snapshots are encrypted at rest. Brand suppression and override lists store one-way hashes of phone numbers — useful for matching but not reversible. The UI never shows the raw digits back, so a brand user can't re-export a list they uploaded earlier.

Today there is exactly one in-app path that adds someone to the suppression list: replying STOP to an RCS or SMS message from your brand. That reply is captured by RCSync's inbound webhook and the recipient is added to your brand's suppression list. Every future campaign from that brand will then suppress them automatically.