When a buyer lands on Devotel Orbit looking for customer-loyalty orchestration or referral-driven SMS, the answer is not one page or one feature. It is a family of outbound capabilities — campaigns, journeys, incentives, referrals, loyalty, and wallet passes — each one shipped and each one pulling a different lever on the same outbound pipe. This post is a guided tour through the seven routes that make up the outbound surface, what each one is for, one capability detail worth knowing, and how they compose into a single orchestration surface so you don't have to pick one in isolation.
All routes live under Outbound in the dashboard. Everything named below is shipped and live today.
What we shipped: the capability routes
Campaigns (/outbound/campaigns)
Buyer value: The umbrella surface for outbound messaging work — audiences, goals, templates, direct-send, and voice broadcasts.
Capability detail: Campaigns is where one-off and recurring outbound sends are created and managed. It is the entry point for most outbound work and the route that stitches the specialised capabilities below into a send.
Journey (/outbound/campaigns/journey)
Buyer value: Multi-step campaign flow — a campaign that branches, waits, and reacts rather than single-shot firing.
Capability detail: Journeys let you sequence steps inside a campaign, so an outbound send isn't a flat one-shot. Each step can be conditionally sequenced, letting a single campaign handle a series instead of just a burst.
Incentives (/outbound/incentives)
Buyer value: The reward catalogue — discounts, codes, credits — that other outbound capabilities hand out.
Capability detail: Incentives is the incentive register. Define the reward once here so that loyalty and referral flows can both draw from the same incentive pool.
Referrals (/outbound/referrals)
Buyer value: Referral-program surface — member-get-member flows with a link and a tracked reward.
Capability detail: Referral programs generate tracked links that customers share, and the reward on success is drawn from the incentives register. Wallet passes carry the voucher to the referee.
Loyalty (/outbound/loyalty)
Buyer value: Points-and-rewards loyalty programme surface — accrual, tiers, and redemption.
Capability detail: Loyalty programmes accrue points against activity and redeem against the incentives register. Like referrals, it draws rewards from the same incentive pool so the economics stay in one place.
Wallet passes (/outbound/wallet-passes)
Buyer value: Digital wallet pass delivery — coupons, vouchers, and membership cards delivered to a customer's phone.
Capability detail: Wallet passes are how a voucher physically reaches the recipient. Referrals use them to deliver the reward to a referee; loyalty uses them to carry the membership or coupon to the member.
AI (/outbound/ai)
Buyer value: AI-assisted outbound — generated variant content and naming for campaign work.
Capability detail: The AI route is where outbound content variants are generated and named, so campaign authors can draft multiple content versions before sending.
How they compose
The capabilities are not alternatives — they stack.
- Referrals use wallet passes: when a referral succeeds, the reward voucher is delivered to the referee through a wallet pass, so the referee gets something they can keep on their phone, not just a code in an SMS.
- Loyalty and referrals both draw from incentives: the incentive register is the shared reward pool, so a program doesn't invent its own discounting logic and the unit economics live in one place.
- Campaigns stitch them: a campaign is how the specialised pieces actually fire. Loyalty or referral programs define the rules; a campaign sends them. Journeys extend a campaign when a one-shot send isn't enough.
Workthrough: a referral reward from trigger to delivery
An annotated flow that uses the capabilities above together — a new referral signup carrying a reward from the incentives register to the recipient's phone.
1. Trigger: a referral event. A referee signs up through a tracked referral link, and the referral program (/outbound/referrals) matches the reward rule you defined. The reward itself comes from your incentives register (/outbound/incentives) — a discount code, a credit, a voucher — not from any ad-hoc value invented per send.
2. Channel pick with a fallback chain. Fallback is an org-level routing posture, not something you set per campaign. Under Settings → Channels → Cross-Channel Fallback you define the order the router tries per recipient, for example RCS → SMS or RCS → WhatsApp → SMS. At send time the router evaluates the recipient's capability (a cached verdict, or a live provider probe on a miss), and unsupported recipients downgrade cleanly to the next chain channel. If the chain falls through to a different channel, consent for that channel is re-checked before anything is sent. The full configuration walkthrough is in the RCS-to-SMS fallback strategy guide.
3. Template the message once. Author the rich version for RCS — a greeting, the reward detail, a link or wallet-pass drop — and a plain-text version that carries all the meaning when the recipient can't render cards. The plain-text variant is what reaches recipients who downgrade. For the delivery object itself, wallet passes (/outbound/wallet-passes) put the voucher on the referee's phone as something they keep, not a code buried in a text.
4. Firing the send. One-off welcome bursts against an audience run as a batch send — the API's batch endpoint (POST /messages/batch) accepts one message template rendered against up to 10,000 recipients with per-recipient personalization variables, and returns a per-recipient outcome map so rejected rows are visible instead of silently dropped. The dashboard's batch review step shows a cost breakdown (per destination-country rates, per-recipient math) before you commit the send. When the flow needs to branch or wait — say, remind the referee about an unredeemed voucher a week later — it runs as a journey (/outbound/campaigns/journey) rather than a one-shot campaign, with each step conditionally sequenced.
5. Delivery webhooks close the loop. The batch response tells you the send was accepted; the delivery webhook stream tells you what actually happened per message — accepted, delivered, failed, or the reason a recipient was suppressed. Feed those receipts into your analytics reads so a fallback downgrade or a suppressed recipient shows up as an event, and your referral-advantage funnel reports on real delivery rather than on sends that were merely accepted.
Compliance posture: program-level, tenant-owned
For outbound messaging the regulatory posture belongs to the tenant, not to the platform. Orbit provides the control surface for consent, opt-out keywords, do-not-contact lists, and quiet hours; your organization sets the actual policy for its programs and jurisdictions. The one carve-out is the US federal TCPA voice dialing window, which the platform enforces globally with no opt-out path — that carve-out is exactly as narrow as it sounds and does not extend to messaging.
What that means in practice for a loyalty/referral send:
- Consent capture is yours. Collect and document consent in your signup and program terms. The platform will check do-not-contact state before each send, but the proof of consent originates in your onboarding flow.
- Opt-out handling is configurable. STOP keywords, quiet-hours windows, and consent windows are per-channel settings under your organization's compliance configuration — set them for the jurisdictions you send to, and the router re-checks them when a fallback chain downgrades to another channel.
- Do not claim the platform forces compliance. Orbit exposes the controls; the legal posture is the tenant's. The postures you set apply uniformly across campaigns, journeys, and ad-hoc batch sends because they live at the organization level.
Measuring ROI
The measurement surface for this lives under Insights → ROI attribution and Insights → Anomalies. The ROI surface attributes revenue and outcome back to the campaign, flow, or program that produced it, so a referral program's lift is readable as a number rather than inferred. The anomalies ledger watches for deviations — delivery-rate drops, suppression spikes, fallback downgrades that skew toward one channel — and turns them into a sorted signal list. Read both per program: a loyalty tier's reward cost against the redemption lift it drives, or a referral cohort's voucher deliverability against the fallback chain that routed it.
Loyalty/referral vs a generic promotional blast
Pick the narrow case honestly: a referral program rewards a member-get-member loop with a tracked link; a loyalty program accrues and redeems points against a shared incentive pool. Both are structured programs — not the right shape for a generic promotional blast to a broad audience. The blast case is a campaign, one-off or recurring, sent against an audience segment. Use the program when you want a tracked, reward-backed loop; use the campaign when you want reach without a program's reward economics attached.
Reading the platform surface
Orbit's platform coverage is broad, and outbound is one pillar. The articles that compare platform approaches (alternatives platforms to consider in 2026 and enterprise messaging-and-voice infrastructure alternatives) position the choice a buyer faces; this post is the capability map for the outbound pillar those alternatives articles land on. If you are weighing consolidated-vs-assembled, the outbound surface above is what consolidation looks like in practice.
Get started with outbound
The fastest way to see the surface is the dashboard: open Outbound and the routes above are the first-level navigation. For an end-to-end walkthrough, the outbound getting-started guide in the docs at docs.orbit.devotel.io covers the outbound surface from first principles.
Frequently asked questions
Is outbound one feature or a family? A family. Campaigns is the umbrella, and the specialised capabilities — referrals, loyalty, incentives, wallet passes, journeys, AI — each do one thing well. They are not competing alternatives; they compose.
Where do the rewards live? In the incentives register (/outbound/incentives). Loyalty and referral programs both draw from it, so the reward economics stay centralised.
How is a voucher actually delivered to a customer? Through wallet passes (/outbound/wallet-passes) — a digital pass on the customer's phone, which is what makes a referral reward or loyalty membership tangible rather than an SMS code.
Can a campaign do more than a single send? Yes. The journey route (/outbound/campaigns/journey) lets a campaign sequence steps instead of firing once.
Does this replace the alternatives articles? No. The platform-alternatives articles cover the consolidated-vs-assembled choice. This post covers what consolidation looks like once you pick it.
---
All routes and capabilities named above are shipped in the Devotel Orbit dashboard under Outbound. Everything referenced is live today.