Triggering Campaigns on Customer, Business, and World Moments
The most effective campaigns reach customers at the right moment: not just on a schedule, but in response to something real. Simon AI helps you define and configure those moments through a conversational interface. Describe the context you want to act on, and the agent translates it into a fully configured trigger, ready to attach to a Journey.
This capability is powered by the Moment Agent.
Types of moments
Simon supports three categories of moment context:
| Moment type | What it captures | Examples |
|---|---|---|
| Customer moments | Behaviors and milestones specific to an individual customer | First purchase, loyalty tier upgrade, cart abandonment, lapsing |
| Business moments | Events driven by your catalog, operations, or commercial calendar | New product launch, inventory change, sale going live, price drop |
| World moments | External conditions that affect purchase intent or relevance | Weather shift, local event, seasonal change |
Most campaigns respond to one type. The most powerful ones combine two or three: for example, a cold-weather alert (world) that fires only for customers who have previously purchased outerwear (customer) when a relevant product goes on sale (business).
Getting started
Navigate to AI Studio > Chats and start a new conversation. Select Moment Agent, or describe the trigger you want to configure and Simon will route moment-related requests to this agent automatically.
You can also access the Moment Agent directly from within a Project by selecting Configure with AI on a Moment node.
Describe the context, not the logicYou don't need to know which events to listen for or how to structure the conditions. Describe what's happening: in the world, in your business, or in a customer's behavior, and the agent figures out the configuration.
Example prompts
- "Trigger when a customer views a product three times in seven days without purchasing" (customer moment)
- "Fire when a customer reaches Gold loyalty status for the first time" (customer moment)
- "Send when a new product drops in a category a customer has purchased from before" (customer + business moment)
- "Trigger when temperatures drop more than 15 degrees in a customer's local market" (world moment)
- "Fire when it's a customer's birthday month and they haven't purchased in the last 60 days" (customer moment)
- "Trigger when a flash sale goes live for a category a customer has browsed but not bought" (business + customer)
What you can do
| Capability | Description |
|---|---|
| Define customer behavior triggers | Describe a customer action or milestone; the agent identifies the relevant events and writes the trigger conditions |
| Configure business event triggers | Connect campaign entry to catalog and operational events: new launches, price changes, inventory signals |
| Set up world context triggers | Use external signals like weather, location, or seasonal data to determine when a campaign becomes relevant |
| Combine trigger conditions | Ask for multi-signal triggers and the agent handles the logic |
| Set frequency and timing rules | Specify how often the moment should fire and any cooldown or recency constraints |
| Configure suppression | Exclude customers who have recently converted, already received the campaign, or don't meet additional criteria |
How to use it
- Navigate to AI Studio > Chats (or open from a Project's Moment node)
- Describe the context you want to act on: a customer behavior, business event, or world condition
- Review the proposed trigger configuration in the results panel: event conditions, timing rules, and suppression logic
- Refine if needed: "Add a 48-hour cooldown" or "Exclude customers who purchased in the last 30 days"
- Confirm to save the Moment to your library and attach it to a Journey
Working inside a Project
When you access the Moment Agent from within a Project, it uses the Project's objective and audience as context. The agent will suggest trigger logic that fits your campaign goal: if your Project targets lapsed buyers, it will favor re-engagement triggers rather than acquisition ones.
Tips
- You can iterate on the trigger definition in the same conversation; the agent maintains context throughout
- If you're unsure which event maps to the behavior you want, describe it in plain English; the agent will map it to the correct event in your data model
- Moments configured here appear in your Moment library and can be reused across Projects
Related
Availability
Moment-triggered campaigns are available to select organizations. Contact your account manager for activation details.
Updated about 4 hours ago