Booking Requests

Understanding the booking pipeline

The real booking statuses — New, Contacted, Quoted, Converted, Declined — and how they move.

Updated 19 July 2026 · 4 min read

A booking request moves through a small set of statuses from arrival to outcome. The page is Requests in the sidebar (its heading reads Booking Requests).

The five statuses

| Status | Colour | Meaning | | --- | --- | --- | | New | Blue | Just arrived, untouched. | | Contacted | Yellow | You have reached out. | | Quoted | Purple | You have sent a quote. | | Converted | Green | Turned into a job. | | Declined | Grey | Not proceeding. |

There is no "Confirmed" status. The pipeline ends at Converted (it became a job) or Declined (it did not). If you were expecting a "Confirmed" stage between quoting and converting, it does not exist — converting is the confirmation.

Which moves are manual, which are automatic

You can only set three of these by hand: New, Contacted, Quoted. The other two are outcomes, not manual settings:

  • Converted is set automatically when you convert the request to a job. There is no manual "mark converted", and no in-between "accepted but not yet converted" stage.
  • Declined is set by the Decline action.

Once a request is Converted or Declined, it is terminal — the status buttons disappear.

So "move an enquiry to any stage at any time" is not quite right. You move it forward through New → Contacted → Quoted by hand, then either Convert to Job (→ Converted) or Decline (→ Declined).

Where the analytics live

The Requests page itself has no conversion analytics. The conversion funnel — This Month, Converted, Conversion Rate, and a New/Contacted/Quoted/Converted breakdown — is a Booking Conversion card on the main Dashboard, not on the Requests page.

A workflow gotcha

Converting a booking to a job emits a job created event, not a booking-status-changed event. So a workflow watching for booking status changing to converted will not fire on the convert path. Declining a request does emit a booking-status change.

If you want automation on conversion, trigger it on Job Created, not on the booking reaching Converted.

Tutorial: move an enquiry through to a job

A new enquiry arrives and you want to work it correctly through the pipeline.

It starts at New

On Requests, the enquiry is New (blue). This is automatic — you did nothing. It just means nobody has touched it.

Contact them, then mark it

Call or email the customer. Then open the request and click Mark as contacted. The status buttons use the plain status words — this is a manual move, and it is yours to make when you actually make contact, not before.

Send a quote, then mark it Quoted

Once you have sent pricing, click Mark as quoted. You are walking it forward one real step at a time — the status should reflect what has actually happened.

Do not look for a Confirm step

When the customer says yes, there is no "Confirm" to click. The next move is Convert to Job — converting is how a yes becomes real work. See converting a booking to a job.

Converting sets Converted for you

After you convert, the request shows Converted automatically and goes read-only. You do not set that status; the conversion sets it.

Or Decline if it falls through

If they go elsewhere, click Decline instead. That sets Declined, which is also terminal. A declined request is kept, not deleted — see managing incoming enquiries.

Track the rate on the Dashboard, not here

To see how many enquiries you are converting, go to the Dashboard and read the Booking Conversion card. The Requests page is for working individual enquiries; the dashboard is for the numbers.

Can't find what you need?

Our support team is here to help.

Contact support