Engagement Execution

Capture visit details by voice on an iPad instead of typing them manually after each meeting. Switch between attendees and start collecting information in group visits faster. Record consent in more ways, including verbal and paper-based options.

  • Prepare Life Sciences Cloud for a Field Rep’s First Visit
    Use an AI coding agent to take a package-ready Life Sciences Cloud org from initial configuration to a field rep's first visit. The headless workflow configures territories and users, deploys the required metadata, creates minimal test data, and regenerates the mobile metadata cache for synchronization. Field reps get a working Visit foundation on the web, with data prepared for synchronization to an enrolled iPad.
  • Enable Voice-Based Visit Logging (Generally Available)
    Remove the manual effort of logging healthcare provider (HCP) visit details after each meeting. Record HCP engagement details by voice with Visit Agent. Visit Agent processes a field rep's notes on device and populates visit records with product details, messages, reactions, presentations, place, and time, even without an internet connection. Reps can review and edit each visit record before saving. Visit Agent supports only English.
  • Host Twilio Remote Sessions from the Desktop Site
    Field users can now use Twilio to conduct remote sessions with healthcare professionals (HCPs) from their desktop without relying on external video tools. The remote session stays within the context of the visit so that sales reps can capture presentation metrics, device data, and consent or product signatures for each participant. HCPs join remote sessions by using a secure link on any device without installing an app. Previously, remote engagement with Twilio was available only in the Life Sciences Cloud mobile app.
  • Capture Attendee Details Faster in Group Visits
    The Attendee Visit action now appears directly in the Attendees section of the parent visit, making it easier for your field users to start capturing information in group visits. Save the current record and open the next attendee visit in one step by clicking the attendee name button at the top of the Attendee Visit Engagement page. Previously, switching to another attendee required navigating back to the parent visit.
  • Focus Attendee Data Entry on Samples and Marketing Items
    Keep product details and discussions consistent across all attendees in a group visit while supporting per-attendee data entry where regulations require it. Show only the Samples, Direct to Practitioner, and Marketing Items sidebars on the Attendee Visit Engagement page if they’re available. Product details from the parent visit apply to all attendees automatically, so your field users can focus on capturing only the data that's specific to each individual attendee.
  • Request Remote Consent Signatures from Participants on Mobile Phones
    Your field users can request and capture consent signatures from healthcare professionals (HCPs) who join remote sessions on their phones, in addition to product and sample signatures. HCPs review consent topics, opt in or opt out, and provide electronic signatures. Previously, requesting consent signatures required HCPs to join from a laptop or desktop.
  • Capture Consent in More Ways
    Adapt consent capture to every market that your sales reps work in with two new methods—verbal consent or a document reference to a paper form. Make at least one proof a requirement so that no consent goes unbacked, while giving sales reps the flexibility to choose between methods.
  • Access Custom LSC Apps Offline
    Give your field reps immediate access to offline-enabled Life Sciences Cloud (LSC) apps without a prior connected session. During each sync, the Life Sciences Cloud mobile app downloads custom app bundles to field reps' devices.
  • Resolve GraphQL Queries Offline in Custom LSC Apps
    Keep your custom Life Sciences Cloud (LSC) apps working for field reps when their devices lose connectivity. When a rep is offline, the Life Sciences Cloud mobile app resolves GraphQL queries from your custom Lightning web components (LWCs) against the data that's synced to the device.
  • Combine Multiple Components in a Single LSC App
    Build richer, more complex Life Sciences Cloud (LSC) apps for your field reps without hitting the single-app limit in the Life Sciences Cloud mobile app. A single LSC app on the Home Page or on a tab in a Lightning record page can now contain multiple nested custom Lightning web components (LWCs). Design a component one time, such as a list, a card, or a menu, and reuse it across multiple LSC apps.