Reminders use confirmed travel records and supported schedules. A week-ahead email brings the trip together. Day-before notices highlight departure details. The train-text default is two hours before the booked departure, even if the train later runs late. Printable hotel information is email-only for applicable trips.

Deadline warnings should arrive early enough to act: the starting policy is 72 hours before a known deadline, with one unresolved urgent follow-up inside 24 hours. Entry documents may need much longer lead times. Exact supplier deadlines and time zones take priority.

Nonurgent actionable items should be bundled into at most one relevant daily digest per channel. Unchanged, resolved and duplicate items should stay quiet. Urgent verified changes may notify separately. Current implementation and delivery ownership vary by reminder family; a selected preference does not establish an active channel.

Email acceptance by the provider is distinct from inbox receipt. Uncertain sends are held for review instead of automatically retried. SMS remains unavailable until approved, enabled and tested.

Compare equivalent dates, travelers, cabin and routing. The intended points workflow may use Seats.aero if access and permission for our use are confirmed. Its results would be leads to verify with the airline or booking partner; cached results are not a guarantee of bookable space.

Show cash price, points required, award taxes and surcharges, baggage, seat fees, positioning costs, cancellation terms and total journey time. A useful starting calculation is (comparable cash fare minus award cash charges) ÷ points used. That figure is only one part of the decision: benefits, flexibility and your points balances matter too.

A transfer bonus changes the number of bank points required; it does not prove availability or good value. Verify transfer terms and award availability before any separately authorized transfer. Transfers may be irreversible.

Award availability in a cabin is different from selecting a particular seat. Window/aisle preferences are checked against the airline's actual seat map and fees where available. Extra-legroom economy is not automatically premium economy; mixed-cabin journeys must be identified. No points transfers, seat fees or bookings occur from a suggestion.

Supported flight monitoring polls near departure; it is not continuous and cannot guarantee immediate notice. Each useful alert should show the observed change, source, check time, affected leg and the practical implication for the trip. Missing data is not evidence of cancellation.

Example: a verified 45-minute delay may reduce a connection from 70 to 25 minutes. The app should flag the possible connection risk rather than declare a missed connection without enough evidence.

1. Check the airline's current status and whether it has issued a replacement itinerary.
2. Review the arrival airport, terminals, boarding cutoff and any verified connection requirement.
3. If action is needed, show airline contact/manage-booking links and help compare alternatives by arrival time, price, baggage and change terms.
4. Identify possible effects on later trains, hotel arrival or activities, while keeping those changes tentative.
5. Update the confirmed itinerary only after a change is authorized and the new booking is verified.

Booking protection differs for through tickets and separate tickets. Do not buy a replacement or cancel an existing reservation solely because of a risk alert. The guided cross-itinerary response above is a product design goal; current monitoring does not establish automated rebooking.

Use ordinary language: “Compare these two flights including bags,” “What still needs my attention?” or “Find activities that fit this free afternoon.” Be explicit about fixed dates, budget and what you want to keep unchanged.

The intended coordinator selects supported tools, shows sources and uncertainty, and separates research from proposed edits and transactions. Supplier login, MFA or CAPTCHA may require your participation. Never paste passwords or verification codes into chat. The assistant panel here is a local demonstration, not a connected AI service.

Railway hosts the owner website and selected workers. Gmail handles enabled owner email. FlightAware supports scoped flight observations. Rail Data Marketplace supplies supported UK departure information; cloud rail validation is still pending. Twilio is intended for SMS, which is not operational yet.

Seats.aero access for the proposed shared use remains to resolve. All Aboard and Transitous are being evaluated for European rail; neither is integrated. No single connection currently provides worldwide real-time rail, guaranteed award inventory or every bookable fare. Account requirements, fees and shared-use permissions must be checked per provider.

The intended setup lets each person change all or some preferences in an isolated workspace. Current access remains owner-only until isolation and recipient verification are implemented. Personal bookings and credentials must not appear in public examples. Cloud hosting, source history and encrypted data backups are separate responsibilities.

When registration is available, use your own email address and choose a display name. Setup will explain whether your email is your username or a separate username is required. Use the supported sign-in method shown on that screen. If a password is required, generate a unique password in your password manager and follow the displayed length and character rules. Save it against the exact website address.

Open the verification message and confirm your email. Check spam if it does not arrive. Use the sign-in page’s recovery option if you lose access; do not create duplicate accounts to work around a login problem. Never put passwords, recovery codes or one-time codes in AI chat.

If offered, enroll a passkey or authenticator, complete its confirmation step and save recovery information securely. Choose a recognizable workspace name, preferred language and home time zone. A workspace is intended to keep your trips, preferences, contacts and conversations separate from other users. Sharing and invitations must show exactly who can access what before you approve them.

On a shared device, sign out when finished. A display name is not a login credential, and another traveler’s workspace should never be used to store your bookings.

Review every starting preference: seat and cabin, hotel room and bathroom, budget and flexibility, baggage, entertainment interests and accessibility needs you choose to provide. Change all or just selected defaults; distinguish your general preferences from exceptions for one trip.

Verify your own email and, if using texts, your phone number with country code. Choose which categories arrive by email or text, their lead time, digest time and time zone. Review quiet hours and urgent-change behavior when available. The proposed worldwide train reminder starts at two hours before departure. A selected channel remains pending until enabled and tested.

The coordinator is the part that brings your request, saved itinerary and supported tools together. Setup should show the AI provider, any required subscription or usage budget, permitted tools and a connection test. Grant only the access you want and review costs before enabling a paid service. Current website chat is not connected.

You may need your own airline, hotel, rail, event or loyalty accounts. Sign in directly on each supplier’s website and complete its MFA yourself when requested. These accounts have separate passwords and recovery processes. The assistant can help research, navigate and prepare booking steps where supported, but some sites restrict automation or require you to finish. API connections are configured through a secure connection workflow, never by pasting keys into chat.

Start with destination, dates or flexibility, departure city, travelers and budget. Add existing confirmations through a supported import or entry flow; review names, local dates, time zones, connection legs and cancellation deadlines. Keep ideas marked as planned until a booking is verified.

Try an example request below, inspect the sources and proposed changes, then preview one reminder. Verify its recipient and time and run an explicitly approved delivery test. Confirm actual inbox or phone receipt. Setup should show Ready, Needs attention or Not connected for each service, plus how to reconnect, change preferences, export data and get help. Do not rely on a pending channel.