Skip to content
  • There are no suggestions because the search field is empty.

Sales App - Subcharter, BCC, and Broker Workflows

This guide provides an overview of the workflows available in the FL3XX Sales App for managing subcharter, broker, and BCC workflows.

Workflow Types and Button Layouts

  1. Subcharter Workflow
  2. Broker Workflow
  3. BCC Workflow
  4. Broker Subcharter Workflow

Each workflow has a distinct set of buttons to simplify the process for different types of bookings. The buttons are divided into two main categories: Customer Buttons and Operator Buttons.

Workflow Details

1. Subcharter Workflow

  • Purpose: To manage subcharter bookings where operators handle customer requests.

  • Button Layout:

    • Customer Buttons: Multi-Quote, Quote, Accept, Sign, Book, Confirm, Manifest, Invoice, Cancel.
    • Operator Buttons: Multi-request, Request, Accept, Confirm, Decline.

  • Button Descriptions:

    • Multi-request: Send requests to multiple operators simultaneously.
    • Request: Send a single request to an operator.
    • Accept: The operator accepts the request.
    • Confirm: The operator confirms the booking.
    • Decline: The operator declines the request.

  • Behavior:

    • When selected, a clear separation between the Customer and Operator buttons is maintained.
    • Buttons are dynamically enabled, disabled, or highlighted based on the workflow state and operator actions.

2. Broker Workflow

  • Purpose: To handle broker workflows created within Avinode or other similar platforms.

  • Button Layout:

    • Broker Buttons: Avinode Search, Decline.

  • Button Descriptions:

    • Avinode Search: Directs users to Avinode to search for available trips.
    • Decline: Decline a request.

  • Behavior:

    • If the Avinode link is unavailable, the Avinode Search button is disabled.
    • The decline button is always enabled.

3. BCC Workflow

  • Purpose: To manage BCC workflows.

  • Button Layout:

    • BCC Buttons: Send to Multiple Operators, Cancel.

  • Button Descriptions:

    • Send to Multiple Operators: Send requests to multiple operators at once.
    • Cancel: Cancel the workflow.

  • Behavior:

    • Both buttons are always enabled and maintain a blue color.

4. Broker Subcharter Workflow

  • Purpose: To manage workflows that are a combination of broker and subcharter processes.

  • Button Layout:

    • Operator Buttons: Accept, Confirm, Decline.

  • Behavior:

    • If the original workflow was Broker or BCC and has been forked into a subcharter workflow, only three buttons (Accept, Confirm, Decline) are shown instead of the standard five.

Additional Features

  • Commission and Margin Functionality:

    • For US customers, commission and user margin details are included, aligning with specific regulatory requirements.

  • Email Communication Adjustments:

    • Email subjects and recipients are dynamically adjusted based on the workflow type. For example, in broker workflows, the recipient changes from "Broker" to "Operator."

  • Aircraft TBA Option:

    • An "Aircraft TBA" button is always visible for quick selection.

General Notes

  • All workflow implementations mimic the logic and functionality of the web app.
  • Different button states (enabled, disabled, highlighted) and colors are determined by the workflow's status and corresponding rules.

Screenshots

Below are the screenshots of the updated interface for each workflow:

  1. Subcharter Workflow:

    Subcharter Workflow

  2. Broker Subcharter Workflow:

    Broker Subcharter Workflow

  3. Broker Workflow:

    Broker Workflow

  4. BCC Workflow:

    BCC Workflow