RCSync DocsPowered by Whisp
Sign in

Campaigns

Campaign types

RCSync supports four campaign types. The type is chosen on the Delivery settings tab and changes what timing controls you see.

Channel: RCS or SMS

Separate from the type, every campaign has a channel — RCS or SMS — chosen with the toggle in the Design section. It's 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.

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; usually a JSON object with a phone number and any merge fields your message uses.

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 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.

Switching types

You can change the type 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.