Automate email and SMS with Flows

Build trigger-based follow-up journeys for eligible promotion and form activity.

Start with a supported event

Open Post-Entry → Flows. Flows are available for standard promotions and Forms, but not Purchase Sweepstakes. Choose the event that should start your follow-up:

Form Submitted or Form Abandoned for completed or unfinished entries.
Referral Completed or Payment Completed for those specific activities.
Winner Drawn for a selected winner.
Contest Vote Cast or Contest Submission Reviewed for contest activity.
Instant Win Won or Instant Win Lost for game outcomes.

Use events appropriate to the promotion type. An abandoned form needs enough contact information to send a message; starting a form does not guarantee Revup knows how to reach that visitor.

Where Send frequency is available, choose Every time, Once per person, or Once per day per person as appropriate. Vote triggers use voter-based limits and default to once per voter. The non-winning Instant Win trigger defaults to once per day per person. Frequency limits do not grant permission to send marketing.

Build the follow-up

Connect steps in the order they should run:

Step	Purpose
Send Message	Send Email, SMS, or Email + SMS using the available sender and template controls.
Send Webhook	Notify your receiving system using POST (default) or PUT. This is separate from a promotion's Webhook integration.
Update Winner Status	Change the available winner lifecycle status in a winner-related flow.
Wait Duration	Pause for the selected interval; the initial setting is one hour.
Wait Until Date	Wait for a specific date or a promotion start/end date with an optional day offset.
Wait Until Event	Wait for the supported promotion-ending or winner-drawing event.

Available conditions check winner status, claim-form submission, total entries, referral count, payment status, or moderation decision. Follow both branches when reviewing a condition. The editor does not currently offer arbitrary form-field conditions, random splits, manual enrollment, tag/list actions, or direct bonus-entry awards.

Prepare messages and test

Email needs an available account sender. Choose From and Reply-To, then review the subject, preheader, message body, and merge tags. Standard email content and Custom HTML have different editing controls. Colors and templates affect presentation, not eligibility to send. SMS uses available templates and variable mappings; confirm that the intended phone number and permission are present.

Test with dedicated staging contacts before activating. Check the exact triggering event, repeated events, waits, each condition branch, missing contact details, and rendered merge values. Review the destination and delivery history. Changing a flow is not proof that people already in a waiting step will receive the new intended journey; validate the affected path before using it for a deadline-sensitive claim or message.