The rules in the middle
Fallback chains. Frequency caps. One profile.
A pipe moves messages. A switchboard decides. These rules run on every send on every channel, which is why adding a channel to AuraPost never adds a risk.
Fallback chains
Try WhatsApp. Then SMS. Then email. Stop at the first delivery.
Build a chain from any of the five channels in any order. See a cost estimate before you save it. Afterwards, a report shows which step delivered for each contact, so you know what each channel is really worth to you.
- Any order, any channelWhatsApp, SMS, RCS, email and push, mixed as you like.
- Consent checked per stepA step is skipped, not forced, when the customer has not opted in to that channel.
- One chain per campaign or per API callAttach a chain ID to a send and the switchboard does the rest.
Estimated cost shown before you save. Actual cost in the report.
Guardrails
Never five channels in one evening.
A daily and weekly limit per channel, and one across all channels. The limit wins, not the campaign.
No sends at night unless a message is transactional and you say so.
Email unsubscribe, SMS STOP, WhatsApp opt-in, push permission. Each checked for its own channel before a message leaves.
Bounces, complaints, opt-outs and manual blocks, per channel, honoured on every send including API sends.
Balance, consent, caps and template status all checked in one place. A failed check is reported, never silently dropped.
One hosted page where a customer chooses channels and topics. Changes apply everywhere at once.
One profile
One customer, however they reached you.
An email address, a phone number and a push subscription that belong to the same person are linked into one profile. Caps, consent and history apply to the person, not to the channel.
- Identity linkingAnonymous push subscribers become known customers the moment they log in or fill a form.
- Send logs across channelsEvery message to a person, in order, on one screen. CSV export included.
- Follow-up series, copy tests, team alertsMulti-step journeys across channels, A/B copy, and alerts to your team when something matters.
- One walletTop up once. Per-message pricing on every channel. Usage by channel. Automatic pause when low.
Questions, answered first
Frequently asked questions
What is a fallback chain?
An ordered list of channels for one message, for example WhatsApp, then SMS, then email. AuraPost tries each in turn and stops at the first delivery. You see a cost estimate before you save the chain and a report of which step delivered afterwards.
Can a customer be messaged on every channel at once?
Not unless you want that. Frequency caps apply per channel and across channels, quiet hours block sends at night, and every send checks consent and suppression for that channel first.
What is a follow-up series?
A sequence of messages across channels, such as a welcome on WhatsApp today, an email in three days and a push a week later. You choose what happens when a step cannot be sent: skip it or stop the series.
Is there one bill or one per channel?
One prepaid wallet, per-message pricing on every channel, and a usage page that shows spend by channel. Sending pauses when the balance runs low, so a campaign can never overdraw.
Set the rules once. They follow every channel.
Free to start. Chains and caps are in every account.