pls_tooltip_button

Predictive lead scoring gives every lead a win probability, computed from how similar leads historically closed. The number on its own invites the obvious question: why that number.

This widget answers it. Clicking the button opens a popover with a progress wheel for the probability and two short lists: the three factors pushing the score up, and the three pushing it down.

Before any of that it saves the record, because unsaved edits, a changed country or source, would make the explanation describe a lead that no longer exists.

Scoring models get ignored when nobody trusts them, and trust comes from being able to see the reasoning. The top and bottom three factors are enough to tell a salesperson whether the model is picking up something real or an artifact of the data.

The factors are also a management signal. If the same field dominates every lead's score, that usually says more about your data entry than about your market.

Placing it

<widget name="pls_tooltip_button"/>

No attributes. It reads the lead from the record.

What the popover receives

probability, team name,
top 3 factors, bottom 3 factors,
the wheel's dash pattern

All from one server call, except the pattern.

Clicking again

# the popover closes; nothing is recomputed

The work only happens on opening.

The sequence on opening is save, ask, reload. The save commits pending edits so the score is computed against what the user actually entered. The server call recomputes the probability and returns the explanation alongside it. The reload pulls that new probability back onto the form.

Between the save and the call sits a guard worth noticing: the widget checks whether it has been destroyed and whether the record still has an identifier. Both can change during an awaited save if the user navigates away, and without the check the popover would open against a component that no longer exists.

The progress wheel is drawn from a dash pattern the widget computes itself. It takes the wheel's circumference from a fixed radius, splits it into a filled length proportional to the probability and a gap for the remainder, and passes that pair to the template.

Right to left layouts get an extra pair prepended, offsetting the pattern by half the circumference so the wheel fills from the correct side. That is the kind of detail that is invisible until you use the product in Arabic or Hebrew.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable and this may still change; we re-verify this page after the release.

A bottom sheet on small screens. The development branch adds the interface service and, when the screen is small, opens the explanation as a bottom sheet rather than a popover. The data and the wheel calculation are unchanged.