Travel Planning Friends

A group-trip server: itinerary, dates vote, budget, bookings, packing list, documents and live updates.

  • 5 categories
  • 16 channels
  • 6 roles
  • Small
Download Discord JSON

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

TRIP HQ

  • trip-chat

    The trip chat. Take Booked or Still Deciding here so the headcount is right.

  • itinerary

    The current plan, day by day. Planners write; everyone reads. Suggest changes in #trip-chat.

  • dates-and-votes

    Polls for when, where and how long. Vote once; planners close the poll.

  • destination-ideas

    Places for this trip or the next one. One per message so it can be reacted to.

MONEY AND BOOKINGS

  • budget-tracker

    The per-person total and what it covers. Updated when a booking is made.

  • bookings-and-confirmations

    Every flight, train and hotel confirmation, posted the moment it exists. Screenshot plus the reference.

  • who-paid-what

    Who covered what and who owes whom. Settle in a thread.

  • flights-and-trains

    Comparison links and fare alerts before anyone books.

PACKING AND PREP

  • packing-list

    The shared list: adapters, the one umbrella, who brings the speaker.

  • documents-and-insurance

    Passport validity, visas, insurance and the deadlines for each. Planners post; Vetox reminds.

  • local-tips

    Apps, phrases, tipping, transport cards. What somebody looked up so nobody else has to.

ON THE TRIP

  • live-updates

    We are at gate 12. The bus is late. Meet at the fountain.

  • trip-photos

    Photos from the trip, as they happen. Comments in threads.

  • emergency-contacts

    Hotel address, local emergency number, embassy. Read-only so it is always three messages long.

VOICE

  • Meeting Point
  • Planning Call

Roles

  • OwnerAdministrator
  • AdminAdministrator
  • Traveler
  • Booked
  • Still Deciding

Overview

Sixteen channels for a group of friends planning one trip, built to be used before, during and after it. Trip HQ is #trip-chat, a read-only #itinerary that the two planners write so the plan is always the latest version, #dates-and-votes for the polls that decide when and where, and #destination-ideas for the next one. Money and Bookings is #budget-tracker for the per-person total, #bookings-and-confirmations where every flight, train and hotel confirmation is posted the moment it exists, #who-paid-what for settling up, and #flights-and-trains for the comparison links. Packing and Prep holds #packing-list, a read-only #documents-and-insurance where the planners pin the passport, visa and insurance reminders, and #local-tips for the apps, phrases and customs someone looked up. On the Trip is for the days themselves: #live-updates for 'we are at gate 12', #trip-photos, and a read-only #emergency-contacts with the hotel address and the embassy number. Voice is Meeting Point, the room to join when the group is split across a city and needs to find each other, and Planning Call for the evening the itinerary gets argued out. Five roles: Owner and Admin are the two planners, Traveler is everyone, Booked is mentionable and means paid and confirmed, and Still Deciding marks who has not committed, so the headcount is visible on the member list.

When to use it

Six people, one trip, and the itinerary has been rewritten in the group chat four times while two people still have not booked flights. This layout keeps the current plan read-only in one channel, puts every confirmation where it can be found at the airport, tracks who has paid, and gives the group a voice room to meet in when they lose each other on the second day.

What makes it different

  • #itinerary is read-only and written by the two planners, so there is only ever one current version.
  • Booked and Still Deciding are roles, so the headcount is visible on the member list without asking.
  • #bookings-and-confirmations holds every confirmation, so nobody searches their email at the gate.
  • #emergency-contacts is read-only with the hotel address and embassy number pinned.
  • Meeting Point is a voice room for finding each other when the group splits across a city.

Recommended Vetox setup

  • Reminders

    Set Reminders in #documents-and-insurance a month before departure for passports and a week before for insurance, mentioning Traveler.

  • Self-Roles

    Post a Self-Roles panel in #trip-chat for Booked and Still Deciding, so people move themselves as they commit.

  • Embed Messages

    Use Embed Messages in #itinerary with one embed per day, so the plan reads as a schedule rather than a wall of text.

  • Counting

    Run Counting in #trip-chat as the countdown to departure; it is the one bot game a trip server needs.

Questions

What happens to the server after the trip?

Keep it. #trip-photos becomes the album, #destination-ideas becomes the seed of the next trip, and the roles reset. A group that travels together every year can reuse the same server and keep the history.

Why is #emergency-contacts read-only?

So it holds three pinned things - the hotel address, the local emergency number and the embassy - and nothing else. On the day something goes wrong nobody should have to scroll past a conversation to find them.

How do we handle two people who have not decided?

They hold the Still Deciding role. The planners can mention it when a booking deadline is close, the headcount on the member list shows how many are firm, and when they book they swap themselves to Booked in #trip-chat.

Common mistakes

  • Letting everyone edit the itinerary in chat, so there are four versions and nobody knows which is current.
  • Posting confirmations in #trip-chat, where they are impossible to find at the airport at six in the morning.

Consider instead

  • Long-Distance Circle when the group is spread across time zones and the trip is one visit among many calls and letters

Do you have any doubts?

Our team is there for you

0.0k

Servers

0+

Commands

0

Users

0

Languages