Automated client notifications in Brindlechute are sent once per day at 5:00 p.m. Mountain Time (MST or MDT, depending on the season).
This is the send window—the time of day a scheduled notification leaves our system. It is not how often a reminder repeats. You set the cadence separately for each payment reminder.
Which notifications this applies to
The 5:00 p.m. Mountain Time send window applies to scheduled notifications such as:
Remaining balance reminders
Deposit due reminders
Pre-trip reminders
Post-trip reminders
Other scheduled notifications you’ve configured for clients
As long as a notification is scheduled for that date, your client will receive it at 5:00 p.m. Mountain Time.
How often do reminders get sent?
That’s up to you. The send window is fixed, but you set the cadence for every payment reminder—there’s no fixed system schedule.
Click your organization name in the top-left corner, select Notifications, then open the Client tab. Click Edit template on the reminder you want to change:
If a client hasn’t paid their deposit—set how many days apart reminders go out, and how many send in total (Invoice Deposit Payment Reminder). Sends 2 reminders, 2 days apart, unless you change it.
Before a balance is due—set how many days before the due date the reminder sends (Invoice Final Payment Reminder). Sends 2 days before, unless you change it.
If a balance is past due—set how many days apart reminders go out, and how many send in total (Invoice Final Payment Overdue Reminder). Sends 1 reminder, 2 days after the due date, unless you change it.
All three are turned on for every organization by default.
When deposit reminders start
Deposit reminders don’t begin on the due date itself. The first one goes out once your reminder frequency has elapsed after the deposit due date passes. At the default frequency of 2 days apart, that means the first reminder lands 2 days after the due date, and the second 2 days after that.
Resending an invoice restarts the deposit reminders. The sequence counts from whichever came later—the deposit due date, or the last time you sent the invoice. So if you resend an invoice while a deposit is still unpaid, the full reminder sequence starts over from the resend date. Worth keeping in mind if you resend invoices often.
When reminders stop
Once the balance is covered. If a client pays partway through a sequence, the remaining reminders are cancelled—they won’t receive messages for money they’ve already paid.
When the sequence finishes. Because you set a total number of messages, reminders stop on their own rather than continuing indefinitely.
Partial payments don’t stop overdue reminders. If a client pays some but not all of an overdue balance, the remaining reminders continue on their original schedule until the balance is fully paid.
What this means for your operation
Reminders are date-based, not triggered by last-minute edits.
You can plan around a single, predictable send time each day.
If you need to reach a client outside that cadence, you can always send a manual message directly from the trip.
This keeps your client communication consistent and easy to anticipate for both your team and your guests.