Digital Connect Check-In supports the possibility to store day-of-travel contact information for all Passengers in order to let the Airlines communicate with the Passengers at the time of flight disruptions.

Agents and/or Passengers are prompted to collect day-of-travel contact information during the check-in flow for all Passengers. Such information is also displayed in the Passenger Details screen under Customer Contact title. Specifically, a mobile phone number is collected with consent to send text messages, and/or an email address to send notifications in the event of travel disruptions.

Note  The Passenger can refuse providing contact details and this information is stored in the PNR.

The feature allows:

• Retrieving contact information using the /dcci/passenger/details service.
• Adding the contact information using the /dcci/passenger/update service.

Returning Day of Travel Data

The /dcci/passenger/details service returns Passenger's and Carrier's phone numbers, and email information in the existing ContactDetails structures (global or on the Passenger level when possible to associate).

Response

The contact details information can be returned on two levels:

• Global level (ContactDetails on Passengers level)
   

  In the global ContactDetails structure the following data is returned:

  • Emails not associated with a Passenger in the PNR

  • Phone numbers not associated with a Passenger

  {
    "reservation": {
      "id": "res1",
      "version": "-2f156d404c26aaf6ca49bfea72ab97f9076ba15a855766e3",
      "passengers": {
        "passenger": [...],
        "contactDetails": {
          "phone": [
            {
              "number": "1234567",
              "type": "HOME"
            }
          ]
        }
      },
      "itinerary": {
        "itineraryPart": [...]
      },
      "recordLocator": "TCHIOD"
    }
  }

• Passenger level (ContactDetails on Passenger level)
   

  In the Passenger's ContactDetails structure the following data is returned:

  • Emails associated with a Passenger in PNR
  • Phones that can be associated with a Passenger
  • Phones mapped from Other Supplementary Information (OSI)

  {
    "reservation": {
      "id": "res1",
      "version": "-2f156d404c26aaf6ca49bfea72ab97f9076ba15a855766e3",
      "passengers": {
        "passenger": [
          {
            "id": "p01.01",
            "syntheticIdentifier": "qJTu6/4y6RTFTznVP23/tVzaBBjnO+xLAzgM29b3VgK3B2+xP+uxNEC5sK1LpO0z",
            "personName": {...},
            "type": {...},
            "contactDetails": {
              "email": [
                {
                  "id": "em1",
                  "value": "PAXA@DCCI.COM"
                }
              ],
              "phone": [
                {
                  "number": "48888777666",
                  "carrier": "ORANGE",
                  "allowedSMS": true,
                  "type": "MOBILE"
                }
              ]
            },
            "emergencyContact": [...],
            "passengerDocument": [...],
            "genericSpecialRequests": {...},
            "ticket": [...],
            "passengerSegments": {...},
            "eligibilities": {...},
            "weightCategory": "ADULT_FEMALE",
            "fiscalCode": "ADT",
            "nameNumber": "01.01"
          }
        ],
        "contactDetails": {...}
      },
      "itinerary": {...},
      "recordLocator": "TCHIOD"
    }
  }

Note  The information is returned only on one level at a time. If it is returned on global level, then it is not returned on the Passenger level and vice versa.

Refusal

The following is data returned as HISTORICAL remark on the reservation level.

{
  "reservation": {
    "id": "res1",
    "version": "-2f156d404c26aaf6ca49bfea72ab97f9076ba15a855766e3",
    "passengers": {...},
    "itinerary": {...},
    "remarks": {
      "remark": [
        {...},
        {
          "id": "remark2",
          "syntheticIdentifier": "Qm5WvUp+6n87hgEgcp437g==",
          "remarkLine": [
            "CUSTOMER DECLINED TO PROVIDE DAY-OF TRAVEL CONTACT."
          ],
          "type": "HISTORICAL"
        }
      ]
    },
    "recordLocator": "TCHIOD"
  }
}

Saving Day-of-Travel Data

Phone numbers added by /dcci/passenger/update service are returned as associated with a specific Passenger, for whom this update has been requested. Infant Passengers are not supported.

The /dcci/passenger/update service collects the following data:

• Mobile number
• Mobile carrier
• Email address
• Indicator whether SMS contact is allowed
• Passenger's refusal of providing Day-of-Travel details.

Error Statuses

The following error status code is introduced and returned in case of some errors in the PNRUpdateReservation response:
UNABLE_TO_ADD_CONTACT_DETAIL.

Examples

• When a Passenger refused providing contact details
   

  Request

  {
    "passengerDetails": [
      {...},
      {
        "contactRefused": true,
        "passengerId": "p04.01"
      }
    ],
    "returnSession": false
  }

  Response

  {
    "results": [
      {...},
      {
        "update": {
          "value": "remark1",
          "context": "RESERVATION_REMARK",
          "operation": "ADD"
        },
        "status": [
          {
            "type": "SUCCESS"
          }
        ]
      }
    ]
  }

• When a Passenger provided new contact details
   

  Request

  {
    "passengerDetails": [
      {
        "contactDetails": {
          "email": [
            {
              "id": "em1",
              "value": "paxA@dcci.com"
            }
          ],
          "phone": [
            {
              "id": "ph1",
              "number": "48888777666",
              "carrier": "Orange",
              "allowedSMS": true,
              "type": "MOBILE"
            }
          ]
        },
        "passengerId": "p01.01"
      },
      {...},
      {...}
    ],
    "returnSession": false
  }

  Response

  {
    "results": [
      {
        "update": {
          "value": "em1",
          "context": "PASSENGER_CONTACT",
          "operation": "ADD"
        },
        "status": [
          {
            "type": "SUCCESS"
          }
        ]
      },
      {
        "update": {
          "value": "ph1",
          "context": "PASSENGER_CONTACT",
          "operation": "ADD"
        },
        "status": [
          {
            "type": "SUCCESS"
          }
        ]
      },
      {...},
      {...}
    ]
  }

• When a Passenger has already the phone number stored but without SMS consent and now they want to add the consent
   

  Request

  {
    "passengerDetails": [
      {
        "contactDetails": {
          "phone": [
            {
              "id": "ph2",
              "number": "48888777665",
              "carrier": "Orange",
              "allowedSMS": true,
              "type": "MOBILE"
            }
          ]
        },
        "passengerId": "p03.01"
      }
    ],
    "returnSession": false
  }

  Response

  {
    "results": [
      {
        "update": {
          "value": "ph2",
          "context": "PASSENGER_CONTACT",
          "operation": "MODIFY"
        },
        "status": [
          {
            "type": "SUCCESS"
          }
        ]
      }
    ]
  

Configuration Reference

The following keys are introduced to support this feature:

• s4ci.feature.passengerDetails.returnPnrDetails
• s4ci.feature.contact.details.channel
• se.adapter.s4ci.configuration.reservationConfiguration.retrieveDetailedInformationEnabled

For more details refer to the Configuration Index chapter.