How to turn five wish lists into one AI trip brief

Five wish lists can contain twenty attractions and several hidden conflicts. Simply merging them creates a longer itinerary, not a shared brief. Ask AI to expose the choices that still require a conversation.

In this guide: Identify common ground, conflicts and the decisions that still need discussion.

1. Collect the same fields from everyone

Ask for must-dos, avoidances, pacing, budget boundary and one flexible preference. Use labels such as Traveller A where names are unnecessary. Do not paste private messages without considering what information the task actually needs.

2. Separate overlap from conflict

Ask the assistant to group common interests, identify incompatible requests and distinguish requirements from preferences. It should not resolve a conflict by silently dropping the minority view.

3. Return decisions to the crew

Present the unresolved questions in plain language. Agree them before requesting a day-by-day plan. Record which compromises people actually accepted so the next generation uses the right brief.

Worked example: what this looks like

Fictional scenario—not a real customer story or executed AI result.

Simulated example: five travellers share food interests, but two want early starts and three want slow mornings. Rather than averaging this into a 9 am compulsory departure every day, the brief proposes optional early outings and shared lunches. A separate conflict about car hire remains open until willing drivers and costs are confirmed.

Give the assistant a test it can actually fail

Define what a useful answer must preserve before requesting it. Examples include the same traveller count, a fixed arrival date, no car hire, a stated budget scope or an unchanged confirmed booking. Then read the answer against those requirements instead of judging its confidence.

When something fails, describe the failure precisely: “This day crosses the city three times and overlaps our confirmed entry.” Ask for the smallest repair and a before-and-after explanation. A vague request to make the plan better invites another attractive rewrite that may discard details you wanted to keep.

If a tool can change the trip, separate the planning conversation from the approved action. Inspect the exact preview, identify the right trip and check the returned result. Do not let an example prompt, draft message or hypothetical itinerary become an instruction to book, pay or speak for someone else.

Copyable AI trip prompt

Replace the bracketed fields with your own details. Read the complete text before sending it; copying it here does not send a message or perform an action.

Build one trip brief from these anonymised wish lists: [inputs]. Keep each hard requirement intact. Show shared interests, conflicting preferences, missing facts and decisions the group must make. Do not treat repeated mentions as permission to override a person’s access or spending limit. Ask concise questions before creating an itinerary.

Run a focused refinement

Use a follow-up that names the actual problem, not just “make it better”.

Review your answer about [specific trip task]. The issue is [what failed]. Preserve [confirmed facts and constraints]. Change only [scope], show what changed and why, and list any remaining unknowns. Do not invent sources or approvals. Do not save, send, book or pay.

A connected workflow needs the current account access, permissions and client support described in the Limbo setup guide. If a required tool is unavailable, keep the output as a text draft and do not claim that the trip was saved.

Before you call it settled

• The answer preserves the original trip constraints.
• Important facts have a source or are marked unverified.
• The worked example is not mistaken for a real booking or test.
• Any proposed saved action has been previewed precisely.
• Completion is claimed only when a returned result supports it.

A good AI brief is shorter than the source conversation but preserves its important tensions. If the conflicts disappear without a decision, the summary has lost information.

Put the decision somewhere useful

Keep the agreed plan and the information needed to act on it together in Limbo. Save the useful outcome of the conversation—not every abandoned option—and make clear what is still awaiting confirmation.

Sources and further reading

• Limbo: current connection setup and supported actions

These references support the workflow and further checks; fictional examples are authored illustrations, not evidence of live prices, bookings or customer outcomes.

Keep planning

• Build an AI trip plan you can actually use
• Group-trip planning guide