Brindlechute gives outfitters two ways to manage client communication. Notification Settings control communication defaults for the whole organization, while Communication Settings inside a booking let staff make changes for one trip only.
Booking-level Communication Settings are best used when a single booking needs an exception. Instead of changing notification behavior for every client, staff can turn off specific communications just for that one booking.
When to use booking-level Communication Settings
Use booking-level Communication Settings when a message should not go out for one specific booking, but should still remain on for other bookings.
Common examples include:
the client already received the information another way
a certain message does not apply to that trip
the booking needs special communication handling
staff want to prevent duplicate or unnecessary messages for one client
one booking needs different communication settings without changing the defaults for everyone else
When not to use booking-level Communication Settings
If the goal is to change how notifications work for all bookings across the organization, that should be done in Notification Settings instead.
Booking-level Communication Settings are meant for one-off changes, not for setting the default communication behavior for the business.
Why this matters
Using booking-level Communication Settings helps keep communication flexible without affecting everyone else. It makes it easy to handle special cases while keeping normal notification settings in place for the rest of the organization.
Booking-level Communication Settings are a simple way to manage exceptions. When one trip needs different communication handling, this feature gives staff control without changing the default setup for every booking.