AirScalp does not treat “cheap” as a complete instruction. A flight rule combines itinerary requirements, price limits, timing, and an action mode. The rule must pass as a whole.
Trip controls
- Origin and destination airports, including acceptable alternatives
- Exact travel dates or a flexible date window
- One-way or round-trip itinerary
- Number and type of passengers
- Cabin and allowed number of stops
- Maximum trip duration and minimum connection time when supported
Price controls
The target fare is the desired price. The hard maximum is the highest permitted total for the rule. The booking workflow must not treat the target as permission to exceed the maximum because of taxes, fees, or a price change.
Invited users should review whether a rule compares base fare or displayed trip total and how optional baggage or seat charges are handled before enabling action.
Action modes
- Alert only sends the match without preparing a purchase.
- Approval required waits for the traveler to confirm the current itinerary and total.
- Automatic booking may attempt the transaction after all saved conditions pass.
Time and stop rules
A monitoring rule needs an expiration date. Booking-enabled rules may also restrict action to a time window. Users can pause a rule at any time, and a confirmed purchase should stop it automatically.
Start with a narrow alert-only rule, inspect its matches, and expand automation only after the rule behaves the way you expect.