Aura Offers

Every other campaign type answers “send this to these people at this time”. Aura Offers answers a different question: given everything known about one customer, what is the best thing to send them next, and when? You supply the options; the picker makes the choice, one customer at a time, continuously.

That means three of the things you'd normally set aren't there: no audience list, no send time, and no single message. What you set instead are the offers, the rules about how often a customer may be contacted, and when the whole thing should stop.

Two routes, both landing in the same builder:

• New campaign → Build Aura Offers campaign — start from an empty catalog and write the offers yourself.
• Draft with Aura — describe an always-on programme in your own words (“keep sending each customer our best offer”) and the assistant recognizes the shape and builds the catalog, including the message for each offer. It deliberately leaves coupons and store settings blank, because those are integration facts rather than creative choices.

The catalog is the heart of it. Each offer is a card in a horizontal strip — add as many as you want, and scroll between them. An offer has four parts:

• Name — how you refer to it. Each offer also gets a short id shown beside the name; that id is what shows up in reporting.
• Description — what the offer actually is, in plain language (“free bagel with any coffee purchase, 7-day expiry”). The picker reads this. It's not an internal note.
• Best for — who the offer suits (“morning regulars who buy coffee but rarely food”). This is your targeting instruction, written as a sentence rather than a filter.
• Message — the RCS message sent when this offer is chosen, built in the normal message designer with a live phone preview.

Tick This offer has a single-use coupon to attach real, redeemable codes. Codes are drawn from a pool in your point-of-sale system rather than generated by RCSync, so a redemption in-store is the same event your POS already understands.

• Parent coupon id — the coupon in your POS that codes are drawn from.
• Store — optional. Set it to restrict the offer to customers whose preferred store matches.

At send time, one code is reserved, assigned to that customer, and delivered as a personalized deep link. Place the link with the {{offer_link}} replacement anywhere in the message — body text or a button URL. The code itself is {{offer_code}} and its expiry is {{offer_expires}}. See Message content → Personalization for the full token list.

These are the guardrails on how often the campaign may act. They're the main thing standing between “always on” and “too much”.

• Message cool-down — the minimum gap between two sends to the same customer, in days and hours. A customer inside their cool-down is skipped entirely.
• Reconsider each customer every — how often the picker re-evaluates a customer, in minutes (15 minimum). This is the thinking cadence, not the sending cadence: reconsidering often doesn't mean messaging often, because the cool-down still applies.
• End date — optional. Leave it blank and the campaign runs until you pause or cancel it.

There's no Audience tab. The campaign draws on your brand's contacts — the customer records synced from your point-of-sale, plus anyone who opts in through your opt-in flow while it's running. A brand-new opt-in gets a first offer straight away rather than waiting for the next pass, since there's no history to predict from yet.

On each pass, a customer is skipped if they already have a send pending, are inside their cool-down, are at the frequency cap, or if no offer in the catalog is eligible for them. Everyone else gets a decision.

For each customer who is due, Aura weighs three things:

• What's known about them — their history with your brand: what they've bought, what they've engaged with, when they tend to respond.
• What the offers say — the description and “best for” you wrote, for the offers currently eligible.
• What has worked — how each offer has actually performed across your customers so far.

It returns one offer and one send time. The send time is why a customer who reliably opens messages in the evening gets theirs in the evening, without you building a segment for it.

Once activated the campaign sits in active and stays there — there's no per-run completion to wait for. Pause it to stop new decisions; cancel it to stop permanently. If you set an end date, it completes itself when that passes.

Cost accrues rather than being estimated up front, because there's no fixed audience to multiply. Two things draw Aura credits: the messages themselves, priced exactly like any other campaign, and each offer decision, which is a model call. The campaign page shows the decision spend per delivered message so you can see what the picking is costing relative to the sending.