Inbound trips — tracking visitors

Most trip planning is outbound (you traveling somewhere). Inbound trips invert that — track visitors coming to your office, partner site, or event. The platform handles the same itinerary structure but for someone else, with host-side workflow built in.

Two ways to create an inbound trip:

Forward an itinerary email:
• Visitor's calendar invite or itinerary email gets forwarded to [email protected] (or a custom alias on your domain)
• Email parser extracts dates, flight info, hotel, agenda
• Creates an Inbound Trip on your org with the visitor as a Contact (creates contact if one doesn't exist)
• You're notified "New inbound trip from [visitor] arriving [date]"

Manually:
• Trips → "+ New trip" → toggle "Inbound (someone visiting us)"
• Pick the visiting Contact (or add new)
• Add their flights, hotel, planned meetings, expected arrival/departure

What inbound trips show:
• Live flight status of the visitor's incoming flight (so you know when to leave for the airport)
• Hotel info (so you know where they're staying — and can send a "welcome packet" or arrange ground transport)
• Their agenda while on-site (linked to internal calendar events, meetings, building access)
• Pre-arrival checklist (door access provisioned? parking permit issued? laptop loaner ready?)

Host workflow:
• Assign a host (the org member responsible for the visit)
• Host gets a daily briefing email morning of: "Today: [visitor] arrives 14:30 at PHX, flight DL1234, hotel: Westin"
• Wally surfaces inbound trips on your home dashboard if you're the assigned host

Use cases:
• Partner orgs visiting for joint customer meetings
• Customers coming to your office for executive briefings or training
• Contractors arriving for installation/audit work
• Conference speakers visiting your event venue (Festival Pass holders, vendor booth setup)

Privacy:
• Inbound trips are visible to org members with the host role or admin
• Visitors don't see the inbound trip from their side — it's purely for your team's coordination
• If the visitor is also a Turtini user, their outbound trip and your inbound trip are NOT auto-linked (privacy-preserving) — both remain independent records