“I’m easy” is not a decision: yes, no and abstain explained

‘I’m easy’ can mean ‘yes’, ‘I do not mind either way’, or ‘please stop asking me’. Those meanings produce different outcomes. Help people choose a response that matches their actual intent rather than translating vague chat messages for them.

In this guide: Help travellers distinguish agreement, disagreement and genuinely having no preference.

1. Use yes for actual support

A yes means support for the described proposal, with its stated assumptions. It should not be inferred from an emoji on an earlier idea. Ask someone directly if the price, timing or room arrangement has changed.

2. Use no to surface a problem

A no can mean the option is unsuitable, unaffordable or simply not wanted. Offer a separate way to explain a constraint without demanding personal detail in public. Do not pressure someone to abstain to make the result look friendlier.

3. Distinguish abstention from no response

An abstention is an intentional recorded choice not to support either side. Silence is missing input. In Limbo the available choices are Yes, No and Abstain; explain how the trip’s resolution rules apply rather than treating abstentions as hidden yes votes.

Worked example: what this looks like

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

A group considers a boat outing. Ana wants to go and votes yes. Bo has motion-sickness concerns and votes no without sharing medical details. Cam genuinely has no preference and abstains. Dee has not read the proposal. The organiser follows up with Dee, does not rewrite Cam’s choice, and offers a land-based optional plan for Bo.

Make the decision bookable, not merely popular

A proposal needs a stable meaning from the moment people read it to the moment someone acts on it. Keep the dates, people, total-cost basis and important conditions together. If those facts change, explain the new version instead of silently editing the commitment beneath an earlier response.

Do not confuse three separate stages: an idea is worth considering, the group supports a specific proposal, and the affected people have authorised the booking and their contribution. A ballot helps with the middle stage. It does not verify supplier availability or move money.

Before closing the discussion, write the next action as a sentence with an owner: “Jordan will confirm the exact room arrangement by Thursday, then ask the crew to approve the current booking total.” That is more useful than “sorted”.

A message or brief you can copy

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.

Please choose Yes if you support this exact option, No if it does not work for you, or Abstain if you intentionally have no preference. If you have not read it yet, let us know rather than sending a vague ‘easy’. We will not record votes for anyone else.

Before you call it settled

• The proposal means the same thing to everyone reading it.
• Hard constraints are handled before preferences are compared.
• Each person chooses their own response; silence is not a payment instruction.
• The actual ballot result and settings are understood.
• A named person owns the next supplier or booking check.

A clean response is more valuable than apparent enthusiasm. The aim is to understand the crew, not to make every proposal look unanimous.

Put the decision somewhere useful

Keep the proposal, current terms and next action with the trip in Limbo. Use the relevant help guide below for the actual workflow; the examples above do not create a booking or determine your configured ballot outcome.

Sources and further reading

• Limbo: current voting guidance

Product guidance was reviewed against the local Limbo help content and voting implementation on 19 September 2026. The suggested group process is separate from the actual configured ballot rules.

Keep planning

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