Approvals Overview

The directive for Ops Support is to automate all travel approvals. Anytime there is a manual approval on the advisor side, the AM will be contacted to consult with the client about automated options available for them.  

Below is a synopsis of what can currently be handled via automation and what cannot. Please advise GDS Support If there is something that currently works that is not listed, or if something is missing that should be added.

• Concur Approval - native tool built within Concur for use with the online booking tool (See more here).

  • NOTE: Very robust set of tools and configuarations that aren't always available/possible for us to enforce within the advisor booking flows.

• Deem Approval - native tool within Deem that includes some basic rules (See more here).

  • NOTE: We currently don't recommend implementing Deem's approval tool. We recommend use one of AirPortal's approval options

• AirPortal Approvals - proprietary tools that have different capabilities around rule configurations and notification options for messages sent to approvers.

  • V2 Approvals (See more here)

  • V3 Approvals (See more here)

Ops will be partnering with Training so advisors can provide better client/customer support. This includes working a request immediately and sending the approval out to allow as much time as possible for the approver to review and better consulting on calls to advise travelers that an approval is required and for traveler to make sure approver is available.

AMs can help by consulting with clients and educating them on why approval policies are like this – to protect the fares and save them money! Things to consider: Are they able to create a distribution list that contains multiple approvers, so  that it gives them a wider berth of hours as well as coverage if someone is out of the office?

Notifications currently use the same system as approvals, so the same rules listed above apply.