Skip to main content

Request Confirmations

Send, Track, and Manage Service Approvals

Jessi McCombs avatar
Written by Jessi McCombs
Updated this week

Request Confirmations help FBOs make sure service requests are clearly reviewed and acknowledged before work begins. By sending a confirmation to crew or operators and tracking their response, teams can reduce misunderstandings, improve accountability, and keep everyone aligned.

With Request Confirmations, you’ll always know whether a request is pending, confirmed, or rejected—all in one place.


What Request Confirmations Do

When Request Confirmations are enabled, you can:

  • 📧 Email a service request confirmation to a selected contact

  • ✅ Require recipients to review and accept your Terms & Conditions

  • 📊 Track confirmation status directly on the request

  • 🕘 View a full audit history showing who confirmed or rejected—and when

  • ⚠️ Continue working even if a request is pending or rejected (with clear warnings)

Note: Request Confirmations apply to the entire request, not individual services.


How to Enable Request Confirmations

To turn on Request Confirmations:

  1. Go to FBO Settings > FBO Profile

  2. Select the Request tab

  3. Enable Email Request Confirmation

  4. Enter and save your Terms & Conditions

Terms & Conditions are required when this feature is enabled.
🔄 After saving, users must log out and log back in for the change to take effect.


User Role Permissions

To access settings to enable or make changes for Request Confirmation feature the following user role permissions are required:


Sending a Request Confirmation

Once enabled, sending a confirmation is simple:

  1. Create or open a request

  2. Add at least one service

    • The confirmation option won’t appear until a service is added

  3. Add a Requester contact

    • Only one requester is allowed per request

  4. Select Send Request Confirmation

  5. Save and send

The requester will receive an email with a secure link to review the request and respond.


What the Recipient Sees

The confirmation email includes:

  • Request number and creation date

  • Aircraft details

  • Arrival and departure dates and times

    • These display estimated or actual times, depending on availability

  • A secure link to view full request details

  • Your Terms & Conditions (acceptance required)

Recipients can then:

  • Confirm the request

  • ⚠️ Reject the request and provide a reason

    • For example: incorrect services or a schedule change


Understanding Request Status Icons

After a confirmation is sent, you’ll see status icons on the request:

  • 🕒 Pending – Sent but not yet confirmed

  • Confirmed – Accepted by the recipient

  • ⚠️ Rejected – Rejected with a recorded reason

Hover over the icon to see additional details, including timestamps and notes.


Making Changes After Sending a Confirmation

If you update services, quantities, or arrival/departure details after a confirmation is sent:

  • ⚠️ A warning appears indicating the request has changed

  • The previous confirmation is no longer valid

  • A new confirmation must be manually sent

If a request was already confirmed, changes do not automatically re‑notify the recipient.

If a request is rejected, it stays rejected until a new confirmation is sent.


Working With Pending or Rejected Requests

Request Confirmations are informational, not blocking:

  • Services can still be completed even if a request is pending or rejected

  • Clear warnings help users stay aware of the current status

  • All actions are recorded in the audit history

This ensures flexibility while keeping teams fully informed.



Best Practices

To get the most value from Request Confirmations:

  • Send confirmations after all services are added whenever possible

  • Re‑send confirmations if any service details change

  • Encourage recipients to review details carefully before confirming

  • Use rejection reasons to guide corrections and follow‑up


Need more help? Contact X-1FBO Support for further assistance.

Did this answer your question?