MustMeet Scoring

MustMeet scoring uses AI-generated recommendations and participant preferences to ensure only highest quality meetings and appointments are scheduled.

In this article, we'll cover:

• Overview of MustMeet scoring
• Scoring Matrix - Buyer to Supplier
• Scoring Matrix - Any2Any

Overview of MustMeet Scoring 

In a MustMeet event, Grip calculates ‘scores’ between all participants, which is what allows the system to determine which meetings to book. These scores are based primarily on participant preferences (e.g., ‘Meet’, ‘Must Meet’, or ‘No Thanks’), as well as preferences from any Sharers (participants who are sharing a schedule with a colleague). Additionally, when preferences are missing, the AI-enhanced scoring system also incorporates profile data to help nudge scores within assigned brackets, improving compatibility matching across more participant data points.

These scores are generated in Grip, and are exportable from the ‘Scoring Matrix’ tab in the MustMeet dashboard page, although you will also see them in the MustMeet platform when you’re generating schedules. You can use the tables below for an insight into why certain participants may have higher or lower scores than others.

Please note the following important factors regarding score calculations:

• Scores rank from 0 (no meeting) up to 98 (meeting will be scheduled if possible).
• A ‘No Thanks’ preference outweighs all other metrics, and creates a score of 0.
  This means that if Participant A has chosen ‘No Thanks’ against Participant B, no meeting will be booked - even if Participant B and any Sharers have chosen ‘Must Meet’ against Participant A.
• Similarly, if participants are flagged as having Met Before in a previous event, and no new preferences have been made between them in the current event, a score of 0 will also be generated as it is assumed that they will not want to meet again. The date before which this is calculated can be controlled when generating scores.
• When not all participants in a potential meeting have set preferences, the AI uses both basic profile data and Custom Field data to assess compatibility. This allows the AI to make more nuanced adjustments within the scoring brackets, resulting in more relevant matches based on shared characteristics or roles. When matching custom field data is used to modify the score, you will see a list of the fields and values that matched in the score reasons. You can see this in the score ranges in the matrices below.
• Scores are calculated differently for the two types of MustMeet event; Buyer to Supplier (HB Classic) or Any2Any.
• Buyer to Supplier (HB Classic) events have a slightly stronger weighted group. This is usually the ‘Buyer’ group but can be controlled by adding the stronger group first in the Scoring Matrix page in the Grip dashboard.
  You can also influence scores much more dramatically by preventing a groups from making any ‘Must Meet’ preferences at all, limiting them to just ‘Meet’ and ‘No Thanks’.
• For Buyer to Supplier events where participants that are set up as Sharers have made different preferences against the same person, the ‘stronger’ preference is used, but again with ‘No Thanks’ overruling all other choices. Sharers will always receive the same score as each other. For example:
  • Three Sharers - one chooses ‘Must Meet’, 1 chooses ‘Meet’, one makes no preference = we take ‘Must Meet’.
  • Three Sharers, two say must-meet, one says ‘No Thanks’ = we take ‘No Thanks’.
• There is no way to manually change the scores that have been generated. You can of course manually modify meetings in MustMeet if you want to override the schedule.

Scoring Matrix - Buyer to Supplier

Here we have used the Buyer group as higher-weighted.

Scoring Matrix - Any2Any

Scores are symmetrical as there is no higher-weighted group.