How To Use Technology To Make Great Hospitality Repeatable

Jess Ary, product manager and designer at Flybook, walks through how operators use booking and operations software to create small, personal touches without adding staff time, from returning-guest recognition to a four-question tech stack audit.

Overview Summary

Jess Ary, product manager and designer at Flybook, walks through what she calls the hospitality advantage: using booking and operations software to create small, personal touches without adding staff time. She opens with a passage from Will Guidara’s book Unreasonable Hospitality, about his time at the New York restaurant Tabla, where hosts asked guests where they parked so staff could go feed the meter while they ate. Ary uses that story to draw the line between service (the baseline of getting a guest through a booking) and hospitality (the extra layer that brings them back). Host Peter presses her on the harder question underneath it: how does an owner build a system for hospitality instead of relying on their own instincts, especially once the business has grown past the point where they can greet every guest themselves.

Ary walks through three operator examples from Flybook’s client base to show what these systems look like in practice. A high-volume water park moves 500 guests through check-in in 45 minutes by collecting waivers through a QR code or kiosk before guests reach the counter, and does it with fewer staff than before. A rafting company that used to run its day off shifting spreadsheets now uses live dashboards to decide in real time whether to open more trips or move staff around. An operator that used to photograph a whiteboard and text it to guides now lets staff view schedules, accept or decline trips, and see guest and allergy details from their phones. Ary closes with a four-question audit for any tool in an operator’s stack: does it enable human connection or replace it, does it help capture and use guest information, does it create flow or friction in daily operations, and does it actually save time or just move the work around.

Key Takeaways

  • Hospitality is the layer above service, and it is built from small, planned gestures rather than personality. 6:04 Ary defines service as the baseline of getting a guest through the door and hospitality as what happens above that baseline. Her example is the parking-meter moment from Unreasonable Hospitality, where a restaurant host asked arriving guests where they parked so staff could feed the meter while they ate. The gesture cost almost nothing but created a guest who came back.
  • First impressions start at the booking flow, not at check-in. 7:01 Ary lists the sequence in order: a frictionless booking flow, a confirmation email sent while the guest is still excited, and pre-trip messages that build anticipation and get waivers signed early. She argues these early touches carry through all the way to the review the guest leaves afterward. Skipping ahead to polish the in-person experience while leaving the booking flow clunky wastes the effort put into the visit itself.
  • Six operational patterns signal an owner still buried in the business: manual guide scheduling, spreadsheet patchwork, paper or third-party waivers, phones ringing instead of online bookings, the owner as the only source of truth, and no visibility for staff. 9:17 Ary lists these as the symptoms she sees repeatedly across Flybook’s operator base. Phone bookings in particular can signal that guests do not have enough information on the website to book without calling. The owner-as-bottleneck pattern means every decision has to run up the chain before staff can act.
  • Manual operations are directly costing hospitality time, not just admin time. 10:22 Ary cites a widely used figure that it costs five to seven times more to acquire a new customer than to retain an existing one. She pairs that with an estimate that operators spend four to six hours a week on manual processes. That time comes directly out of the hours that could go toward the guest experience itself.
  • Recognizing returning guests before they say a word is a repeatable system, not a personality trait. 11:17 Ary describes looking up a caller’s number against the guest database so staff can greet them by name and pull up their reservation immediately. The same system surfaces notes such as food allergies or an upcoming birthday so a guide can say “happy birthday, Sally” without being told. These moments read as personal to the guest but run entirely on stored data.
  • One adventure resort layers pre-arrival questions, automated reminders, and guest tags into a single dashboard any staff member can pull up. 12:20 Guests fill out pre-arrival questions covering preferences and flight details before they arrive. Automated reminders follow up with guests ahead of their trip to build anticipation and confirm readiness. Reservation tags flag VIPs and guests with a birthday or anniversary, and any staff member can see all of it on one dashboard when greeting the guest.
  • Scaling without losing the human touch starts with automating the repetitive tasks that steal time, not the guest-facing ones. 13:37 Ary’s starting point is small daily tasks like sending waiver links or routine client messages, moved into the background so nobody has to think about them. The next step is giving guides and staff the schedule, guest information, and trip manifest they need without asking. The goal is to free up staff time specifically for the interactions that Ary says people who work in hospitality actually enjoy.
  • A high-volume water park moved 500 guests through check-in in 45 minutes using fewer staff, not more. 14:58 Guests fill out a waiver from a QR code or kiosk before they reach anyone at the front desk. Staff work from a live waiver dashboard that lets them pull up everyone in a group and create the reservation in one pass. Ary points out this cut headcount without cutting the guest experience.
  • A rafting company replaced spreadsheets and phone calls to management with live dashboards that adjust staffing and trip counts through the day. 16:01 The operator has a high volume of walk-up business, so the shape of the day changes constantly from morning to close. Staff use dashboards and calendars to see how many more guests are arriving and decide on the spot whether to open additional trips or move people around. None of it requires a phone call up the chain.
  • Mobile schedules replaced whiteboard photos for one operator, and it visibly changed how prepared staff showed up. 16:44 The operator used to photograph a whiteboard listing daily trips and staff assignments and text it out, which meant updates never reliably reached people once plans changed. Staff now view schedules from their phones in real time, including any changes made that day. They can also accept or decline trips directly instead of waiting on a photo.
  • Software that does not talk to your other software actively works against the sale. 18:15 Ary’s example: a skier books a ski trip for themselves and a beginner friend, and the confirmation and marketing emails go only to the person who booked. If waiver data from every guest fed the marketing system, the beginner would also get marketed a lesson. Flybook connects to PMS, food and beverage, golf, and other third-party systems specifically to close that kind of gap.
  • Four questions test whether a tool belongs in your stack: does it enable human connection or replace it, does it help you use guest information, does it create flow or friction, and does it actually save time. 19:24 Ary offers this as a closing audit for any reservation system, CRM, point-of-sale, or guest communication platform an operator is running. A “no” or “not sure” answer to any of the four is where she says to start investigating. The audit applies to tools already in place as much as to ones under consideration.
  • The owner is usually the weakest link in a hospitality system, because most owners build systems for staff and for the business but never one that lets them step away. 23:00 Peter frames this from his own operator background: no matter how good an operation is, it has weak points, and the recurring one is the founder. Ary agrees and adds that businesses run and owned by a single person are a different case, but wherever staff exist, listening to the people talking to customers every day produces better systems than routing everything through the owner.
  • If an operator cannot leave the business for two weeks at the height of the season, something in the system is broken. 24:32 Peter states this as a rule he uses with operators, regardless of whether their high season falls in July, August, or the opposite months in the southern hemisphere. The test is not whether the owner wants to leave. It is whether the business keeps running while they do.
  • Phone and chat conversations sell in ways online checkout cannot, and operators who removed that channel lost revenue they never got back online. 26:09 Peter describes testing forced online booking against open communication channels including WhatsApp, Facebook Messenger, and phone at his own tour company. Every guest who booked purely online bought only the trip; every guest who called or messaged first got upsold lunch, a whiskey tour, or missing accommodation, at a rate of roughly 35 to 45 percent of those conversations. Ary agrees there is a real trade-off for operators without the staff capacity to handle high call volume, but the difference for those who can is a deliberate sales channel, not just a service one.
  • Signals buried in scattered feedback can uncover entire unmet segments, but only if someone is set up to notice them. 33:47 Peter’s own example: repeated questions from customers with nowhere to leave their dog led his company to advertise that dogs were welcome in the office, which drove a wave of new bookings from dog owners who had not previously considered the trip. He also points to real-time weather shifts, such as a current heat wave keeping people indoors during peak hours, as a signal that should prompt operators to test early-morning or evening trip times. Ary’s counterpoint is that collecting this kind of feedback is not the hard part. It is building a system to actually rank the signals and act on them instead of letting them sit unused.
  • A structured season debrief, done while the season is still fresh, turns scattered feedback into next season’s plan. 34:26 Flybook runs season debriefs directly with accounts, walking through what came up, what worked, and what did not. Ary acknowledges operators are often drained right at the point when the debrief would be most useful. She recommends doing it anyway, because the insight fades the longer it waits.
  • Slow response times erode guest trust before the trip even starts, and that erosion happens before human-to-human contact has a chance. 40:32 Peter argues that operators already deliver a good in-person experience on the whole, backed by review data that shows tours and activities beating hotels and other sectors on guest satisfaction. The trust problem sits earlier: a guest who has to call three times or message twice before getting a reply has already had their trust damaged. Ary’s fix is a stated internal standard, such as responding to every inquiry within 24 hours, and then building the process needed to actually hit it.
  • Reviews carry more weight now because AI tools are using them to help people decide where to book. 44:00 Ary connects this directly to the pre-trip communication work discussed earlier: setting the right tone early and carrying it through the trip is what earns a guest’s willingness to leave a good review. She recommends asking for the review as soon as possible after the trip ends, by email, text, or both. Peter adds that operators should already be scraping their own reviews and their competitors’ with AI to rank what guests say is working and what is not.
  • An 85 percent guest rebooking rate is the evidence that justifies premium pricing against cheaper competitors. 46:50 Peter cites a Tourpreneur community member running expensive multi-day outbound tours who faced repeated pushback on price. Her answer, that 85 percent of her customers rebook, is the number that makes a higher price defensible. Peter notes the lifetime value compounds further because some of those guests return three, four, or five times.
  • Building a hospitality system does not require an overhaul. It starts with one repetitive task and one honest look at your emails. 48:53 Ary’s closing advice is to start small: identify the repetitive tasks eating time and automate one of them first, and check that existing confirmation and pre-trip emails are actually introducing the brand the way the operator wants. She pairs this with a reminder that the season debrief conversation should happen this year, not get pushed off again.

We’ll transform your business, guaranteed.

Join now, it’s free to start.