Disney Imports

Disney sends confirmation emails directly to the guest — you (the travel agent) often don't see them until the client forwards them over. "Here's my dining confirmation", "Here's my Lightning Lane purchase", "Can you add this to our itinerary?" Each one used to mean manual data entry into the booking form.

Disney Imports is the intake lane for those forwards. Your client forwards the email to a dedicated address, JourneyFuse's AI reads the confirmation, and the result lands in a queue you can review. One click attaches it to the right trip and creates a booking.

Covers: Advance Dining Reservations (ADRs), Lightning Lane / Genie+ / ILL passes, Disney resort reservations, park tickets, Disney Cruise Line sailings, and Aulani stays.

How It Works

1. Your client forwards a Disney email

Every workspace has a dedicated Disney import address:

disney+<your-workspace-id>@mail.journeyfuse.com

You can find yours in Settings → Integrations → Disney Imports. Share it with clients who book their own Disney add-ons. They forward any WDW, Disneyland, Disney Cruise Line, or Aulani confirmation email to it.

Tip: Some agents save the forwarding address as a contact named "Disney Imports" so clients can just pick it from their address book. Others set up a client-side mail rule that auto-forwards anything from disneydestinations.com.

2. JourneyFuse parses it

Behind the scenes, we:

Confirm the email actually came from Disney (we ignore off-topic forwards)
Run it through an AI extractor tuned for Disney confirmation formats
Classify the confirmation type: dining, lightning_lane, resort, park_tickets, cruise, or other
Pull out the lead guest, party size, reservation date + time, venue or ride name, confirmation number, and — on resort guest copies — the Travel Plan Number
Try to match the confirmation to an existing trip in your workspace

3. You get notified

As soon as a forward is processed, JourneyFuse sends you both an in-app notification and an email letting you know the confirmation arrived. The notification tells you whether it was auto-matched to a trip or still needs a trip picked. You don't have to keep checking the queue manually.

4. You review + attach

Open the Disney Imports page (sidebar under Tools) and you'll land on the Needs attention view by default. This view shows both unmatched confirmations and auto-matched ones that haven't been turned into bookings yet, so nothing slips through. Open an item, confirm (or fix) the extracted details, pick the trip it belongs to, and click Create Booking. Done — the booking is created, linked to the trip, and the import is marked attached.

The Disney Imports Page

You'll find it in the sidebar under Tools. The page has four tabs:

Needs attention (default) — both unmatched confirmations and auto-matched ones that are waiting to be turned into bookings. This is where your attention goes. Previously, auto-matched imports were only visible on a separate tab and could look like they had failed to arrive; now they're right here alongside unmatched ones.
Unmatched — new forwards with no suggested trip yet. A subset of what's in Needs attention.
Attached — confirmations you've already turned into bookings. Useful for auditing what came in.
Dismissed — things that weren't worth attaching (spam, duplicates, already-booked confirmations). Restorable if you dismiss by mistake.

Each card shows:

Confirmation type badge — Dining, Lightning Lane, Resort, Park Tickets, Cruise, or Other
Match confidence — strong / likely / low, based on how well the guest name + date match an existing trip
The key fields — venue / ride name, date, time, party size, confirmation number
Suggested trip — if the matcher is confident, we show which trip this probably belongs to
Source — the client's email address and the subject line, for context

Attaching an Import to a Trip

Click Attach on any unmatched card. The drawer that opens is pre-filled with the extracted data — most of the time you just pick the trip and hit Create Booking. When the AI got something slightly off, you can fix it right there.

Fields you can edit:

Trip — required. The matcher pre-selects a trip when confident; otherwise pick from the dropdown.
Booking type — defaults based on the confirmation type (dining → Dining, lightning_lane → Lightning Lane, etc.). Override if the email was misclassified.
Venue (or Attraction for Lightning Lane) — the restaurant, resort, park, ship, or ride name.
Date + Time — ISO date + free-text time (e.g. "7:30 PM"). Required for dining ADRs; the time lands on the new booking so it shows up in the itinerary.
Confirmation # — Disney's reservation ID / pass number.
Party size — defaults to what was on the email, editable.

Hit Create Booking and JourneyFuse:

Creates a booking on the selected trip with the correct type, supplier, time, and confirmation number
Marks the Disney Import as attached with a link to the new booking
Auto-seeds a matching itinerary block (with the correct time) if the trip has an itinerary

Dining ADR pro tip: the time you enter here flows straight into the itinerary dining block on the correct day. No more re-typing "7:30 PM at Chef Mickey's" in three different places.

Confirmations on the Trip Itself

Auto-matched confirmations also surface directly on the trip so you don't have to go hunting in the queue:

Trip header banner — a "Forwarded Disney confirmations" banner appears near the trip header when one or more matched confirmations are waiting. One click opens the attach drawer, pre-filled with that trip already selected. You can also dismiss the banner from there if the import isn't actionable.
Bookings tab — a section at the top of the trip's Bookings tab lists any matched-but-not-yet-attached confirmations, each with an Attach button that works the same way.

Both surfaces disappear once all matched confirmations for that trip have been attached or dismissed.

Travel Plan Numbers

A Walt Disney World or Disneyland guest copy prints two numbers that look alike but mean different things:

Hotel Confirmation Number — identifies one reservation: this room, these dates.
Travel Plan Number — identifies the whole Disney order. The room, the park tickets, the dining plan and Memory Maker all hang off the same Travel Plan Number.

The Travel Plan Number is what Disney's phone agents ask for when you call to change something, so JourneyFuse stores it separately rather than overwriting the confirmation number.

Where it shows up:

Booking form — a Travel Plan Number field appears under Confirmation Number on Walt Disney World and Disneyland bookings. It's hidden everywhere else, including Disney Cruise Line, because no other supplier issues one.
Booking details — a Travel Plan value sits beside Confirmation.
Disney Command Center — when every Disney booking on the trip shares one Travel Plan Number, it appears as a chip in the command center header. Click it to copy. A trip whose bookings carry more than one travel plan (a split stay, for example) shows no header chip — read the number from each booking instead.

Only guest copies carry a Travel Plan Number. Reservations you made in Disney's travel agent portal don't print one, so most Disney bookings will simply have no Travel Plan value, and nothing is shown for them.

Booking Type Mapping

Behind the scenes, confirmation types map to booking types like this:

Disney confirmation	Becomes booking
Dining (ADR)	Dining
Lightning Lane / Genie+ / ILL	Lightning Lane
Resort reservation	Resort
Park tickets	Park
Cruise (DCL sailing)	Cruise
Other	Other

You can override the type in the attach drawer if the AI misclassified. Override also lets you promote a DCL confirmation to a Cruise booking with the ship name in the supplier field, or attach a Lightning Lane as a generic Activity.

When to Dismiss Instead of Attach

Not every forward becomes a booking. Common reasons to dismiss:

Duplicate — client forwarded the same confirmation twice, and you already attached the first one
Already booked — you entered this manually before the forward came in
Not actionable — Disney newsletter, cancellation notice, survey request, marketing
Wrong workspace — a client forwarded a personal trip to your agency address by mistake

Dismissed items go to the Dismissed tab, which keeps an audit trail without cluttering Unmatched. If you dismissed something by accident, click Restore to put it back.

What Gets Auto-Matched

When a confirmation comes in, JourneyFuse tries to guess which trip it belongs to by checking:

Lead guest name against trip clients and household members
Reservation date against trip start/end dates
Confirmation number against bookings you already have

When the match is confident (the lead guest name + date line up with exactly one Disney trip), the import lands pre-linked to that trip and the Attach drawer opens pre-filled with the trip selected. You still confirm before the booking is created — the matcher never writes a booking on its own.

Low-confidence matches still show a suggested trip in the card, but you'll pick it manually in the drawer.

Supported Confirmation Formats

We extract from the standard Disney confirmation emails:

Walt Disney World — dining, resort, park tickets, Genie+ / Lightning Lane purchases
Disneyland Resort — same categories as WDW
Disney Cruise Line — sailing confirmations across Wish, Fantasy, Dream, Magic, Wonder, Treasure, Destiny, and Adventure. DCL forwards now show up in the Imports queue just like WDW and Disneyland confirmations (previously they were processed internally but never surfaced to you).
Aulani — resort reservations

The extractor is forgiving with attachments — if the confirmation was forwarded as a PDF (some clients do this to preserve formatting), we OCR it and extract from there too.

Limits + Gotchas

Only Disney emails. The import guard rejects anything that doesn't look Disney-related so a random client forward doesn't end up in the queue. If you expect a confirmation that didn't show up, check your Unmatched tab first, then confirm the client actually forwarded to the Disney address (not your regular inbox address).
Matched to workspace, not agent. Any agent with access to the workspace can see and attach imports. If your agency has a Disney specialist, it's fine for them to own the queue — but any teammate can help out.
The matcher won't create trips. If a confirmation arrives for a client who doesn't have a Disney trip yet, the matcher leaves it Unmatched. Create the trip first, then reopen the import and it'll let you select the new trip.
One booking per attach. Each confirmation becomes exactly one booking. A resort email with both a resort stay and a linked dining package should be split into two forwards (or attach the main one and add the dining as a separate manual booking).

AI Booking Import — for non-Disney confirmations (airlines, cruise lines, hotels), use the paste/upload flow
Disney Dining Alerts — get notified when hard-to-book ADRs open up
Bookings — managing individual bookings on a trip