After a service is rescheduled, a seat changes or support replies, several files with almost identical names may remain in your inbox. One opens from your gallery, another from the seller’s email, and a companion forwarded a third. The newest message does not always contain a new ticket, and an old code may look just as convincing as the current one. Before boarding, understand what the documents say rather than simply comparing email dates.
These instructions help organise confirmations you already have. They do not describe a universal numbering system: exchange procedures differ between sellers and carriers. If documents contradict each other, obtain final clarification through the official channel for the specific purchase.
Collect the complete set without deleting anything
Open the original purchase email, change notifications and every attachment. Do not rely on the latest search result for “ticket”: an inbox may sort a thread by a new reply that did not change the attachment at all. A file in Downloads may likewise have a recent save date even though it is an old version downloaded again today.
Collect the material in one local folder. Do not erase previous documents: they are needed to understand the sequence of changes and explain the situation to support if necessary. Until the status is clear, do not arbitrarily label a file “valid”. Temporarily identify its source instead: original purchase, rescheduling email, support response.
If another buyer sent the ticket, ask for the complete document, not just the code image, and an explanation of any changes. A forwarded screenshot may predate an exchange. Do not send the whole set back to everyone in the group: establish the current version first, then send each person the documents they need through a private channel.
Make a simple comparison table
Separately note where each version came from and which request it answered. This helps distinguish a resend from actual reissuing. When support can see the sequence of events, it is easier to explain how documents relate without guessing from filenames.
For each file, list the passenger’s name, date, direction, time, boarding point, ticket number and booking number. Add the carrier’s name and section if there is a transfer. If outward and return journeys appear in the same correspondence, separate them immediately. Otherwise, a correct return ticket could be mistaken for an update to the outward journey.
Do not treat booking and ticket numbers as interchangeable. A purchase may remain the same while its documents change. Another process may issue a separate booking or additional confirmation. Your task is not to guess the service’s internal structure, but to record the details you can see and ask a precise question.
A useful table contains only information needed for comparison. Your full passport number, banking details or home address are unnecessary. If the table is in a shared workspace, restrict access. For a family journey, a clear passenger label is sufficient when the full name already appears in the original document.
Distinguish a ticket from an information update
A carrier may update the boarding address without issuing a new PDF. A seller may confirm a change in correspondence and send a new document separately. The same file may also be sent again. Consequently, “the newest email always cancels the previous one” is unreliable: read exactly what changed and how it affects the previous set.
If the message says only “the service is being rescheduled”, establish the new date and time, stop, document required for boarding and status of the previous document. Do not infer missing details from the calendar. A change across midnight is particularly risky because the departure day changes as well as the hour. Ask for both to be confirmed clearly.
Changing one section does not necessarily update every ticket in the journey. If you have several buses, check each separately. Ask whether documents for onward sections remain valid and which connections need checking. Do not apply information about one part of a route to the entire purchase without explicit confirmation.
How to ask support
Send the booking number, date, direction and a short description of the differences. For example: “The first PDF shows departure at 20:00, the second at 21:30, and the latest email mentions a different stop. Please confirm the current time, address and document to show.” That is easier to process than “I have three tickets; which is correct?” without attachments.
Attach the relevant versions through a private official channel and do not conceal details support needs to compare them if those details are genuinely necessary for the check. For public discussion, however, hide codes, the purchase number and personal information. Do not send unnecessary passport pages merely because several documents are mentioned in the correspondence.
Ask for an answer with a specific outcome: which file to open, whether an additional message is needed, exactly what changed and which previous materials should no longer be used for boarding. If staff reply generally, clarify the unclear part. Save the answer beside your ticket so you do not search a long email thread on departure day.
What not to do with files
- Do not combine a code from an old version with the time or address from a new one by editing the PDF.
- Do not replace the surname yourself or remove pages whose purpose you do not understand.
- Do not delete original materials until the journey and all related issues are complete.
- Do not try different codes in turn with different staff members without explaining the situation.
A document you “assemble” yourself does not change system data. Even if it looks tidy, it conceals where individual details came from and makes checking harder. If a new version is needed, the responsible party must issue or confirm it according to its procedures. An original with an explanation is better than an attractive file containing an unverified combination of details.
Do not rename files in a way that loses their history. You can give a folder or copy a clear local name while retaining the original file. After establishing the valid set, separate it from previous materials. Send your companion that set with a short note about its currency, rather than the whole archive without explanation.
Check before leaving for the bus
Open the required document without internet and reread the main details. Compare them with the carrier’s latest confirmed message. If an information update must be kept separately, save it too. Your phone should make clear which material to show when boarding and which is retained only as history.
In a group, check everyone’s documents, not just the purchaser’s file. Rescheduling may have changed the time for everyone, but a further exchange for one passenger may have been a separate transaction. An identical booking number is no reason to assume every attachment automatically has the same status.
If a conflicting new message arrives before departure, verify its source through a known contact. Do not proceed to pay for “new ticket activation” through a random link. A genuine service change does not make every subsequent payment safe. Clarify separately whether an additional payment is required and how it is officially processed.
Questions and answers
Does the current file always have the most recent download date?
No. An old document can be downloaded again today. Compare the content and official confirmation of changes, not just the date in the folder.
If the address changes by SMS, do I need a new PDF?
This depends on the particular carrier’s procedures. Ask which document to present and whether the information message needs to be saved separately.
Can I delete old tickets after support replies?
You can separate them from the current set for convenience, but it is better to keep originals until the journey and related issues are resolved.
What if documents for different sections were updated separately?
Check every section and passenger. Ask which documents remain valid and whether the change affected onward departures.
Useful links
Check official channels on the RedRay website. Additional explanations about documents and boarding are available in the RedRay blog. These instructions do not establish a universal exchange procedure: your ticket requires confirmation from the responsible seller or carrier.