Risk settings
Pick a point on the protection / revenue tradeoff.
A risk setting is the preset that decides how a decision turns into a suggestedAction. It's the single dial you adjust when you want StaySignals to be more or less strict.
The setting controls how much evidence is required for some signals to fire and the score threshold for suggestedAction (allow or deny). A signal's weight stays fixed once it fires. Different settings can produce different scores, while the mapping from riskScore to riskLevel stays fixed.
There are three presets. Wire values are camelCase: maximizeProtection, balanced, maximizeRevenue.
Maximize protection
Deny early. Catches more non-customer bookings at the cost of denying some real customers. Use when the cost of a missed non-customer booking is high — for example, high-value inventory or a property that has been hit hard recently.
Balanced
The default. Deny only checkouts that look clearly non-customer; let ambiguous cases through. Appropriate for the steady state of most OTAs most of the time.
Maximize revenue
Allow aggressively. Deny only the clearest non-customer cases. Use when you'd rather let some non-customer bookings through than risk interrupting a real customer mid-checkout — for example, during a launch or a high-traffic promotion.
How to switch
Change the active preset in the Dashboard under Risk control. Changes apply to future decisions only; past decisions keep the riskSetting they were scored under (and carry it on the decision record).
The Dashboard also shows a projected-impact panel: what each preset would have done if it had been active across your recent traffic. Use it to compare before committing.