Action categories
- Interactions: show something to the customer and wait for a response
- Executions: run automatically without requiring customer input
Interactions
Interactions require customer input to proceed. By default, they display a popup prompting the customer to confirm or make a choice. In cancellation (and similar) flows, accepting an offer typically keeps the subscription from the trigger’s default outcome (for example, cancellation). Customers see configurable Accept / Decline (or similar) buttons. Choosing Accept is enough to apply the related effect. In other words, you don’t have to follow anOffer Delay Order interaction with a separate Delay Order execution.
Interactions require the customer to be present in the Customer Portal, so they can only be used with customer-initiated triggers.
Executions
Executions run without waiting for confirmation.Subscription & messaging
Payment failed (dunning)
These actions are only available with the Payment failed trigger.Scheduled order actions
These actions are only available with the Next order updated trigger. They:- Modify the upcoming order — adjust the scheduled order when conditions are met (for example add a gift, apply a discount, or change the date).
- Validate the renewal — approve the order or block it from processing.
Messaging actions (
Send SMS, and similar) are not offered on Next order updated, so customers are not messaged on every order regeneration.