Skip to content
ModulesPut a person in the middle
Back to Workflows

Put a person in the middle

The step that makes automation safe to turn on.

You want the reminder sent, the fee posted or the refund issued, but not without someone seeing it first.

1

Hold for approval

The run stops. It lands in the approvals queue and on a manager's phone with the context attached.

2

Two paths from there

Approved carries on down one path, declined takes the other, and nobody sitting on it means the timed out path after your window.

3

It shows up afterwards

The history says who decided, when, and what happened next, so the next person is not guessing.

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.

What that saves you

  • Automation you can hand to staff
  • No silent money movement
  • An audit trail without a spreadsheet

Want to see this with your own park?