Call IMPT
Call IMPT / Hotel Swarm / Agents / Intent agent

Intent agent

The Intent agent — parsing your trip brief

Parses the user brief into constraints, preferences, priorities, traveller types, and optional extras.

Direct answer

Parses the user brief into constraints, preferences, priorities, traveller types, and optional extras.

What it does

When a traveller says 'find me a hotel within 15 minutes of my meeting, with late check-in, reliable Wi-Fi, a quiet room, an airport taxi, and breakfast', the Intent agent breaks that into structured fields: hard constraints (15 min from meeting, late check-in), preferences (Wi-Fi, quiet, breakfast), and optional extras (taxi). Every other agent in the swarm reads from this structured trip-brief object.

Example inputs

Outputs

trip_brief object with: dates, destination, traveller count, meeting location, desired amenities, food preferences, sustainability constraints, budget hints, optional extras

Try the live booking flow

Parses the user brief into constraints, preferences, priorities, traveller types, and optional extras. — much of this is already running under the hood on the current IMPT booking flow.

Search hotels →

Other agents

Frequently asked

What does the Intent agent actually do?

Parses the user brief into constraints, preferences, priorities, traveller types, and optional extras.

Does it run on every search?

Yes. The orchestrator dispatches all 10 agents in parallel for every search. Each agent has a time budget; if one runs slow, partial results stream into the UI while it finishes.

What if it can't find an answer?

It returns 'unknown' with confidence. The ranking engine uses the absence of evidence as a signal — a hotel where the Amenities agent can't validate Wi-Fi will rank lower than one where it can.

Where do I see this in production?

app.impt.io. The Swarm UI surfaces what each agent found — Phase 1 build in progress.