Campaigns

Audiences

How RCSync handles the list of people you're sending to — including what it drops, what it suppresses, and how it protects recipient data.

Adding an audience

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.

On an email campaign the audience is email addresses instead. An uploaded CSV is scanned for the email column rather than a phone column, and anything that isn't a valid address is dropped the same way.

Campaign types with no audience tab

Open campaigns take their audience per-request from the calling system. See Campaign types → Open.
Aura Offers campaigns send to your synced contacts, and the picker decides who is due. See Aura Offers.

What happens to the list before send

Deduplication — duplicate phone numbers (or email addresses) within the list are merged into one recipient.
Validation — anything that doesn't parse as a phone number, or as an email address on an email campaign, is dropped.
Suppression — recipients on your brand's suppression list are removed. See how a recipient lands on it below.

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 caps are tracked separately (see Governance & compliance) and are not yet reflected in the preview.

How RCSync stores phone numbers and addresses

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

How someone lands on the suppression list

Suppression is per brand, not per campaign — once someone is on the list, every future campaign from that brand suppresses them automatically. Four things put them there, all of them automatic:

Replying STOP to an RCS or SMS message from your brand. The reply is captured by RCSync's inbound webhook and the number is suppressed.
Clicking unsubscribe in one of your emails. The one-click unsubscribe in the email footer suppresses that address.
A hard bounce — the address doesn't exist or permanently rejected the mail. Continuing to send to it damages your sending reputation, so it's suppressed on the first hard bounce.
A spam complaint — the recipient marked one of your emails as junk.

Each record keeps why it was suppressed, so you can tell a deliberate opt-out from a dead address. You can see and export the whole list from the Consent page.

Changes outside the in-app flow

There is no UI today for adding or removing individual recipients manually. Anything beyond the automatic paths above — bulk imports of previously-collected opt-outs, re-adding someone after documented re-consent, audited removals for a support escalation — runs as an operator-side database task. Open a ticket with your RCSync admin and they'll work it from the operator side.