Promises are the rules Brella uses to generate a program's meetings. A Meetings and picks promise sets how many meetings and picks a group of participants gets. A Must not meet promise stops Brella from generating meetings between two groups.
Before you start
You need to be an event admin or an organization admin.
Set up the program's two sides first. See Set up a managed meetings program.
Where to find it
During setup: the Promises step.
After launch: the program page, Promises tab.
Both places have 3 tabs: Promises, Affected registrants and Affected companies. In Promises, switch between Picks and meetings and Must not meet to see each kind.
The default promise
When the program's two sides are created, each side gets a default promise covering everyone on that side. Open it and review its meeting, pick and priority-pick numbers before launch.
On a default promise you can change only the numbers of meetings, picks and priority picks. You can't change who it applies to, move it in the list, or delete it.
Create a meetings and picks promise
A promise reads as a sentence: "Everyone in [who] must meet [how many] from [whom]." Select each part of the sentence to open a drawer, set it, and select Done.
Select New promise > Meetings and picks.
Under Side, choose the side the promise belongs to.
Select "Everyone in" to open Who this applies to:
Choose Individuals or Companies.
Under Covered by, choose a level and a target, for example Lists and "Gold buyers". To cover the whole side, leave it empty.
Select Include to add another row. With 2 or more rows, choose All of or Any of.
Select Exclude to take people out, for example one company.
Select "must" to open What they have to do:
Meetings: At least a number, or Between two numbers.
Counted for (company promises only): Each person, or The whole company to share the number between the company's representatives.
Picks: the minimum and maximum picks per person.
Priority picks: the maximum priority picks per person.
Select "from" to open Who counts as a match:
Anyone eligible: anyone on the other side.
Specific people: choose levels and targets, as in step 3.
Optional: set Back this promise with funds.
Select Create promise.
The editor shows an example: "Everyone in Gold sponsors must meet at least 2 · 4–10 picks (max 2 priority) from anyone eligible."
Levels you can choose under Covered by:
Individual promises: Lists, Company categories, Companies, Individual registrants.
Company promises: Company categories, Companies.
The editor calculates initial pick values from the promised meetings. Review the minimum, maximum and priority-pick fields. If you change a number, Reset to <n> restores its calculated value.
Back this promise with funds
Turn on Back this promise with funds to record the value of each promised meeting. Choose the currency under Price per meeting (USD, EUR, GBP, JPY, AUD, CAD, CHF or Credits) and enter the amount. The value shows in the Refunds per meeting column. Brella stores it and doesn't charge or refund anything.
Turn the switch off if you don't track a value. Otherwise, check the currency and amount before saving.
Create a must-not-meet rule
Select New promise > Must not meet.
Select "Everyone in" and choose who the rule covers. Levels include Sides. This part is required.
Select "anyone in" and choose the people they must not meet. This part is required.
Select Create promise.
The table reads, for example, "Everyone in Competitor A must not meet Competitor B."
Must-not-meet rules work in both directions and apply to generated meetings only. People covered by a rule can still see and pick each other in the app. Meetings you arrange by hand and meetings attendees request themselves are not blocked.
How promises apply
Order decides which promise applies. Each side's promises are listed in a table in order. When a person matches several promises of their side, the highest one in the list applies to them. This is their governing promise.
Drag rows to change the order. The default promise keeps its place, so drag the other promises above or below it.
A promise created in the admin panel is added at the top, giving it the highest precedence. Check its scope and the order before continuing.
Check Affected registrants and Affected companies. The Governing promise column shows which promise applies to each person or company.
The governing promise sets the person's limits.
Picks: attendees see the minimum and maximum in the app. They can't pick more than the maximum, or mark more priority picks than allowed.
Meetings: generation books up to the maximum and aims for the minimum. The preview shows who reached their minimum. See Generate meetings for a managed meetings program.
Picks are always counted per person, even under a company promise.
Company promises. A company promise covers the company's representatives on the side. With The whole company, the representatives share one meeting number. A representative whose individual promise is higher in the list follows that promise and isn't counted for the company.
Matches must work both ways. Brella only pairs two people when each is a valid match under the other's governing promise and no must-not-meet rule covers the pair. Picks don't override this.
Edit or delete a promise
To edit, select the promise sentence in the table. Make your changes and select Save promise.
To delete, select Delete on the row and confirm "Delete this promise?". The default promise can't be deleted.
Affected registrants and companies
Tab | Columns |
Affected registrants | Registrant, Side, Picks, Priority picks, Governing promise, Included in promises |
Affected companies | Company, Side, Reps affected, Company picks, Company priority picks, Meetings promised, Governing promise, Included in promises |
These tabs list only people and companies covered by at least one promise.
Settings
Setting | What it does | Default (new promise) |
Side | Side the promise belongs to | None, required |
Individuals / Companies | Counts the promise per person or per company | Individuals |
Meetings | At least or Between | Review the number shown |
Counted for | Each person or The whole company (company promises) | Each person |
Picks | Minimum and maximum picks per person | Calculated from promised meetings; review the fields |
Priority picks | Maximum priority picks per person | Calculated from promised meetings; review the field |
Who counts as a match | Anyone eligible or Specific people | None, required |
Back this promise with funds | Records a value per promised meeting | On; check the currency and amount |
Limits
100 meetings and picks promises and 100 must-not-meet rules per program.
Picks fields accept 1 to 200. The maximum can't be lower than the minimum.
Priority picks can't be more than the maximum picks.
The maximum number of meetings can't be lower than the minimum.
A side's default promise can't be deleted or moved, and only its meeting and pick numbers can change.
Troubleshooting
"Pick a side first."
Choose the side under Side before you create a meetings and picks promise.
"Choose who this promise applies to."
A must-not-meet rule needs at least one row under Covered by.
"Choose who counts as a match." / "Choose who they must not meet."
Open the "from" or "anyone in" part of the sentence and choose an option.
"Choose the specific people who count."
With Specific people, add at least one complete row.
"a program can have at most 100 promises"
The program has reached the limit. Delete a promise you no longer need, or cover more people with one promise.
"default promises cannot be deleted"
Change the default promise's numbers instead, or create a separate promise and check its precedence.
Saving or dragging the default promise shows an error
Only the meeting and pick numbers of a default promise can change. It can't move in the list, and it can't hold a value under Back this promise with funds. Move the other promises instead.
A promise doesn't change the expected limits
Check Who this applies to, the side and the table order. In Affected registrants or Affected companies, read Governing promise. A higher promise may govern, or the person may be outside the promise's scope.