July 26, 2026 · Limbo Crew
How to ask AI for three genuinely different trip options
Compare a relaxed, adventurous and food-focused version under the same constraints. Practical steps and a worked example.
Photo: Vyacheslav Argenberg · CC BY 4.0. Full-frame photograph; cover thumbnails may crop for layout.
Three itineraries with different restaurant names are not three meaningful options. Hold the constraints steady and vary the experience so the crew can compare genuine trade-offs.
In this guide: Compare a relaxed, adventurous and food-focused version under the same constraints.
1. Fix the comparison frame
Use the same destination, dates, traveller count, budget scope and accommodation assumptions. Otherwise one version may look better simply because it spends more or assumes another night.
2. Vary the daily rhythm
Ask for relaxed, active and food-led versions with different time allocations. Require the assistant to explain what each gains and sacrifices. Do not define ‘active’ as ignoring rest or realistic transfers.
3. Audit before choosing
Check that all versions satisfy the same requirements. Compare travel time, fixed bookings, free time and unresolved facts. Ask the crew to select a direction before combining favourite elements.
Worked example: what this looks like
Fictional scenario—not a real customer story or executed AI result.
Simulated example: a four-day city trip produces a relaxed one-neighbourhood-per-day version, an active version with one checked excursion and a food-led version with longer meals and market time. All preserve the same arrival/departure days and budget scope. The group combines the relaxed structure with one food experience rather than stacking all three itineraries together.
Photo: Jebulon · CC0. Full-frame photograph; cover thumbnails may crop for layout.
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.
Create three genuinely different [destination] trip options for [dates + travellers]: relaxed, active and food-led. Hold [budget, rooms, transport, requirements] constant. For each show daily rhythm, fixed commitments, free time, travel effort and sacrifices. Flag facts needing sources. Do not merely swap attraction names or combine all options into one overloaded plan.
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.
The point of alternatives is to choose what not to do. Resist turning every attractive suggestion into another compulsory stop.
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
These references support the workflow and further checks; fictional examples are authored illustrations, not evidence of live prices, bookings or customer outcomes.