Campaigns

Campaign types

RCSync supports five campaign types. Four are chosen on the Delivery settings tab and change what timing controls you see; the fifth, Aura Offers, has its own builder.

Channel: RCS, SMS, or Email

Separate from the type, every campaign has a channel. RCS and SMS are chosen with the toggle in the Design section; Email is picked as its own channel group on the New campaign page. The channel is locked once the campaign is activated.

RCS — rich messages: cards, carousels, media, and suggested replies. Sends from an RCS sender.
SMS — a single plain-text message (links can go right in the text). No cards, media, or buttons. Sends from an SMS sender, and is billed per message segment.
Email — a subject, optional preview text, and an HTML body. Sends from an email sender whose sending domain you've authenticated, at a flat per-email rate. Opens, clicks, unsubscribes, and bounces are tracked. See Campaigns overview → Channels.

Switching an in-progress draft to SMS keeps your text but removes any rich content. SMS analytics have no “Opened” stage, since SMS has no read receipts.

Immediate

Sends the campaign once, as soon as you activate it. No timing controls. Use this for time-sensitive messages or for any campaign you want to fire off manually.

Activation button is Send.
State after activation: active, then complete when the run finishes.

Scheduled

Sends the campaign once, at a specific date and time. The send time is interpreted in the timezone shown on the form — not your account timezone — so changing the timezone in the picker shifts the absolute moment of the send.

Activation button is Schedule.
The send time must be in the future at the moment you activate; the system refuses to schedule a send time that has already passed.
The send time must be within 30 days from now.
State after activation: scheduled, then active while it's sending, then complete.

Recurring

Sends the same campaign on a schedule that repeats. Pick how often it repeats (e.g. every 2 weeks) and when it ends. Each run is independent; you can see them all in the campaign's runs table.

Repeats every — combine a number and a unit (Day, Week, or Month). For example, set 2 and Weeks to send every other week.
Ends — choose Never to keep going indefinitely, On date to stop after a chosen date, or After a number of sends to stop after a fixed count.
The first send must be within 30 days from now. Subsequent runs can extend past that.
State stays scheduled between runs and flips to active only while a run is in flight.
With an end date or send count, the campaign automatically reaches complete once the last run finishes. With Never, pause or cancel it when it's done its job.

Open (webhook-triggered)

Doesn't run on a schedule. Instead, it's triggered by an external system posting to a unique webhook URL. Each request sends the campaign to the audience supplied in the request body.

When to use it

Pick “Open” when the audience is dynamic and decided by something outside RCSync. Two common shapes:

A CRM or marketing automation tool fires a webhook when a customer reaches a lifecycle stage (cart abandoned, trial ending, NPS due).
Your Whisp platform calls the webhook right after a customer opts in, so the welcome RCS message lands on their device within seconds of consent.

The webhook URL

Once activated, the campaign's Audience tab shows what you need to share with the calling system:

URL — looks like /api/campaigns/open/<token>. The token is unguessable and tied to this campaign only.
Pre-send secret — optional. When set, the caller must pass it in a header so RCSync can verify the request before sending. Leave it blank if the token in the URL is sufficient protection for your integration; set it (and treat it like a password) for stricter callers.

The campaign also shows the expected request body shape: a JSON object with the recipient and any merge fields your message uses. On an RCS or SMS campaign the recipient is a phone; on an email campaign it's an email. The example payload on the campaign page always shows the right one for that campaign.

Opt-in attestation

The webhook request body accepts an optional trackingId — your external identifier for the contact, typically a customer ID from the system firing the webhook. RCSync treats its presence as the brand attesting that consent exists upstream:

With trackingId — an opt-in is recorded for that phone (or email address) under this sender, with the ID stored as provenance. You can later look the contact up by the same ID on the Consent page.
Without trackingId — the message still sends, but no consent record is written. Use this only when you already track consent elsewhere.

Aura Offers (always-on)

The one type that isn't a send you schedule. Instead of one message to one list, you define a catalog of offers and Aura decides, per customer, which offer to send and when. It runs continuously until you stop it.

Start one from New campaign → Build Aura Offers campaign, or describe an always-on programme to Draft with Aura and it will build the catalog for you.

Its audience is your synced contacts, not an uploaded list — there's no Audience tab.
It has no send time. Message cool-down sets the minimum gap between sends to one customer, and Reconsider each customer every sets how often the picker re-evaluates them.
State after activation: active, and it stays there. Set an optional End date, or pause or cancel it when it's done its job.

It has its own page — see Aura Offers for the catalog, coupons, and how the picker chooses.

Switching types

You can change between Immediate, Scheduled, Recurring, and Open while the campaign is in draft. Once activated, the type is locked. To switch types on an active campaign, duplicate it as a draft and activate the new one.

Aura Offers is not interchangeable with the other four — it's a different shape of campaign with its own builder. To move between them, create a new campaign.