Skip to content
ModulesForty triggers, one message
Back to Workflows

Forty triggers, one message

Keeping a busy Saturday from turning into a mailing list.

Forty departures at eleven, and every one of them fires the same run.

1

Roll them up

Forty triggers become forty runs unless you group them, so a digest goes out instead of forty separate messages.

2

Cap the guest

Never more than two messages a day to the same guest, and hold texts until quiet hours end.

Decide a long stay applicationDraft
Approved
Declined
ActionSend the decision noticeApplication declined, with the reason and the adverse action notice where one is required
ActionRelease the holdThe deposit authorization comes off their card and the site reopens
Run history

Nothing has run yet. A test run walks every step for real and sends nothing.

Step 1

Press test run and watch it walk the steps.

3

Never twice for the same thing

A run will not fire twice on the same record for the same event, so a retry cannot double send or double charge.

What that saves you

  • No mass text at 7 am
  • Guests who stay subscribed
  • Limits set once, not remembered nightly

Want to see this with your own park?