A follow-up leak is not always a speed problem. It is a visibility problem. Your property management system receives an inquiry at 2:47 PM. Your sales person checks email at 9:15 AM the next day. The inquiry has cooled. The conversion rate has dropped from what it could be. But the real leak is not that someone was asleep—it is that no one knew the inquiry had arrived. Most STR operators stack tools without connecting them: Airbnb sends to email, Vrbo sends to a different email, Booking.com bounces into a channel manager, and the channel manager syncs to a PMS that nobody checks. By the time a human logs in to any system, the inquiry is already aging out of the conversion window. The operator then blames the sales person. The sales person blames the tool. Nobody names the system leak. ## The Follow-Up Leak Is an Attention Leak A follow-up leak begins before any response is sent. It begins when an inquiry lands and no system raises its hand. In a properly wired operation, an inquiry arrives and immediately creates a task, a notification, or a state change that someone actually sees. In a broken operation, the inquiry sits in whichever silo it landed in until someone manually checks that silo. The time cost is enormous; the conversion cost is silent. The first patch is visibility. You need to know, in real time, when an inquiry has arrived. This does not require ripping out your Airbnb integration or replacing your PMS. It requires a single rule: every incoming inquiry must trigger a notification to the person whose job it is to respond. Text message, Slack, email—the medium matters less than the immediacy. If that person is you, the operator, then you need to know within 60 seconds. If that person is a VA or a sales agent, they need to know before they check their personal email. ## Attribution Without Ownership Is a Future Problem Once you patch the attention leak, a second leak surfaces: you cannot see which responses convert and which do not. Your Airbnb inquiry converts to a booking. Your Vrbo inquiry converts to a booking. Your Booking.com inquiry becomes a no-show. But you have no field in your PMS that tags which inquiry source produced which guest. The inquiry vanishes into the booking record. When you analyze this month's revenue, you have no way to know whether your Airbnb response time is better than your Booking.com response time, or whether one source genuinely has a higher conversion rate than another. Patch this by adding a source tag to every booking created from an OTA inquiry. The tag should be captured at the moment the inquiry is logged, not retroactively. Most PMS platforms allow custom fields; most channel managers log the source. The patch is a rule: before a booking is created, its source must be recorded in an auditable field. This is not a feature request to your platform vendor—it is a workflow rule you can enforce today, even if it means adding a step to your manual booking process. ## Response Time Is the Lever You Can Pull Immediately Once attention and attribution are visible, response time becomes measurable and therefore improvable. Field data from dozens of STR operations shows a sharp conversion cliff: inquiries answered inside 5 minutes convert at roughly 21 percent. Inquiries answered between 15 and 60 minutes convert at roughly 12 percent. Inquiries answered after 60 minutes convert at roughly 4 percent. The operator cannot control whether an inquiry arrives at 3 AM. The operator can control whether a notification system wakes someone up or whether a VA is standing by to respond within the conversion window. The immediate patch is to assign follow-up ownership and set a response-time target: 30 minutes from inquiry to first contact. This target is not aspirational—it is a system requirement. If you cannot hit 30 minutes with your current team and tools, you have a capacity leak, not a tool leak. The remedy is either to hire a VA, to shift response ownership to a sales person with fewer duties, or to use an AI agent to send a templated initial response while a human reviews the inquiry for context. The point is: you cannot improve what you do not measure, and you cannot measure what you do not see. ## Patching Without Platform Migration Most operators imagine that a follow-up leak requires switching from their PMS to a new CRM, or from their channel manager to a new one. This is a trap. A follow-up leak often patches with the tools you already own. The patch involves: notification rules (can be configured in most PMS and channel manager platforms), custom fields (available in almost every PMS), and a worksheet or dashboard that shows you response time and source attribution (buildable in a spreadsheet or a no-code tool like Zapier, Make, or Airtable). The patch does not require platform replacement. It requires system visibility. Here is a diagnostic framework for your operation: Can you see, in real time, when an inquiry arrives? Can you tag which source produced which booking? Can you measure the time between inquiry and first response? If the answer to any of these is no, you have a follow-up leak. If the answer to all three is yes, your leak is likely a response-quality problem, not a speed problem, and that is a different repair. Run your operation through the free STR Leak Scorecard to see which of your follow-up systems are actually wired, and which are running on operator memory. The Scorecard will show you whether your leak is attention, attribution, or response time—and what the actual cost is in lost conversions and revenue per month.