Campaigns

Message content

Pick a template when you create a campaign. Each template constrains what the editor shows, what fits on screen, and what falls back to SMS.

Campaign wizard
The wizard layout is the same for every template — the editor changes shape, the phone preview reflects it live.

Choosing a template

The template picker appears once, when you create a new campaign. It sets the structure of the message you can edit and the preview RCSync shows.

TemplateWhen to use itNotes
TextPlain copy with optional quick-reply chips.Quickest path. Falls back cleanly to SMS.
FileMedia-forward send: a single image, video, or document.Pair with a short caption. Falls back to SMS with a link.
Rich CardSingle card with hero image, headline, body, and call-to-action buttons.The most flexible single-message template.
CarouselMultiple swipeable cards in one message.Great when one message has several distinct items the recipient should browse.
EmptyBlank editor; build the message from scratch.Useful when you're copying content from a spec.

What the phone preview tells you

  • The preview is a close representation of how RCS-capable handsets will render your message, not an exact one — actual rendering varies by device, OS version, and messaging app. Always send a test to a real device before activating to see the real thing.
  • Buttons that look truncated in the preview are likely to be truncated on at least some devices. Treat the preview as an early warning and shorten them.
  • The preview doesn't simulate SMS fallback. To see what your SMS recipients get, use Send Test.

Buttons, quick replies, and chips

Quick replies

Buttons that send a postback when the recipient taps them. The recipient's reply shows up under Reply options on the campaign detail page, grouped by which chip they tapped. Use this for lightweight surveys, lead routing, or filtering downstream campaigns.

URL buttons

Open a URL in the recipient's browser. Use full URLs that include the scheme (https://) — some devices won't recognize a scheme-less value as a clickable link. Prefer your own short domain if you want clean analytics.

Dial buttons

Dial a phone number. Include the country code (e.g. +15555550123) so the dialer works the same way on every device, regardless of where the recipient is. Numbers can be up to 16 characters.

Personalization

Drop a replacement anywhere you want a per-recipient value by wrapping a field name in double braces — {{first_name}}, {{offer_code}}, {{store_name}}. The Text editor has quick-insert chips for the common ones; in every other field you just type the replacement.

Replacements work in card buttons too

Replacements aren't limited to the message body. You can use them in any card or button field — button label, postback data, link URL, dial number, location label, and a calendar event's title, description, and times. For example, a button that links to {{offer_url}} or a calendar invite whose start time is {{appt_start}} resolves differently for each recipient.

  • For a button's Start time or End time, use the Use a replacement instead toggle to type a token in place of picking a fixed date.
  • Length limits (like the 25-character button label) and format checks (like requiring a full URL) are relaxed while a field holds a replacement, because the final value is what counts — so keep the resolved value within the same limits.
  • Latitude and longitude accept a replacement, but the value you provide must be a plain number for the map pin to land correctly.

Import from JSON

Already have a message in Messages API format? On an RCS campaign message — or an RCS follow-up step in the interactive builder — use Import JSON and paste the payload. RCSync fills out the editor from it: text, rich cards, carousels, media, and reply buttons all come across, ready to tweak and save.

  • Accepts a full { "messages": [...] } payload, a single message, or a bare content object.
  • For a campaign, each message becomes one of your messages (up to 10); for a follow-up step, the first message is used.
  • Importing replaces the current content for that message. The sender and recipients in the JSON are ignored — your campaign's own sender and audience always apply.

Media uploads

For rich cards and files, you can either upload directly in the wizard or pick from your Asset library. Uploads in the wizard are added to the library too, so reuse is automatic.