Manage deals in Post-Flight phase

The post-flight phase begins when a deal reaches the end of its life cycle. Completed deals have reached their flight end date, expired deals occur when the buying party hasn't responded by the flight end date, and canceled deals result from a rejection. In this phase, you can organize past deals, maintain deal hygiene, and take actions to manage your most valuable deals effectively.

Here's what you need to know about managing deals in the post-flight phase:

• Avoid sending deal notes when deals have reached the end.
• Deals that are completed or rejected cannot be revised. To continue, you must initiate a new deal.
• To maintain deal hygiene and organize your most valuable deals, you can remove expired or canceled deals that the buying party isn't interested in.
• After you remove a deal, it no longer appears in deal queries.

The following sections provide suggestions to maintain deal hygiene by removing deals.

Post-Flight workflows

The following diagram shows actions you can take to improve the hygiene of post-flight deals that are COMPLETED, CANCELED, or EXPIRED.

Remove a deal

You should only remove deals in the post-flight phase. When you remove a deal, it ends communication with the buying party and the deal is no longer visible to you.

IMPORTANT Removing live deals can degrade the experience of all your buying parties and must be clearly communicated beforehand.

Here's what you need to know about removing deals:

• Deal removal is permanent—you can't make view or make changes to a deal after it's removed.
• The dealRemove mutation removes one deal at a time.
• You can remove both commitment and endeavor deals.

The following example dealRemove mutation shows how to remove a deal.

mutation {
  dealRemove(
    input: {
      id: "REMOVE_DEAL_ID_PLACEHOLDER"
      accountId: "ACCOUNT_ID_PLACEHOLDER"
      removedBy: {
        name: "Jane Doe"
        email: "janedoe@example.com"
      }
    }
  ) {
    errors {
      ... on MutationError {
        __typename
        message
        field
      }
    }
  }
}