Joint visits with internal attendees and team visit sharing
Key Takeaway
Internal colleagues who join a visit are saved as Visitor records, and adding them shares the visit with them. To let field users add visitors without read access to the User object, use the Related List - Life Sciences component with the logAVisitVisitorPicker action handler, which creates visitor records in system context. Then activate the VisitorShareHandler trigger handler.
Field reps often visit healthcare professionals together with colleagues such as their manager. Reps who cover the same accounts also need to see each other's past interactions. In Agentforce Life Sciences, Visitor records capture the internal colleagues who took part in a visit and share that visit with them. Visit sharing gives reps access to visits for the accounts they can reach through territory alignment or manual account sharing.
Attendees, visitors and visit sharing
Visit Management offers three collaboration features that are easy to confuse:
- Attendees add multiple healthcare professionals to one group visit.
- Visitors record internal colleagues who take part in a visit.
- Visit sharing lets field reps see previous interactions that other reps have had with accounts in their territories.
A group visit, such as a lunch and learn, uses a Parent Visit for the main event. Each healthcare professional attendee gets a child visit made of a Visit and Provider Visit pair. The child visit links to the Parent Visit through a self-lookup on Visit. Internal colleagues are captured as Visitor records instead.
A rep hosts an evening talk for four oncologists, and her district manager comes along. The evening talk is the Parent Visit. Each oncologist gets a child visit, which is a Visit and Provider Visit pair linked to the Parent Visit. The district manager is an internal colleague, so the rep adds him as a Visitor record instead.