Rheo documentation
User GuideEngage

Rheo Engage

Reach customers by email, webhook, or push after they use your app.

What Engage is for

Rheo Engage sends lifecycle messages to people who already use your app. You write the message in Rheo, choose who should get it, and deliver it on one or more channels:

ChannelWhat goes outWhat you connect
EmailA message to the customer's inboxYour Amazon SES, Resend, Postmark, or SendGrid account
WebhookA JSON POST to an endpoint on that messageNo provider in App settings. The URL lives on the broadcast or automation step
PushA notification on the customer's registered devicesAPNs, Firebase Cloud Messaging, and Web Push keys under Engage settings

Rheo does not send Engage email from Rheo-owned infrastructure. Push uses the credentials you save. A webhook is an HTTP request from Rheo to your URL.

Use Engage when you want to:

  • Announce a launch or win-back offer to everyone who opted in
  • Follow up after an in-app event (for example a trial start or onboarding completion)
  • Call your own backend with a JSON payload, or notify a device, alongside or instead of email
  • Branch people into different paths based on attributes, segments, or what they did next
  • Stay within marketing consent, topics (when enabled), and email deliverability health

This is separate from product email for workspace teammates (Account → Personal) and from email you collect inside an onboarding flow. Engage is outbound messaging to Customers.

Where it lives in the dashboard

Under each app, the Engage sidebar group includes:

PageUse it for
OverviewRecent sends, open and click rates, and deliverability signals. When more than one channel has sends, a By channel chart shows accepted sends
BroadcastsOne-shot campaigns you draft, schedule, or send now
AutomationsBranching workflows that enroll people over time
TemplatesReusable starters for email, webhook, or push — see Templates
Content blocksReusable email fragments (footers, shared CTAs) to insert in the composer — see Content blocks

Open and click rates are email engagement. Webhook and push still count in sent and delivered totals.

Customers → Segments defines audiences for Broadcasts and Automations. App settings → Engage settings covers the email provider, push credentials, frequency cap, quiet hours, marketing topics, and the preference center.

Advanced Engage features (marketing topics, recipient local-time sends, quiet hours, broadcast holdout / A/B, conversion goals) require Grow or above. Indie workspaces see an upgrade prompt (plan_feature_engage_advanced). Base Engage (consent, preference center, frequency cap, broadcasts, and automations without those controls) is available on Indie. See Plans & entitlements.

How the pieces fit

  1. Prepare the channel. Connect and verify an email provider before email (step-by-step for Amazon SES). Save push credentials before push. Put a public https endpoint on each webhook message. See Set up Engage.
  2. Collect consent on each Customer. Email also needs an address. Push also needs a device registration from the SDK.
  3. Optionally build Segments so you target the right people.
  4. Create a Broadcast for a one-time send, or an Automation for a multi-step journey. See Broadcasts and Automations.

Who can receive an Engage message

Rheo sends only when global marketing consent is granted. Denied and unknown do not send.

If marketing topics mode is on, the message's topic must also be granted. Topic checks use the customer's email record, so that person needs an email address as well.

ChannelAlso required before delivery
EmailAn email address that is not suppressed (hard bounce, complaint, or unsubscribe), plus a verified sending identity. The app frequency cap and the test destination allowlist apply to email
WebhookA complete endpoint and JSON object payload. An automation step can send without an email address when topics mode is off. A webhook-only broadcast still uses the email audience, so those recipients have an address and are not suppressed
PushAn active device subscription for this app and environment, and at least one of APNs, FCM, or Web Push connected. The email frequency cap does not apply

Quiet hours can defer any channel until the quiet window ends. They do not drop the send.

Topics mode is off by default. Turn it on under App settings → Engage settings → Marketing consent.

Environments

Engage respects the same test / live environment selector used elsewhere in the app. Use test while you are still wiring providers and reviewing copy.

  • Test-environment email can be limited to the test destination allowlist under Frequency Cap settings.
  • Test-environment push to Apple uses the APNs sandbox.
  • A webhook Send test adds the header X-Rheo-Test: 1. A launched broadcast still POSTs to the endpoint on the message.
  • Set up Engage — Email provider (including Amazon SES), push credentials, consent, preference center, deliverability
  • Broadcasts — One-shot sends on email, webhook, and push
  • Automations — Branching workflows and publish lifecycle
  • Templates — Reusable email, webhook, and push starters
  • Content blocks — Reusable email fragments
  • Customers — Profiles, consent, and segments
  • Apps Settings — Engage settings overview
  • SDK overview — Register push devices from the app
  • CLI — Same Engage actions from the terminal (rheo engage)