Simon AI

A segment-triggered Simon journey normally admits contacts who qualify in the future. Existing segment members need the separate backfill option. For a launch announcement to the current audience, the one-time journey option backfills that membership and immediately begins draining, allowing those people to finish while preventing later entrants. This is a different operation from leaving an ongoing welcome journey active.

Set re-entry rules before publishing. A contact may be allowed to enter again while already inside, only after leaving, after a specified waiting period, or never. The documented re-entry setting cannot be changed after launch. Review global entry and exit settings before publication; later structural work uses journey versions.

The base price counts contacts read by the platform, while Simon Mail, Journeys and other add-ons are priced by usage. Connected deployment requires the customer's own Snowflake account; Managed uses Simon's Snowflake infrastructure and can work with another source warehouse. The enterprise pilot is a paid, reduced-scope engagement lasting 90 days.

Before sending, open Review Draft and resolve the validation issues shown at the top of the journey. Select an issue and use Fix issue to reach the affected settings; publication is blocked until these are resolved. An administrator controls staff access through Admin Center, Manage Users, including a View-Only role for colleagues who need to inspect results without editing flows.