> ## Documentation Index
> Fetch the complete documentation index at: https://docs.soundchecklive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Confirmations and imports

> Get travel into Soundcheck without typing it: forward flight, hotel and ground transport confirmations, import flights from Brex Travel, and record travel through connected AI tools. What each one creates on the gig.

Typing every flight and hotel is slow. Travel takes bookings from three other places: confirmation emails you forward, Brex Travel, and AI tools connected to Soundcheck. Each one ends up as ordinary flights, stays and rides on the gig.

![Travel view on a gig with lodging, flights and transportation cards](https://mintcdn.com/soundchecklive/lQnZZlowbtujL4vJ/images/travel/overview-light.png?fit=max\&auto=format\&n=lQnZZlowbtujL4vJ\&q=85\&s=cc857ea3c9a96c8634640d34882c40f8)

| Source | What it brings in | Who |
| - | - | - |
| [Forwarded confirmations](#forwarded-confirmations) | Flights, hotel stays and ground transport, read from an email | Owners, admins and gig coordinators |
| [Brex Travel](#brex-travel) | Flights booked for your team on Brex | People who can edit travel, once an owner or admin connects Brex |
| [Connected AI tools](#connected-ai-tools) | Flights, stays, passengers and guests, through the Soundcheck MCP server | Depends on the tool and your access |

## Forwarded confirmations

Forward a booking confirmation email to your organization's forwarding address. Soundcheck reads it, and it waits in the **Inbox** for you to review. Nothing touches a gig until you choose **Approve and import**.

The forwarding address, the **Inbox**, and the review steps are covered in [Forwarded confirmations](https://docs.soundchecklive.io/features/gigs/documents/forwarded-confirmations.md). This section covers what happens to the travel in an email.

### What each confirmation becomes

| In the email | On the gig |
| - | - |
| **A flight** | A flight on the **Flights** card, with the airline, flight number, airports, departure and arrival times in each airport's time zone, the booking reference and notes. The traveler becomes a passenger with the confirmation code. |
| **A hotel stay** | A stay on the **Lodging** card, with check-in, check-out, the confirmation number and notes. A hotel you haven't saved yet is added to your saved hotels. |
| **Ground transport** | A row in the gig's run of show, with its title, start and end times, and the booking details in its notes. It doesn't become a ride on the **Transportation** card. |

> [!NOTE]
>
> A flight's passenger must match exactly one active member of your organization by email. If the traveler isn't a member, or the email matches more than one, the import stops and asks you to fix it.

### Matching what's already there

Soundcheck avoids duplicates when it imports:

* **Flights.** A flight already on the gig with the same airline, flight number, departure time and airports gets the passenger added, rather than a second copy.
* **Hotels.** A saved hotel with the same name and address is reused. A stay at the same hotel with the same check-in day is updated, as long as its confirmation number agrees.
* **Updated confirmations.** Forward a changed confirmation, such as a new departure time, and approving it updates the flight, stay or run of show row you imported before. Notes you edited on the gig are kept.

### When an import stops

Approving stops, and says why, when the gig no longer matches what was imported before. Fix it on the gig, then approve again. Common messages:

| Message | What to do |
| - | - |
| *Imported hotel stay was removed; review the itinerary on the gig first* | The stay from an earlier import was deleted. Check the **Lodging** card. |
| *This hotel booking has a different property or dates; resolve the existing stay on the gig first* | The stay was changed on the gig. Make it match, or remove it. |
| *Another stay already exists for those dates* | A different booking already holds that hotel and check-in day. |
| *Multiple saved hotels match this property* | Two saved hotels share the name and address. Remove the duplicate. |
| *Imported ground travel was removed; review the run of show on the gig first* | The run of show row from an earlier import was deleted. |
| *Imported ground travel was edited on the gig; review the run of show first* | Someone changed that row's title or times. |
| *Multiple flights match this number and schedule; resolve them on the gig first* | Two flights on the gig look the same. Remove one. |
| *This booking already has another route; resolve the existing itinerary on the gig before importing a new leg* | The same booking is already on a different flight for that traveler. |

See also [Troubleshooting](https://docs.soundchecklive.io/features/gigs/travel/troubleshooting.md).

## Brex Travel

If your team books on Brex Travel, an owner or admin connects Brex once, and then anyone who edits travel can choose **Import from Brex** on a gig's **Flights** card. Soundcheck lists the Brex flights around the gig's dates, and you pick the ones to import. Travelers are matched to members by email.

Setup and the matching rules are on [Flights](https://docs.soundchecklive.io/features/gigs/travel/flights.md#import-flights-from-brex-travel).

Brex brings in flights only. Hotels and cars booked on Brex aren't imported; add them on the gig or forward their confirmations. Brex is the only travel booking tool Soundcheck imports from today. TripIt, Concur, Navan and Egencia aren't connected; forward their confirmation emails instead.

When your Brex account has more trips than one check reads, the import sheet says *Your Brex account has more trips than one check reads, so some flights may be missing.*

Connected AI tools can also link a Brex trip to a Soundcheck [trip](https://docs.soundchecklive.io/features/gigs/travel/projects-and-trips.md#trips), so imported flights land on the right trip in a project.

## Connected AI tools

AI assistants connected to Soundcheck through the [MCP server](https://docs.soundchecklive.io/integrations/mcp-server.md) can read and record travel. They can list a project's or a gig's flights and hotel stays, search and add hotels, record flights and stays with their times, put people on them, add rides to a gig, and set up trips, trip buyouts and guest nights. Each change goes through the same permissions as the app, and removals ask for confirmation first. Nobody is notified of what they record.

Connected AI tools can't edit a person's traveler details. Passports and frequent flyer numbers stay on the person's profile.

Ask your assistant something like *"Who is flying into Chicago for Saturday's show, and where are they staying?"*. Every tool is listed in the [MCP catalog](https://docs.soundchecklive.io/integrations/mcp-catalog.md).

## Related

> [card] [Forwarded confirmations](https://docs.soundchecklive.io/features/gigs/documents/forwarded-confirmations.md)
>
> The forwarding address, the Inbox and review.

> [card] [Run of Show](https://docs.soundchecklive.io/features/gigs/run-of-show.md)
>
> Where forwarded ground transport lands.

> [card] [Integrations](https://docs.soundchecklive.io/integrations.md)
>
> Brex and the other tools Soundcheck connects to.

> [card] [Travel FAQ](https://docs.soundchecklive.io/features/gigs/travel/faq.md)
>
> Travel agents, TripIt, Concur and other import questions.

> [card] [Travel glossary](https://docs.soundchecklive.io/features/gigs/travel/glossary.md)
>
> PNR, confirmation code and other booking terms.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.