AI can suggest the trip. Your group should choose it.

An AI assistant can make a shortlist quickly. It cannot know which compromise your friends willingly accept unless they tell it. Use generated options as material for a human decision, not as a shortcut around the group.

In this guide: Turn generated options into clear proposals for human review and voting.

1. Give the assistant the agreed boundaries

Supply dates, comfortable budget, practical requirements and preferences. Distinguish a hard condition from a nice-to-have. Ask for missing information before a polished itinerary.

2. Turn options into comparable proposals

Request the same fields for each option: experience, cost basis, travel effort, exclusions and unresolved checks. Ask what would make each option unsuitable. Do not let enthusiastic language substitute for evidence.

3. Let people choose their own response

Review the output, verify important facts and ask the crew to decide. Connected tools can help organise approved work, but the assistant should not invent consent or vote on behalf of other people.

Worked example: what this looks like

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

Simulated example: an assistant produces three weekend options. One includes an assumed rental car even though nobody has volunteered to drive. The organiser removes or revises it before voting. The remaining options become clear proposals, and the crew chooses. The AI helped structure research; it did not decide what the group wanted.

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.

For [trip destination] from [start date] to [end date], turn these agreed requirements [list] into three comparable proposals. Show cost assumptions, travel effort, compromises and facts requiring verification. Do not rank people’s preferences or infer consent. Once Limbo is connected, preview the proposals for [trip name] without saving or casting any votes.

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 useful handoff is from generated possibilities to understandable decisions. Keep the people in charge of the trade-offs.

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