Home โ€บ Blog โ€บ Amadeus RF Command: Received From & Queuing

Amadeus RF Command: Received From & Queuing

A complete guide to the RF command in Amadeus โ€” how to record who requested or provided the information for a PNR and how to use RF for queuing to another office or agent.

A PNR is not just a record of flights and passengers โ€” it is also a record of how the booking was handled. Who made the request? Where did the information come from? Was the change requested by the passenger, by a corporate travel department, or by another office? The RF command is the Amadeus entry that captures this information. It records the source of the PNR update โ€” the person or office responsible for the request โ€” and it can also be used to queue the PNR to another office or to a specific agent. This guide explains what RF does, the syntax for each variation, and when it should be used.

What Does the RF Command Do?

RF is the Amadeus GDS command used to record who requested or provided the information for a PNR.

Category: PNR Elements.

It records the person or source responsible for the PNR update. It can also be used with office and agent information for queuing purposes.

The RF element is documented in the PNR and appears in the PNR history, providing a clear record of the source of the request. This is useful for audits, dispute resolution, and continuity when the booking is handed between agents or offices.

Received From โ€” General

Record that the information was received from the passenger:

RFPSGR

This records that the request or information came from the passenger, without naming a specific individual.

Record that the information was received from a specific passenger:

RFMRMEYER

This records that the request came from the named passenger โ€” in this case MR MEYER. Use this format when it is important to document exactly who provided the information.

Change the Queuing Office

Change the queuing office to another office:

RFMR/MIAAF0234

This queues the PNR to another office identified by its office code, so the follow-up work is handled by the correct location.

Change the queuing office back to your own office:

RFMR/Q

The /Q option returns the queuing office to your own office, which is useful when a PNR was previously routed elsewhere and needs to come back.

Queue to Another Agent

Queue the PNR to another agent in your office:

RF KAY SMITH/-0001AB

This queues the PNR to the specified agent โ€” KAY SMITH โ€” in your office. The agent is identified by name and by the office or agent code at the end of the entry. Use this when a specific colleague should handle the follow-up work on the booking.

When to Use RF

Use RF before ending or updating a PNR to record who made the request or provided the information. Typical scenarios include:

  • Documenting that a change was requested by the passenger.
  • Recording the name of the specific traveller who provided the information.
  • Noting that the request came from a corporate travel department or agency contact.
  • Routing a PNR to another office that must handle the follow-up.
  • Returning the queuing office to your own office after a transfer.
  • Assigning the PNR to a specific colleague for processing.
  • Supporting audits and dispute resolution with a clear record of the source of information.

How RF Fits Into Your PNR Management Workflow

A typical session using RF might look like this:

  • Retrieve the PNR with RT and confirm the changes to be made.
  • Identify who requested the change โ€” the passenger, a corporate contact, or another office.
  • Enter the RF entry with the appropriate source, name, or office.
  • If the PNR should be handled by another office or agent, use the queuing variation of RF.
  • End the transaction with ER or ET to save the change.
  • Review the PNR history with RH if you need to confirm the source was recorded.

How RF Relates to Other PNR Management Commands

  • RF โ†’ records who requested or provided the information for the PNR.
  • RM โ†’ adds a general remark to the PNR.
  • RX โ†’ adds a corporate or business-related remark to the PNR.
  • RC โ†’ adds a confidential remark to the PNR.
  • QE โ†’ places the PNR on a queue.
  • QS โ†’ starts processing a queue.
  • RH โ†’ displays the PNR history, including the RF entry.

The distinction matters: RF records the source of the information and can also route the PNR for queuing, while RM, RX, and RC add remarks about the content of the booking. Use QE for standard queue placement, and RF when the source of the request needs to be documented as well.

Important: The RF element appears in the PNR and in the PNR history, and it may be visible to airlines and partner offices. Keep the entry clear and accurate โ€” it is a documentary record of who provided the information for the booking.

When using RF for queuing, confirm the correct office code or agent identifier before entering the command. Routing a PNR to the wrong office or agent will delay the follow-up work and may require a correction.

Frequently Asked Questions

What does the RF command do in Amadeus?

RF records who requested or provided the information for a PNR. It can also be used with office and agent information for queuing purposes.

What does RFPSGR mean?

It records that the information was received from the passenger, without naming a specific individual.

What does RFMRMEYER mean?

It records that the information was received from the named passenger โ€” in this case MR MEYER.

How do I queue a PNR to another office or agent using RF?

Use RFMR/MIAAF0234 to queue to another office, RFMR/Q to return to your own office, or RF KAY SMITH/-0001AB to queue to a specific agent.

How is RF different from RM or RX?

RM and RX add remarks about the booking itself. RF records the source of the information and can also route the PNR for queuing.

Conclusion

The RF command is the source-of-information tool in Amadeus. Use RFPSGR to record that the information came from the passenger, RFMRMEYER to name the specific traveller who provided the details, RFMR/MIAAF0234 to queue the PNR to another office, RFMR/Q to return it to your own office, and RF KAY SMITH/-0001AB to route it to a specific agent. It supports audits, dispute resolution, and continuity when a booking is passed between colleagues or locations. Always confirm the office code or agent identifier when using RF for queuing, and remember to save the change with ER or ET. Paired with RM, RX, and RC for remark management, QE and QS for queue processing, and RH for reviewing the history, the RF command completes your PNR management toolkit and keeps every booking properly documented.

Focus Keywords

  • RF command
  • Amadeus RF
  • received from element
  • PNR source of information
  • RFPSGR
  • RFMRMEYER
  • RF queuing office
  • Amadeus PNR elements
  • QE command
  • Amadeus PNR management