Group visits and attendee-level visit data
Key Takeaway
A group visit is one parent visit for the event plus a child visit for each attendee, so each attendee's samples, product details, and messages are recorded on that attendee's own child visit.
A group visit lets a field user record one interaction, such as a lunch and learn, with several healthcare professionals at once. Salesforce models it as one parent visit for the event plus a separate child visit for each attendee. Because each attendee has their own records, each person's samples, product details, and messages are captured separately.
The parent-child structure
A group visit is a parent-child structure. The parent visit represents the main event and its location. Each attendee gets a child visit, which is a pair of records: a Visit record and a Provider Visit record. The child visit links to the parent visit through a self-lookup on the Visit object, which means one Visit record points to another Visit record.
A child visit needs two records because Provider Visit is an extension object with a strict one-to-one relationship to Visit. Provider Visit stores industry-specific data that the standard Visit object doesn't hold, such as signature status, confirmation flags, and compliance details.
Attendees and visitors are different features. Attendees are healthcare professionals recorded as child visits. Visitors are internal colleagues recorded as Visitor records that link directly to the Visit. The visitors feature automatically shares visit data with them.