Say it once, and stop doing it yourself.
An agreement unsigned for two days, a balance still owing on arrival morning, an order sitting unclaimed at the window. You already know what should happen next.
Run history
Nothing has run yet. A test run walks every step for real and sends nothing.
Press test run and watch it walk the steps.
modules that can start a run
messages a day to a guest, at most
approval step anywhere you want one
runs live until you activate them
Automation you can hand to your staff.
The reason most park software automation stays switched off is that nobody can see what it did.
A ladder, built as a run.
An orphan night, a delinquent unit, an ending long stay. Each is a sequence of offers with waits between them, and each step can stop and ask somebody before it goes further.
One offer at a time, with a floor under it. Nothing escalates because a timer fired and nobody was watching.
See the guardrailsStart the ladder and watch it work the empty night.
You see exactly what it sent.
Every run says which rule was true, who approved it, what went out, what was skipped and why. The next person reading it does not have to reconstruct the reasoning.
A test run walks every step for real and sends nothing, so you find the noisy version before your guests do.
See a run tested firstTap a quick reply to answer without typing.
Forty departures at eleven.
The Saturday that turns a well meant automation into a mailing list, and what stops it.
An agreement unsigned 48 hours after it went out. Nothing has to be noticed by a person first.
Only stays over three nights, because chasing a two night booking is not worth the message.
The run waits, they decide from their phone, and it takes the path they chose.
Rolled up into a digest rather than forty separate messages to forty people.
Never more than two a day to the same person, and texts held until quiet hours end.
A retry cannot double send or double charge, because a run will not fire twice on one record for one event.
Twenty two pieces you can assemble yourself.
Not a fixed list of automations we picked for you.
22 things listed right there. Ask about any of them and we will show you it working on your own park, not on a slide.
Everything starts as a draft. A test run walks every step for real and sends nothing, so you see what it would have done before anyone hears from it.
Put a manager in the middle of any run. It waits, they decide on their phone, and the run takes the path they chose.
Every run says which rule was true, who approved it, what went out and what was skipped, so the next person understands what happened.
What you get.
Triggers from every module
A booking, a checkout, an unsigned agreement, an orphan night, a failed autopay, an order sitting unclaimed, or simply a time of day.
Rules in plain words
Only run when the stay is over three nights, the balance is over fifty dollars, or the site is a cabin. Leave it empty to run on every one.
Split the path
Approved goes one way, declined goes another, and a run nobody answers takes the timed out path after the window you set.
Guardrails that keep it sane
Never send the same guest more than two messages a day, hold texts until quiet hours end, and never run twice on the same record for the same event.
How operators actually use it.
Short walkthroughs of a real situation, start to finish.
Questions operators ask.
What happens when I edit one that is already live?
Edits go into a new version. Runs already going finish on the version they started under, so nothing changes shape halfway through.
Could it send forty texts by mistake?
Forty triggers become forty runs unless you roll them up, so the limits sit on the same page. Cap messages per guest per day, hold anything that would land in quiet hours, and never run twice on the same record for the same event.
Do I have to build them from scratch?
No. The ones your team already does by hand are there as starting points, and every one is yours to change before you turn it on.