Travel advisor calling playbook: call blocks, cadence and KPIs

What this playbook covers

A travel practice lives on three lists that decay at different speeds: inquiries that cool in days, proposals that stall on a price question, and past clients who quietly book direct if nobody calls. This playbook structures the calling week so each list gets its own block, its own opening and its own cadence. It assumes a three-line browser dialer on your own Telnyx numbers, an advisor or coordinator doing the talking, and recordings with after-call AI summaries on every connect.

List hygiene, three lists kept apart

New inquiries: form submissions, webinar attendees, referral introductions. The clock is days. Proposal follow-ups: travelers holding an itinerary. The clock is the pricing question nobody answered. Past clients: travelers who booked before. The clock is the season. Mixing them into one queue is how a repeat client gets a cold opener and a fresh inquiry waits behind a rebooking call.

Your internal DNC list applies to everything, and opt-outs are permanent across every queue. Consent notes travel with the row: where the traveler came from, what they asked, when. A prior inquiry creates an established business relationship, a purchase within 540 days or an inquiry within 90 days, under 16 CFR 310.2; beyond those windows the residential rules apply in full, registry screening included.

The calling week in blocks

Inquiry block, inside the week, three lines. Newest first. The date question comes before destination talk, because firm school dates fix the inventory and flexible dates open value. The budget band is asked as the picture in their head, flights included or separate. The call ends with a deliverable and a dated checkpoint: two real options tomorrow, the walkthrough call Friday.

Proposal follow-up block, two or three times weekly. Travelers holding itineraries get the pricing conversation, not a check-in. The online comparison is invited and decoded: cabin class, transfers, drink packages, gratuities hide most differences. The deposit conversation is set as a dated checkpoint, because mid-season inventory moves and travelers deserve the fact, not pressure.

Past client block, seasonal. Last year’s travelers get called about this year’s season before they book direct. It is a relationship call and should sound like one: the trip they took, what they said afterward, the same season’s options. The AI summary from the original booking makes the call feel like memory, which is exactly what it is.

Post-trip calls, two weeks after return. Not a sales call and it contains none: what was the best part, what would you change. The answers improve the next itinerary, they surface the referral, and the next proposal for that client starts from a better brief.

Group queue, as they arrive. Ten travelers together is a different motion: an organizer, conflicting constraints, a shared budget conversation, a deposit deadline. The call captures who commits, who collects money and what happens when someone drops, and the queue stays separate so individual pipelines stay clean.

Attempt cadence travelers tolerate

Inquiries: attempt one inside three days, attempt two the following week at a different hour, attempt three inside 30 days, then a dated re-entry if the trip window is still alive. Proposals: the dated checkpoint structure carries it; a missed checkpoint gets one reminder call, then a re-entry tied to the season. Past clients: once per season cycle, plus the post-trip call. Attempt caps enforce all of it, and a do-not-call request removes the traveler from every queue, which is both the rule and the relationship-saving move.

Dispositions that move a booking forward

Proposal sent, deposit requested, comparing options, budget mismatch, travel date moved, past client rebook, wants group pricing, callback requested, left voicemail, do not call. Each one carries a date or a reason: “travel date moved” keeps the record with the new dates and a timely callback; “comparing options” notes which option and against what, because that is the objection the next call answers. The disposition routes; the summary carries the nuance.

Three lines and the AI summary workflow

Three lines clear the voicemail layer so a two-hour block produces conversations instead of rings. After each connect, the AI writes the transcript and fills the fields: destination and trip shape, dates and firmness, party size and ages, preferences, budget band, decision step, the objection in their words. The advisor’s job is verification: dates, ages and prices against the recording, every time, because a wrong date becomes a wrong booking and a wrong age changes both price and paperwork.

The summaries compound into the household record regulars expect: the loyalty status, the pre-cruise night habit, the anniversary week. The advisor who reads the summary before the rebooking call sounds like the professional who remembered, because the system remembered.

KPI ranges and the production benchmark

• Dials per active calling hour: 70 to 100, median near 85 in DialBreeze production use, 3-line sessions, 90 days.
• Dials per advisor day: 150 to 400 depending on proposal load; advising hours and calling hours are different hours, and both need protecting.
• Person-connect rate: 12 to 22 percent planned, 17.8 percent production median; evenings run differently, measure separately.
• Inquiries touched inside one week: 95 percent. The one number with no asterisks.
• Deposit conversations held per week: your own baseline; proposals sent is the denominator you can name.

The production figures come from 37,411 dials over 90 days to 2026-09-26 in DialBreeze operation, aggregate activity, not customer results and not a promise about your lists.

Compliance checklist for the travel practice

Consumer travel calls are telephone solicitations: calling hours 8 a.m. to 9 p.m. at the traveler’s location under 16 CFR 310.4(c), registry screening every 31 days for marketing calls beyond your own inquiries, and immediate opt-out honoring. Revocations by any reasonable means must be honored within ten business days under 47 CFR 64.1200(a)(10). All-party recording consent in the states that require it, with the disclosure. Seller of travel registration or bonding where your states demand it. Nothing here is legal advice; the list policy belongs in writing with counsel’s review where your client base crosses strict states.