Convert a PNR by Forwarding the Email — No Copy-Paste Needed

Every agent knows the routine: a booking confirmation lands in your inbox, and before a client sees anything, you have to log into the GDS, pull up the record, copy the raw PNR text, switch tabs, paste it into a converter, and only then does a readable itinerary exist. It's maybe two minutes of work. It's also two minutes you repeat dozens of times a week, usually while juggling three other things.

PNRGenius now skips the GDS step entirely. If a booking confirmation email is already sitting in your inbox — from your GDS's auto-notification, from the airline, or forwarded to you by a colleague — you can turn it into a client-ready itinerary without opening a terminal, without copying anything, and without even being at your desk.

How It Works

The idea is deliberately simple: forward the email, get a link back. There's nothing to install, no account to create, and no app to open on your phone beyond the one you already use for email.

1. Forward the booking confirmationOpen the email containing the raw PNR or booking confirmation and forward it to parse@mail.pnrgenius.com.
2. Wait a few secondsPNRGenius reads the email, pulls out the booking text, and sends a reply to the address you forwarded from.
3. Open the replyThe reply contains a single link and nothing else to configure or click through.
4. Click the linkIt opens PNRGenius with your PNR already pasted in and already converted — passengers, flight segments, times, layovers, the works, exactly as if you'd pasted it in yourself.

Why Forward Instead of Paste?

Copy-paste isn't hard. But it assumes a specific set of conditions: you're at a computer, you have the GDS terminal open, and you have a spare browser tab. Email-forwarding removes all three of those assumptions.

• Works from your phone. Forwarding an email and tapping a link are both things a phone does natively — no separate app, no mobile GDS client.
• Works away from the GDS. If a client's confirmation lands in your inbox and you're not near your terminal, you don't need to be. The email itself has everything the converter needs.
• Works for anyone on the team. A junior staff member handling client communication doesn't need GDS access at all to turn a confirmation into something presentable — they just need to be able to forward an email, which they already know how to do.
• No new habit to learn. "Forward this email" is a muscle memory most people already have. There's no new interface to get used to.

What Kind of Emails Work

Anything that contains the raw PNR or GDS booking text works — the format PNRGenius already reads when you paste it directly. That includes:

• Your GDS's own auto-generated booking confirmation, if it includes the raw PNR text in the body
• An email a colleague forwarded to you that still has the original PNR text intact further down the thread
• A confirmation you saved to yourself after pulling it from the terminal

PNRGenius auto-detects the GDS format the same way it does on the main converter — Amadeus, Sabre, Galileo, and Worldspan are all supported, so you don't need to tell it which system the booking came from.

When Forwarding Doesn't Work Cleanly

Email forwarding handles the vast majority of booking confirmations without a hitch, but it isn't magic — it still needs the raw PNR or GDS-formatted text to be present somewhere in the email body as selectable text. A handful of situations trip it up, and it's worth knowing what they are so you're not left wondering why a link didn't come back the way you expected.

• Screenshots instead of text. If a supplier or a colleague sends a photo or screenshot of a booking rather than the actual email text, there's nothing for the parser to read — an image isn't text, no matter how clearly it's captured. Ask for the original confirmation email instead, or fall back to pasting the PNR manually if you have it.
• Heavily reformatted supplier confirmations. Some OTA-style or consolidator confirmations strip out the raw GDS record locator format entirely and replace it with their own custom layout. If the email never contained GDS-style PNR text in the first place, forwarding it won't produce a GDS conversion — for these, the Itinerary Builder is usually a better fit since it doesn't require GDS-formatted text at all.
• Digest emails covering multiple bookings. If one email bundles several unrelated PNRs together — common with group business or back-to-back bookings for the same client — the parser reads the whole email, so results can be inconsistent. Splitting the bookings into separate forwards, one PNR per email, gives cleaner results.
• Deeply nested reply chains. A confirmation that's been forwarded three or four times, with each hop adding its own quote markers and signature block, can bury or fragment the original PNR text. If a forward like this doesn't come back clean, go back to the earliest, least-forwarded copy of the email you can find.

Group Bookings and Multiple PNRs in One Thread

Large groups are frequently split by the GDS into more than one PNR once the party size crosses a carrier's threshold, even though the booking started as a single request. If a confirmation email mentions more than one record locator, or references a second reservation, check the original email for every locator involved — forwarding it will convert whichever PNR text is present, which may only be one part of the group. When in doubt, pull each PNR from the GDS individually and confirm you've accounted for every passenger before sending anything to the client.

Is It Secure?

Nothing about this requires handing over GDS credentials, creating an account, or storing your data long-term:

• The system only reads the email you explicitly forward to it — it never reaches into your inbox on its own.
• The converted-link is single-purpose and expires after 1 hour.
• No login, password, or personal account is created or required at any point.

A Practical Example

Say a client's flight confirmation for a Karachi–Lahore booking on PIA lands in your inbox while you're out of the office. Instead of making a mental note to convert it once you're back at your desk:

1. Forward itTap forward on your phone, address it to parse@mail.pnrgenius.com, send.
2. Get the replyWithin moments, a reply lands with your link.
3. Send the client their itineraryOpen the link, and the full itinerary — airline, flight number, route, times, layover detection, even a PNR Health Check flag if something like a missing ticketing deadline needs attention — is sitting there ready to copy, email, or download as a PDF.

What used to require being at a desk with a GDS terminal open now takes about as long as forwarding any other email.

Before You Hit Send: A Pre-Send Checklist

The conversion itself is reliable, but "reliable" doesn't mean "unsupervised." A forwarded email is still just a fast path to the same converted itinerary you'd get from pasting — and the same quick check you'd give any itinerary before it reaches a client is still worth doing here.

• Passenger name spelling. Confirm it matches the passport exactly, especially with names that have alternate transliterations — a forwarded confirmation reflects whatever was typed into the GDS, errors included.
• Dates and layover math. Overnight and multi-day itineraries are where layover timing most often looks wrong at a glance; a quick check of arrival versus departure dates catches this before the client does.
• Ticketing deadline. If the PNR carries a time limit, make sure it's visible and hasn't already passed by the time you're sending the itinerary along.
• Fare class flags. If a segment is flagged for a restrictive fare — Basic Economy or similar — decide whether that needs a note to the client before they're surprised by it at the airport.
• Status codes. A segment showing HL or KL (waitlisted) rather than HK, KK, or TK (confirmed) is worth flagging explicitly rather than letting the client assume everything is locked in.

Setting Up an Inbox Rule for the Busiest Suppliers

If a particular supplier or your GDS's own auto-notification address sends you booking confirmations constantly, it's worth setting up a simple forwarding rule rather than manually forwarding each one.

IF sender contains "@yourgds-notify.com"
   OR subject contains "Booking Confirmation"
THEN forward a copy to parse@mail.pnrgenius.com

Most email clients — Gmail's filters, Outlook's rules, or the equivalent in whatever you use — support this kind of "forward a copy automatically" rule. It doesn't remove the review step above; you'll still want to open the reply link and run through the checklist before anything reaches a client. What it removes is the step of remembering to forward in the first place, which is often the part that gets skipped when things get busy.

Getting Started

There's no setup on your end — the address is live now. The next time a booking confirmation email lands in your inbox, forward it to parse@mail.pnrgenius.com and see the converted itinerary for yourself.