Additional Contacts
The Additional Contacts setting on an Item controls whether DonorPoint prompts for one or more additional people as part of selecting that item on a form. This is used for event packages where you need to collect registrant names, for auction items where a guest name is required, or for any item where the purchasing donor is registering on behalf of others.
Configuration
Additional Contacts is configured on the Restrictions tab of any Item, in the Assignability section.
| Setting | Description |
|---|---|
| Type | How additional contacts are collected: Fixed (a set number of additional contacts), Open (donor specifies how many), or None (no additional contacts) |
| Minimum | The minimum number of additional contacts required (for Open type) |
| Address Optional | Whether the address field is required for each additional contact |
| Whether to collect an email address for each additional contact | |
| Email Optional | Whether the email field is required or optional |
| Use Existing | Whether to search for and link existing contacts in your database rather than creating new ones |
| Contact Group | If Use Existing is enabled, restricts the searchable contacts to a specific segment |
| Reconcile Contacts | Whether to attempt to match additional contacts to existing records on save |
| Custom Fields | Additional custom fields to collect for each additional contact |
How It Works on the Form
When a donor selects an Item with Additional Contacts configured:
- A section appears on the form prompting for the additional contact’s information
- For Fixed type, the form shows the exact number of additional contact fields required
- For Open type, the donor can add or remove contact entries up to any limit configured
- Each additional contact is linked to the transaction as a separate Contact record
Event Registrations
For Event Packages, Additional Contacts is the primary mechanism for collecting attendee names. Each additional contact entered on the form becomes an Event Registration Instance linked to the transaction. This is how you track who actually attended, not just who paid.
See Events and Event Packages for how this appears in the event context.