Activating the autopilot

Activation is a short wizard under Settings → Engagement Autopilot. It captures everything the autopilot needs to reason about your customers reliably: which lifecycle model fits your business, what your events mean, how much autonomy to grant, and which channels it may use.

Before you start

You need at least one connected channel — the autopilot has to have somewhere to send. If no channels are connected, activation stays disabled until you connect one. It also helps to be sending behavioral events already, since classification is driven entirely by them.

Step 1 — Choose a lifecycle model

Pick the predefined model that best matches your business. Each one defines the lifecycle stages the autopilot assigns and the canonical behaviors it reasons over. See lifecycle classification for the full list of six models (SaaS, E-commerce, Marketplace, Subscription/Media, Fintech/Neobank, On-demand/Delivery) and their stages.

Step 2 — Map your events

The model asks for a handful of canonical behaviors — semantic actions like “signed up”, “activated”, “purchased”, or “added to cart”. For each one, map it to one of your real event names via the type-ahead (backed by your event discovery). For example, you might map the purchased behavior to your own order_completed event.

• Required behaviors must be mapped for the model to classify contacts at all — typically acquisition, the key conversion, and recurring activity.
• Optional behaviors (like a high-intent signal or an explicit cancel event) unlock extra opportunities when mapped, and are skipped when left blank.

Step 3 — Autonomy & guardrails

Choose how far the autopilot goes on its own:

• Review required (default) — it detects and drafts campaigns, then waits for your approval.
• Auto-execute — it activates campaigns automatically within the guardrails you set.

Set the volume caps and audience thresholds that bound its behavior. These are covered in detail in autonomy & guardrails.

Step 4 — Participating channels

Select which of your connected channels the autopilot may send through. Only channels you’ve actually connected are offered, and you must pick at least one. This lets you, for example, let the autopilot use email but not SMS. Your existing frequency caps, quiet hours, and suppressions still apply on top.

Activate

Activating writes your configuration and the workspace joins the autopilot sweep on the next cycle. You can return to this screen any time to remap events, change autonomy, adjust channels, or disable the autopilot — disabling preserves your configuration so you can turn it back on later.

Next steps

• Run a first pass and watch stages populate in lifecycle classification.
• Review what it proposes in the opportunity queue.
• Track results on the performance dashboard.