How can we
help you today?
How-to guides, troubleshooting, FAQs, and product updates for UrTravelPro — everything you need to get the most out of Books, Marketing, Compass, and Trips.
Featured
Fresh off the pressEmail Series — automate your trip follow-ups
Email Series turn your best follow-up sequences into automation: build an ordered set of email steps once, assign it to a trip, and the right emails send at the right time — from your own mailbox, with attachments and merge tags handled. Covers building a series, trigger types, send times, assigning, and per-trip skip/reschedule overrides.
Invoicing — Send, Track, and Book Payments
How invoicing works in Books: create invoices with categorized line items, email them to clients from your billing address, track viewed/paid status, and post payments to the ledger. Cash-basis by default — the invoice hits the books when you mark it paid.
Groups in Trips — what they are, when to use them
Groups are Trips' primitive for hosted cohorts — cruise groups, escorted tours, themed trips, corporate incentives. This article explains what a Group is, when to reach for one instead of individual Trips, and how the pieces fit together.
More guides
92 guidesWhat a Trip is in Trips
A field-by-field tour of a Trip — the central record in Trips. What each field actually does, and how a Trip ties together its travelers, destinations, proposals, invoices, files and notes.
Customize your pipeline (Trip statuses)
Rename, recolor, reorder, and add custom trip statuses to match how your agency actually works — plus what core, default, final, and client-facing really mean.
Contacts in Trips
How contacts work in Trips: the split between Core identity and Trips-owned travel data, the contact drawer's tabs, the find-or-create dedup flow on add, and how contacts become travelers on a trip.
Companions and relationships
Link spouses, kids, parents, friends, and travel partners between contacts in Trips. How mirrored pairs work, how to add and remove them, and where they show up.
Global search (Cmd-K)
How the topbar global search works in Trips: how to open it with Cmd-K / Ctrl-K, the buckets it searches (trips, invoices, forms, reports, contacts), how phone/email/name matching works on contacts, and how clicking a contact opens the drawer in place on /contacts.
The Trip page, top to bottom
A guided tour of the trip detail page: the hero, the eight tabs, the action pill, the "+ Create" menu, and the right-rail Trip details card. Where everything lives and how to interact with it.
Trip files (encrypted attachments)
How the Files section of a trip works: uploading documents, the 25 MB limit and supported file types, the client-visible toggle that controls what your traveler sees in the portal, virus scanning, encryption, and the access log we keep for every file.
Send emails from your own Gmail
Connect your Google or Workspace mailbox so trip emails go out from your real address, sent copies land in your Sent folder, and client replies thread back to the trip's Messages tab automatically. Covers the OAuth flow, the scopes we ask for, the fallback sender, and disconnect.
Trip Memories (client-uploaded photos)
A private photo shelf on each trip in the client portal — travelers upload photos from their phone, see them next to their itinerary, and keep them as a memento after they get home. Agent-blind by design.
Custom domain for the portal
Run the client portal on your own subdomain — e.g. portal.youragency.com — instead of the shared trips.urtravelpro.com host. Walks the CNAME setup, the four pending states, the SSL wait, the Apple Pay re-registration step, and the cross-host session handoff.
Invite a client to the portal
Two places to send a portal invite — the trip's travelers strip and the contact's Access tab — plus the auto-invite setting, the 7-day claim link, resending, and how disabling and reactivating works.
The branded client portal
A tour of the client-facing portal in Trips — what your clients see when they sign in, how trip pages, messages, files, and notifications work, and why portal logins are kept separate from your agent session.