Automatic add-ons apply a service to a booking by default, based on the space, booking type, or layout selected, so users don’t have to add it manually every time. Power users can still remove an add-on for a specific booking, and every automatic add-on stays fully visible in Service Reports and the Service Tracker.
Most people treat whatever’s already selected as the recommended choice, even when it’s never labeled that way, according to research from the Nielsen Norman Group. Automatic add-ons put that instinct to work: the system handles the predictable choices so users don’t have to.
Q: What exactly is an automatic add-on?
A: An automatic add-on is a service that gets applied to a booking by default, without the user having to manually select it every time. Think of it this way: if there’s a service that’s essentially always part of a certain kind of booking, why make someone click “add” for it over and over? Automatic add-ons remove that repetitive step entirely, the service is just there, already included, the moment the booking is created.
Q: What kinds of services make sense as automatic add-ons?
A: The best candidates are add-ons that a user would choose anyway, almost every single time. If you find yourself manually adding the same service to nearly every booking of a certain type, that’s a strong signal it should be automated. The goal isn’t to sneak in extra services, it’s to save people from doing something they were going to do regardless.
Want to see automatic add-ons set up for your spaces? Explore Korbyt Space Booking →
Q: What actually triggers the automation? How does the system know when to apply one?
A: Automation can be triggered by a few different elements, depending on how the setup is configured:
- The space itself: certain rooms or locations may always require a given add-on.
- The booking type: some categories of booking naturally call for a specific service every time.
- The layout selected: choosing a particular layout can automatically bring along the add-on that pairs with it.
Any of these can act as the trigger, so the automation can be tailored to whatever combination of conditions makes sense for the use case.
Q: What if a specific booking doesn’t need the add-on? Are all users stuck with it?
A: Not at all. As with many parts of the system, power users retain override capabilities. If an automatic add-on isn’t needed for a particular booking, it can be removed on a case-by-case basis. That’s an important distinction: automation here is meant to speed things up, not lock everyone into a rigid process. The system defaults to the sensible, common-case behavior, but it never takes away the flexibility to make an exception when one is needed.
Q: Once an automatic add-on is applied, how do services teams know it’s there?
A: Because automatic add-ons are identified in the Service Reports and the Service Tracker just like any manually added service, they don’t disappear into the background once they’re applied. Services teams can see exactly what’s needed and where, giving them the same clarity they’d have with a manually selected add-on. So while the automation saves the user a step up front, it doesn’t cost the team any visibility on the back end.
Q: So, what’s the bottom line?
A: Automatic add-ons are about eliminating unnecessary clicks, not removing control. They handle the predictable, “you’d choose this anyway” parts of a booking automatically, based on the space, booking type, or layout, while still leaving the door open for power users to adjust things when a specific booking calls for something different.
Ready to see Korbyt in Action? Talk to an Expert
Catch up on the rest of the series: Streamlining Booking with Korbyt & Outlook
