Skip to content
  • There are no suggestions because the search field is empty.

MustMeet Cheat Sheet

A list of some important points to remember

In this article we will walk through some of the basic rules of MustMeet to give you a better understanding of the platform and help answer some general questions.

MustMeet only generates meetings for available time slots

The MustMeet platform only generates meetings for available time slots. If an event has six time slots and the participant is busy for two of them, the participant will only get four pre-scheduled meetings. This means, if a participant blocks out a large amount of time within their calendar, this could impact the number of meetings generated for them.

If one participant says "No thanks" to another participant, a meeting will not be scheduled

If a participant makes a "No thanks" preference on another participant, they will be scored as a '0' and no meeting will be generated between them. Any other score can result in a meeting, if there are enough slots to meet.

The MustMeet scheduler will try to create as many meetings as possible

The number of meetings at an event depends on a few factors:

  • No. of "0" scores (from 'No Thanks' preferences, "Met Before" or from using the 'Mutual preferences only' score modifier)

  • No. of participants (considering the balance between groups)

  • Participant availability

  • Participant meeting limits

  • No. of meeting slots

You can increase the number of meetings by modifying these - for example, adding additional time slots to your locations, or finding more suppliers to meet all your buyers.

Scores are primarily based on Preferences

Participants that make more (positive) preferences to other participants will naturally get higher scores on average. Less-engaged participants will get lower scores (and potentially fewer meetings) as there is less data to base scores on. AI-scoring works to try to improve these scores where possible, but it cannot replace participant preferences entirely.

Custom field data must be configured from participant to participant in order to be useful for scoring

When calculating scores, we can use Custom Fields to give richer data to the AI to help with scoring. However these custom fields must be assigned to and shared by the Participant data types on both sides. They cannot be inferred from Company relationships.

Participants without scores will not recieve meetings

When adding new participants to a MustMeet event that's already in progress, remember to re-run the scores so that they can be calculated between the newcomer and all the existing participants.