---
title: "Identifying high-intent travel enquiries"
description: "Identify planning-ready travel enquiries with observable signals, a local triage scorecard and a Nowah-supported example that prompts useful questions."
canonical: https://nowah.xyz/blog/travel-agents-identifying-high-intent-travel-enquiries
lastModified: "2026-11-20T15:07:02.550Z"
---

# Identifying high-intent travel enquiries

Identify planning-ready travel enquiries with observable signals, a local triage scorecard and a Nowah-supported example that prompts useful questions.

Identify high-intent travel enquiries by checking what the traveller wants to decide and whether you have enough information to help. Destination direction, dates, party details, budget scope and a decision timeline are useful signals. They indicate planning readiness, not a proven probability that someone will book.

Use the 15-point worksheet below as an agency triage aid, then ask focused questions. A worked hypothetical example uses [Nowah](https://app.nowah.xyz) to prepare two planning directions that a traveller can discuss before you undertake more detailed research.

## What “high intent” means in agency operations

“High intent” is not “the nicest lead” or “the biggest budget.” Operationally, it means:

- **The enquiry is constrainable**: you can narrow it into a small number of viable trip structures.
- **The traveller can approve next steps**: either they decide, or they can state who decides and when.
- **They accept real-world constraints**: availability and supplier terms govern bookings, changes, and refunds; you’ll obtain their approval before payment.

Your objective at this stage is not to deliver a complete quote. It is to decide whether the enquiry deserves immediate planning energy, a limited “proof-of-fit” response, or a short request for essentials.

## Five planning-readiness signals to investigate

Enter the confirmed constraints in Nowah to investigate the remaining trip choices. The [brief audit](/blog/travel-agents-auditing-a-travel-brief-before-starting-research) distinguishes a researchable request from missing essentials.

### Strong signals

1. **Timing tightness**: exact dates, a fixed week, or a narrow window.
2. **Destination direction**: a city/route, not only a theme.
3. **Budget boundaries**: a ceiling/range and what it must include.
4. **Party clarity**: number of travellers, room set-up, and any mobility/pace constraints.
5. **Decision trigger**: an event, leave approvals, school break, or “ready to book soon.”

### Misleading signals (false positives)

- **Urgent tone without inputs** (“Need this ASAP”) can still be low intent if dates/budget/party are missing.
- **“Send deals” language** can indicate bargain-hunting rather than booking readiness unless paired with dates and constraints.

Missing details call for clarification, not a judgement about the person. A first-time traveller may need help defining the brief, while someone with exact dates may still have no authority to approve a purchase.

## The 15-point Intent Scorecard (copy/paste rubric)

Use this internally as a starting worksheet. The points and bands are illustrative, not validated conversion benchmarks. Review them against your own completed enquiries before relying on them to allocate substantial work.

| Signal | 0 points | 1 point | 2 points | 3 points |
| --- | --- | --- | --- | --- |
| Destination | None | Theme only | Country/region | Specific city/route |
| Timing | None | Season only | Month + duration | Exact dates / fixed week |
| Budget | None | “Affordable/cheap” | Range/ceiling | Ceiling + priorities |
| Party | None | “Couple/family” | # travellers | Ages/constraints + room needs |
| Trigger | None | “Thinking about it” | “Soon” | Deadline/event/ready to book |

**Interpretation:**

- **12–15 = High intent:** prioritise today; move toward structured options.
- **8–11 = Developing intent:** respond with tight questions + a mini plan to prompt a choice.
- **0–7 = Information incomplete:** ask for the essentials and offer an appropriate discovery step rather than assuming the person is uninterested.

Tip: keep the score private; it’s a routing tool, not a client-facing label.

## A triage workflow that protects your time (without ghosting leads)

A practical daily routine:

Use Nowah for a bounded comparison after triage, keeping the work proportional to readiness. The [enquiry prioritisation method](/blog/travel-agents-choosing-which-travel-enquiries-to-prioritise) helps allocate that research time.

1. **Batch new enquiries** (e.g., morning and late afternoon).
2. **Score each** using the rubric.
3. **Send one of three response types**:

- **High intent**: propose two trip structures; ask only missing essentials to start availability checks.
- **Developing**: ask 3–5 targeted questions; include a “proof-of-fit” mini plan framework.
- **Incomplete**: ask for destination direction, date window, and budget scope; explain what you can research once those are clearer.

4. **Only begin live searching** (flights/hotels) after the traveller confirms basics and chooses a direction. Bookings are subject to supplier availability and terms; obtain client approval before payment.

## Two-message triage script (high intent) that tests commitment

Use this when a lead scores 12–15 or feels close.

### Message 1: confirm fit + propose structure

Yes—I can help. Based on what you’ve shared, I suggest we start with **two route options** and then I’ll check live flight/hotel availability once you choose a direction.

To make this efficient, please confirm:

1) Departure city/airport

2) Your tightest date window (earliest depart / latest return)

3) Room set-up (one room vs two; bedding needs)

### Message 2: set expectation + next step

Once you confirm those three items, I’ll send **Option A and Option B** with clear trade-offs so you can pick one. After you choose, I’ll check live availability and return a short list of bookable choices for your approval before any payment.

This script does the intent work for you: it asks for minimal facts and makes the next step a decision, not a brainstorm.

## Use a small planning comparison to clarify fit

A mini plan is intentionally constrained:

- It presents **two coherent trip structures** (A/B), each viable.
- It highlights **trade-offs** (pace vs coverage, rail vs flights, one base vs two bases).
- It ends with **a choice**: “Pick A or B so I can check availability.”

## Worked example: score, response, and a Nowah prompt you can reuse

Show how the Nowah outline changes when the traveller chooses a slower pace. Use the [itinerary review rubric](/blog/travel-agents-creating-a-repeatable-ai-itinerary-review-rubric) before interpreting their response.

### Hypothetical enquiry (fictional)

Hi—We’re considering Japan for about 10–12 days in a future late-March window. Two adults and one 9-year-old. We want Tokyo plus one other base with day trips, and mid-range hotels in walkable areas. Total budget around USD 12,000 excluding shopping. If it’s a good fit we’d like to book flights and hotels soon.

### Score it

- Destination: **2** (country + general structure)
- Timing: **2** (late March + duration)
- Budget: **3** (ceiling + exclusions)
- Party: **3** (count + child age)
- Trigger: **3** (“book soon”)

**Total: 13 (High intent).**

### Your reply (tight and decisive)

Thanks—yes, I can help.

For 10–12 days with a 9-year-old and a walkable-hotel preference, a sensible starting point is **Tokyo + one additional base** with day trips. I’ll send two route options so you can choose a direction.

To start checking live flight and hotel availability, can you confirm:

1) Your departure city/airport

2) Earliest departure and latest return dates

3) One room for three vs two rooms

### Copyable Nowah planning prompt (mini plan)

Use fictional details for practice. For real clients, handle information through your approved process and confirm the actual future dates before searching live offers.

Create two trip structures for Japan for 2 adults + 1 child (age 9), 11 days, using the future date window I provide next.

Priorities: walkable hotel areas, efficient rail routing, kid-friendly pacing with daily buffer time.

Budget guidance: around USD 12,000 total excluding shopping; target mid-range hotels.

Output two options:

A) Tokyo + Kyoto base

B) Tokyo + Osaka base with day trips

For each option provide:

- Suggested hotel areas by neighbourhood (no specific properties)

- Day-by-day outline with realistic pacing

- Key trade-offs (why choose A vs B)

- A short list of questions I must confirm before I run live flight/hotel availability checks

### What the adviser checks before using the output

Treat Nowah’s draft as a starting point that you validate:

- **Assumptions**: placeholder dates, airport logic, trip length.
- **Pacing**: buffers included; no unrealistic transit stacking.
- **Trade-offs**: A and B are meaningfully different.
- **Decision readiness**: questions list is short and actionable.

## The intent-confirming question bank (use selectively)

These questions are designed to *increase signal* without turning into a full discovery call. Use only what’s missing.

**Core (most often needed):**

- “What is your departure airport/city?”
- “What’s your earliest departure and latest return?”
- “Is your budget a ceiling, or a target with flexibility?”
- “One room or two? Any bedding needs?”
- “What are your top two priorities (location, nonstop flights, room size, pace)?”

**Decision and timing questions:**

- “Who needs to approve the plan, and when can you decide once you see options?”
- “Once you have reviewed suitable options and their conditions, when would you be ready to decide?”

## One-page checklist: “Is this enquiry high intent?” (ready to paste into SOPs)

- \[ \] Destination is specific enough to research \(at least country/region\)
- \[ \] Dates are fixed or the window is narrow
- \[ \] Budget boundary exists \(range/ceiling and inclusions\)
- \[ \] Party is clear \(\# travellers \+ room needs\)
- \[ \] Trigger exists \(deadline/event/readiness\)
- \[ \] Decision path is clear \(who approves and when\)
- \[ \] Traveller agrees to choose between A/B before you do deep availability work

If you can tick **5+** of the first six items, treat it as high intent and prioritise it.

## Use Nowah to turn the brief into a useful discussion

Nowah can help you turn an emerging brief into structured choices. The traveller’s response can clarify preferences and readiness, while you retain responsibility for interpreting it. Use Nowah for:

1. **Conversational trip research** to transform a rough brief into two viable trip structures.
2. **Editable day itineraries** with map/timeline views to sanity-check routing and pacing before you invest deeper effort.
3. **A natural transition to execution** once intent is confirmed: flight search (including multi-city) and hotel search/booking, plus travel eSIM purchasing when relevant (see [Nowah features](/features)).

When your process is: *score → propose A/B → get a choice → check live availability*, you have a clearer record of the decisions requested and the information still needed. Compare that process with actual outcomes rather than assuming a score guarantees a sale.

Build your next “proof-of-fit” mini plan in Nowah at [Open Nowah](https://app.nowah.xyz), and keep the product reference handy for capabilities at [/features](/features).

## Related guides for travel agents

- [Building relationships with executive assistants](/blog/travel-agents-building-relationships-with-executive-assistants)
- [Measuring the quality of travel agency leads](/blog/travel-agents-measuring-the-quality-of-travel-agency-leads)
- [Qualifying travel leads before preparing a quote](/blog/travel-agents-qualifying-travel-leads-before-preparing-a-quote)
