Your booking funnel is leaking at three invisible points. Most operators patch one and wonder why velocity doesn't recover. Lead flow breaks are rarely about lead quantity. A 12-unit operator in Playa del Carmen ran 18 months on 2–3 inquiries per day from Airbnb, Vrbo, and Booking.com combined. Assumed the market was soft. Pulled more PPC. Spent 8K on ads. Got 14 more inquiries that month. Didn't convert a single one. The leak wasn't the source. The leak was that inquiries landed in three different places—one Airbnb message, one Vrbo email, one Booking.com webhook into a spreadsheet—with no unified response trigger, no attribution, and a 47-minute average response time. His sales person was awake, but the system was asleep. He rebuilt in six days. Same 3 inquiries per day. 23% conversion vs. 9%. The difference: a single response trigger, one inbox, one source tag, one follow-up sequence, and a 5-minute response protocol. No new leads needed. The leads were already there. The system was just blind to them. Broken lead flow has three structural roots. Identify which one (or all three) is your leak, and you can stabilize within days instead of months. ## The Intake Leak: Inquiries Land in Multiple Disconnected Buckets Airbnb messages sit in Airbnb. Vrbo emails arrive in Gmail. Booking.com webhooks fire into a Zapier zap that logs to a spreadsheet. Or worse: they hit three different people's phones, three different Slack channels, and a CRM that no one checks. The operator thinks: I have a system. I have a CRM. I have automations. What they actually have: three separate inboxes masquerading as one system. Result: inquiries age before they are seen. The first responder is whoever happens to check their phone. Response time drifts. Attribution dies. You cannot tell which channel actually converted the booking. The fix is architectural, not tooling. Every inquiry must land in one place with one source tag attached. That place is usually not your CRM—it is a single, monitored inbox (email, SMS, or dashboard) that your team watches first. Your CRM is the follow-up layer, not the intake layer. Intake belongs to the fastest human reflex, not the smartest platform. Then, tag every incoming inquiry with its source (Airbnb, Vrbo, Booking, organic, referral, etc.) the moment it arrives. You cannot optimize what you cannot measure. ## The Response Leak: Timing Collapse You see the inquiry. You do not answer for 2 hours. Someone else sees the inquiry. Answers at 2:15. Realises the first person already replied. Sends another message. The guest gets two responses and ignores both. Or: you answer in 8 minutes. Great. But your follow-up sequence is manual—a reminder to yourself to send more photos, a reminder to ask about their travel dates. Three days later, the guest has already booked somewhere else. Or: you answer in 15 minutes, but your reply is a generic template that does not reference their specific inquiry. The guest senses the template, assumes they are one of 50 people you are pitching that day, and applies elsewhere. The cost of a broken response layer is lost conversion velocity and lost attribution. You cannot rebuild your booking timeline if you do not know when each step happened. The fix: define a response protocol. First response within 5 minutes if possible, always within 1 hour. One person per inquiry (or a handoff protocol if the first responder is unavailable). Response must reference the guest's stated intent—dates, property type, budget, note—not a generic template. Log the response time and message in your system so you can measure what works. Measure at the channel level, not in aggregate. Booking.com inquiries may convert faster than Airbnb; you need to know that, because it changes your response priority. ## The Follow-Up Leak: Sequence Chaos or Silence Guest inquires. You respond. Guest goes quiet. You wait for them to come back. They never do. Or: guest inquires. You respond. Guest goes quiet. You send a follow-up after 4 days. They have already booked elsewhere. You send a reminder anyway. Then another. Then an apology. Now they have four messages from you and no booking. Or: you have a follow-up sequence. It fires for every inquiry. Half are from guests who already booked. Half are from guests who got cold-listed and lost interest. You burn your credibility chasing dead leads. The leaks here are: no logic between first response and follow-up (you do not know if the guest has booked, gone silent, or is actively deciding), no time-gating (all sequences fire on the same cadence regardless of the guest's state), and no attribution (you do not know which follow-up message actually converted the booking, so you keep replicating the wrong sequence). The fix is a branching follow-up system with state detection. After your first response, the guest either responds or does not. If they respond within 24 hours, they are active—escalate them into a faster sequence (daily contact, flexible payment options, availability confirmation). If they go silent for 48 hours, shift them into a slow sequence (one gentle reminder at 72 hours, then one more at 10 days, then archive). If they message back with specific questions, they are converting—prioritise them. If they ask for a discount three times and go silent, stop. Log which sequence branch actually produced a booking, then replicate that branch. Do not send the same email to everyone. ## Running the System Audit These three leaks are not independent. A broken intake system cascades into broken response timing. Broken response timing cascades into a follow-up system that chases ghosts. All three combined can turn a healthy source (Airbnb, Vrbo) into a ghost channel that you believe is dead when it is actually just unmanaged. To stabilize your lead flow in the next six days, audit each leak: Do all inquiries land in one place with source tags? Does your team have a written response protocol with a time gate? Does your follow-up sequence branch based on guest state, or does it blast everyone the same way? If you answered no to more than one, you have found your stability drain. Fix the intake layer first. The rest will become visible. This is the kind of system audit that the free STR Leak Scorecard is designed to surface. It asks the questions that expose the three structural breaks. Run it, identify which leak is eating your conversion rate, and you will have your repair sequence for the next week.