The 48-Hour Rule: Building a Lead Response Process That Doesn't Lose Bookings
The TravelIQ team · 8 min read · Updated August 2026
Why response time predicts conversion
A trip inquiry is a perishable asset, and every hour of silence deducts from it — not because the traveler is impatient, but because of what the silence period contains: the other agencies they also contacted, the supplier's own website with its chat widget, the creeping do-it-myself option, and the ordinary cooling of an enthusiasm that peaked the moment they hit submit. The first credible, human response doesn't just answer the inquiry; it converts an open search into a working relationship, and every later responder is competing against that relationship instead of against silence.
Owners who start timestamping their leads — when it arrived, when a human first replied, whether it booked — invariably find the same lopsided pattern: the bookings cluster overwhelmingly among the fast responses, and past a couple of days the reply is functionally a courtesy. The exact curve doesn't matter and will differ by niche. What matters is the operational conclusion: response time is a conversion lever you control completely, which makes it the cheapest one you own. Improving it requires no ad spend and no new leads — just process, which is what the rest of this playbook is.
Setting an SLA your team can actually hit
An SLA fails in one of two directions. Too loose, and it blesses the problem — a 72-hour target formalizes the very silence that loses bookings. Too aggressive, and it becomes fiction: the two-hour promise that's missed nightly breeds the learned habit of ignoring the number entirely, which is worse than never having set one. The correct target is the tightest window your roster can keep on its worst normal week — short-staffed, wave season — not its best.
Two definitional choices make or break it. First, count business hours, not wall-clock hours: a lead arriving Saturday at 11pm should not consume its window while the team sleeps, or your SLA punishes people for closing on weekends. When we built the clock into TravelIQ we made it 24 business hours, counted Monday to Friday, 9am to 9pm Central — the honest version of "we respond within two business days," enforceable without asking anyone to answer at 2am. Second, define what stops the clock: a real, substantive reply from the owning advisor. An autoresponder doesn't count. "Got it, will look tomorrow" doesn't count. The traveler can tell the difference, so the SLA must too.
What “assigned” should mean
Every lost lead has the same epitaph: everyone thought someone else had it. "Assigned" is the word that's supposed to prevent this, and in most agencies it's been diluted to mean "visible to" — the lead is in the shared inbox, the group chat saw it, therefore it's handled. Visibility is not ownership. A lead five people can see and no one must answer is exactly as owned as a lead nobody saw.
Give the word teeth: assigned means one named advisor owns this lead's clock, they know it, and everyone else can see it. One owner — never a pair, because shared ownership is diffusion with a paper trail. Named — a rule like round-robin or specialty can pick the name, but a name comes out. Aware — assignment the advisor hasn't seen hasn't happened; the handoff completes when they have it, not when it was sent. And visible — the roster can see who owns what, so an unowned lead looks wrong to every person who glances at the board, instead of looking like someone else's problem. Reassignment then needs the same explicitness: advisor unavailable, lead moves, new owner named, clock honest about the time already burned.
Catching leads before they slip
An SLA that's only checked after it's missed is a grading system, not a process — the report card arrives after the booking is already lost. The operational version needs states, and three are enough: on track, due soon, overdue. "Due soon" is the one that earns the money, because it's the only state where intervention still changes the outcome: the owning advisor gets a nudge while the window is open, and the reply that would have been three hours late goes out on time instead.
Two habits make the states matter. The board has to be somewhere someone actually looks — a pipeline view opened every morning, not a report requested monthly; a state nobody sees is a state that doesn't exist. And overdue has to trigger a human decision rather than a shrug: the owner or ops lead sees today's overdue leads and acts — a call to the advisor, a reassignment to someone who can reply now. That escalation being a person's job, written down, is the difference between a process and a dashboard. The goal isn't punishing the advisor who slipped; it's rescuing the lead while it's still warm, and the two get confused in agencies that discover their leads in the autopsy.
Measuring it after the fact
The live board keeps this week honest; the retrospective numbers improve next quarter. Three are worth the effort. Median time-to-first-contact, tracked over time — the honest center of your response reality, which a couple of heroic instant replies can't flatter the way an average can. SLA hit rate — of the leads that arrived this month, what share got a real reply inside the window. And conversion by response speed — your own leads, bucketed by how fast the first reply went out, booked or not. That last one turns the whole argument from an industry claim into your agency's own arithmetic, which is the version that survives a staff meeting.
Read the numbers as diagnosis, not judgment. A miss rate concentrated on weekends is a coverage gap; concentrated on one advisor, a workload or fit conversation; spread evenly, the SLA itself is set wrong for the roster you actually have — tighten the process or loosen the promise, but don't let the number and the reality disagree for long. And when the numbers are good, say so out loud. A team that hears "we answered 95% of leads on time this month" learns that the clock is real, that someone reads it, and that being fast is part of what this agency is — which is the culture the whole playbook was ever trying to build.