Why do forwarded booking emails sometimes lose the reservation details?
Details drop out when the message you send is no longer the message the company sent. An inline forward is a new email. Its subject and its body are whatever the sending app wrote, often a quote of the old text, with images, buttons, and attachments left behind. Attaching the original message, or saving that original as a file, keeps the reservation in the form it arrived. A screenshot is a third thing: a photograph of part of the screen, not a forward of the booking at all.
What to keep from a booking confirmation lists the fields that matter. This page is about how those fields disappear on the way to another inbox, another person, or a tool that reads mail.
A forward is a new email
RFC 5322 describes each email as its own object: headers such as From, Date, and Subject, then a body. A forward does not edit the airline’s message in place. The app creates a new message, you are its sender, and the subject line belongs to the new message.
Many apps prefix the old subject with “Fwd:” and leave the rest. That prefix is a habit. The field is editable, and a mailbox rule can rewrite it. A short phone composer can keep a title you typed earlier and never put the airline’s subject back. A search for the carrier’s wording, or a reader that expected a locator in the subject, is then looking at a different string. The code may still be in the body, or it may have lived only in the old subject. Check both.
The original From was the airline. The new From is you. Someone who needs the carrier’s address needs the original message, not the forward’s header.
Quoted body or attached original
Quoting the body pastes part of the old content under a banner. HTML may be simplified, remote pictures dropped, and buttons turned into bare links or removed. A PDF ticket or a calendar file on the original is not always reattached. The composer can look complete because you remember the layout, while the sent copy is a thinner quote.
Attaching the original is a different command, sometimes labeled “forward as attachment.” RFC 2046 describes a durable form: a note whose inner part has type message/rfc822, so the encapsulated message keeps its own headers and its own type. The RFC encourages that shape because the recipient can present the original correctly. In the inbox it looks like a paperclip that is the old email, wrapped in a short note from you.
Some mail apps never offer that command. Some hide the attachment until it is opened, so the outer body looks empty. That is a reason to open the result, not a ranking of products. If the app can only quote, and the quote is missing the locator, attach a PDF you saved from the original. Put the trip name in your first sentence so a rewritten subject does not have to carry the booking.
Confirmation drawn as a picture
RFC 2046 defines multipart/alternative for several versions of the same content, with the recipient choosing one. The plain-text version is often a short fallback. The HTML version may be a table, or one large image with the table painted into the pixels.
When the words live only in the image, a forward that keeps the plain-text part keeps the fallback. That fallback is sometimes a single sentence telling you to view the message in a browser. The names, the locator, and the times were in the picture.
Remote images widen the gap. The HTML can point at a picture on the sender’s site instead of including the bytes. An app that blocks remote images shows a hole, and a forward that never fetched those bytes forwards the hole. Seeing the picture once on your screen does not paste it into the quote.
Print to PDF while the picture is visible, or save the original message, and forward that file. How to keep bookings from different sites in one place assumes the files still contain the times. A hollow forward makes the day look shorter than it is.
Buttons that open a sign-in page
“Manage booking” and “download tickets” are often links. The link opens a site that asks for a password, a one-time code, or a locator plus a last name. The email stored the URL. The page behind the login was never in the message.
Forwarding the email forwards the URL. The next person hits the same sign-in. A reader that only sees the message cannot open a page it is not allowed to see. If the meeting point or the QR code exists only on that page, save it while you are signed in: print to PDF, then attach the PDF.
Text survives that round trip more reliably than a session. The record locator and, when printed, the ticket number are text. What is a PNR? explains why those strings are not interchangeable. Copy them from the message. Do not expect a login wall to travel with the forward.
A photograph of the screen
Forwarding a screenshot sends the image you captured. It does not send the company’s message, its headers, or its attachments. There is no text layer unless some later tool guesses letters from the pixels.
The picture contains only what was on screen. A locator below the fold, a cancellation line under a collapsed section, and a second passenger you did not scroll to are absent. A crop through a barcode makes the rest hard to use. A later schedule-change email is a different message you have not photographed.
Use a screenshot as a spare when the code, the time, the city, and the address are fully in frame. Keep the original or the PDF. What on a trip itinerary works offline? shows how that spare goes stale when a gate changes, which is a separate failure from losing the details in the forward.
What Sam’s forward kept
This walkthrough is an illustration. The name and the hotel are made up.
Sam has a hotel confirmation on a phone. The rate table is a large image. The plain-text part says “View this email in your browser.” On screen, Sam can see a property code, a street, check-in at 3:00 PM local, and a cancellation line. Forward produces the subject “Fwd: Your stay,” a quoted greeting, and a blank rectangle where the image was. Sam sends it.
The partner can see the greeting. The code, the street, and the deadline are gone. “View reservation” opens a sign-in the partner cannot pass. The reservation stayed in the original. Sam prints that original to PDF once the image has loaded, and sends the PDF. That second file is the booking. A forward-as-attachment might have carried the HTML, and the partner might still have needed to load remote images. The PDF does not depend on that.
Read it before you hit send
Inspect the outgoing message as if you had never seen the booking.
- Attach the company’s PDF, or a PDF you printed from the open original.
- When the app can attach the original message, do that instead of relying on a quote. That command is the message/rfc822 form RFC 2046 describes.
- Find the locator, the names, the times with a city, and the address as text or inside the file you attached. If you cannot point at them, wait.
- A rewritten subject is harmless once the code is in the body or the attachment. Name the trip in your first sentence.
- Add a screenshot only when the crop includes every field you would have copied by hand.
If those details are already gone from your inbox, recover the booking from the company while you can still sign in, save a PDF, and send the PDF.
Forward the original, then let a parser read it
Tineo parses a confirmation forwarded to [email protected], and pasting the confirmation also works when a quote has already dropped the image. The setup for that workflow is in Email forwarding for travel planning. Send the original message or the company’s PDF, because a parser can read only the details that are still in what you send. Connecting Gmail is optional and not required.
Frequently asked questions
Does a "Fwd:" subject remove the reservation?
The prefix alone does not delete the booking. The subject of a forward belongs to the new message, so the sending app or a mailbox rule can shorten, translate, or replace it, and a search for the airline's old subject can miss a locator that lived only there. Open the body and check that the code is still visible as text.
What should you do when the confirmation is only an image?
Save a PDF while the image is visible, or save the original message, before you forward anything. A forward that keeps only the plain-text part often keeps a fallback sentence such as a prompt to view the email in a browser. The names, times, and locator drawn inside the picture do not come along as text.
Is forwarding a screenshot the same as forwarding the email?
A screenshot is a photo of part of the screen, and forwarding it sends that picture rather than the company's message, headers, or attachments. Use it when every field you need is in the frame and readable. Keep the original email or a PDF as well.
What is the difference between quoting a message and attaching it?
Quoting builds a new email and pastes some of the old body into it. Attaching the original encapsulates that message, which RFC 2046 describes as a message/rfc822 part, so its headers and parts travel with it. Some mail apps never offer the attachment command, so check the result on screen before you send.
Related guides
- What should you keep from a booking confirmation?
Keep the traveler names, the locator, times with a zone, the address, the cancellation deadline, the amount paid, and a phone number. Skip the marketing.
- How do you keep bookings from different sites in one place?
Keep one morning from five different companies in a single note, named files, and calendar holds. Edit all three when the flight time changes.
- What is a PNR?
A passenger name record is the booking. The record locator, the ticket number, and a hotel confirmation are different, and one trip can carry several of each.
Sources
- RFC 5322, Internet Message Format (accessed 2026-11-20)
- RFC 2046, MIME media types (accessed 2026-11-20)