Create a scoring and apply it to contacts

Prolibu has a real Scoring module, even though it doesn’t show up in the app’s side menu. To open the scoring list, go directly to /ui/spa/stg/scorings. The Scoring model stores scoringCode, scoringName, type, entity, criteria, bands, normalization, an ai block and active. When a scoring is applied to a contact, Prolibu stores the result in score, scoreBand and scoreDetail.

Before you start: enable scoring on the account

Creating a scoring and applying it are two different things. The switch that turns the module on lives under Account > Preferences > Modules > System > Scoring:

• Entities: the models that can be scored. It’s the preference that feeds the Entity field in the creation panel and its validation, and it comes with Contact.
• Enabled (required): turns native scoring on. With it off you can still create scoring profiles, but nothing gets scored.
• Default scoring: the profile used to score records. This is where a scoring goes from existing to being applied.
• Recompute > On activity: queues an async re-score when a record changes meaningfully.
• Recompute > Periodicity: cron expression for the periodic AI re-score. Empty, there’s no cadence.

Where it’s created

Once the Scorings list is open at /ui/spa/stg/scorings, the floating button in the bottom-right corner opens the creation panel. It sits there as a circle with a plus sign and expands on hover to show its name, New Scoring.

The Create Scoring panel carries these fields in the main section:

• Scoring name (required) and Description.
• Type (required): rules (algorithmic/deterministic), ai (LLM-based) or hybrid (combines both) — that’s how the field’s own tooltip explains it, and those three are the only options in the list.
• Entity (required): the model the scoring applies to. Options come from the account preference (modules.system.scoring.entities), so to see another model here you add it there.
• Assigned to and Collaborators, same as any other Directory record.

On save, Prolibu generates its own Scoring Code with the format SCR-<timestamp> (for example SCR-1787370232330) — no need to type it by hand. Reopen the record and that code sits at the foot of the panel, under PRIMARYKEY: Scoring code, with a button to copy it.

Criteria and bands

The panel has two sections for the scoring’s rules:

• Criteria, meant for the conditions that add or subtract points.
• Bands, meant for grouping score ranges into categories (for example, “Hot” / “Warm” / “Cold”).

Both have an Add button that adds a new row and a trash icon to remove it.

The criteria are defined through the API

In the current version, the Criteria and Bands rows arrive with no fields for typing the criterion’s name, the condition it evaluates, or the points it awards. A scoring saved from this screen ends up with criteria and bands at zero; to load its rules, write them through the API onto the already-created scoring.

Normalization

The Normalization section decides how the sum of points turns into a final score:

• Mode: sumCapped adds the criteria points directly and clamps the result between 0 and 100, or maxPoints, which computes score / Max points × 100. The field arrives empty in the creation panel, but leave it that way and the scoring is saved with sumCapped.
• Max points: the denominator used by the maxPoints mode — doesn’t apply when the mode is sumCapped.

The AI block

Only has an effect when Type is ai or hybrid:

• Skill: the Skill whose prompt acts as the AI’s scoring rubric.
• Provider credential: the AI provider credential used to score.
• Weight: how much the AI score weighs when blended with the rules score, under a hybrid scoring’s “weighted” combine mode (0 to 1).
• Combine: how the rules score and the AI score are merged in hybrid mode.
• Min re score minutes: if the last AI score is newer than this threshold (and the band hasn’t changed), a fresh LLM call is skipped.

Touch none of it and the block is saved with Weight 0.5, Combine weighted and Min re score minutes 30; reopen the scoring and the AI section sums those three values up in its header.

Active and visibility

The Active switch determines whether the scoring is in use, and it comes on out of the box: a freshly created scoring lands with active: true. The Scorings index shows that same switch in each row’s Active column.

Allow everyone has two independent switches, View and Edit, that control whether any user on the account can see or edit that scoring — the same permission pattern as other Directory records. Both come off.

Edit, clone or delete a scoring

In the index, each row’s actions menu (the three-dot icon at the end of the row) offers Edit, Clone and Delete. Edit opens the same panel of fields, now titled Edit Scoring, over the record’s URL; the Criteria, Bands, Normalization, AI and Allow everyone sections arrive collapsed, each summarizing its current values in the header.

Where the result shows up

The Contact model has score, scoreBand and scoreDetail fields to hold the result of applying a scoring. The Lead model has the exact same three fields, though for Lead to show up as an Entity option it has to be added to the account’s Entities preference.