Nexus-Salesforce Integration Overview

Benefits of the Nexus-SFDC Integration

Quicker / Easier Briefing Requests for Sales team

On average, the Nexus-SFDC integration auto-populates 50% of the fields required for a salesperson to enter a briefing request, cutting the time and effort of submitting a request in half. This, combined with the ease of allowing your sales team to initiate a request right from within their SF workflow makes this a huge boost to efficiency and user experience for your sales.

Accurate Data for Briefing Team

Having the account, opportunity, and contact data pulled directly from Salesforce ensures that the info in the request form is accurate and up-to-date. This allows for the Briefing Managers to spend their time planning and executing a high-level customer experience, instead of chasing down missing or inaccurate information to complete the request form.

Data Accuracy and Accessibility in Nexus

The Nexus-SFDC integration ensures that you are getting full and accurate data for reporting.
The Opportunity Tracking feature also opens up entirely new reporting capabilities, allowing you to measure the impact that the briefing program has had on opportunities in an actual dollar amount.

Visibility and Reporting in Salesforce

By allowing Nexus to send briefing data back up to Salesforce, full visibility of briefing center activity within Salesforce is possible, as well as powerful reporting that combines Salesforce and EBC data.

Integration Features

There are 4 components to the Nexus-SFDC Integration. It is up to each program to decide which of these components should be implemented.

1) SSO Access from SF into Nexus

Allows your sales team to be transferred from SF directly into their main menu in Nexus using Salesforce authentication. This lets users view/update their existing Nexus visits, check availability at a center, and request a non-customer-facing visit. 

2) Initiate Visit Request from SF

This is the core functionality of the Nexus-SF integration. It allows a user to initiate a visit request starting from the account object in SF. Account, Opportunity, and contact object info can all flow directly into a request form in Nexus through this process. 

3) Pull SF Data into Nexus Request Form

Users can lookup their Salesforce accounts, opportunities and contacts while working on a request in Nexus and pull the data directly into the request form or add the data later after the initial request is submitted.

4) Automated Opportunity Tracking

Nexus performs a daily query back to SF to monitor and record updates on opportunity information for Opps tied to briefings. This is crucial to allow for Pre vs Post visit opportunity impact reporting.

5) Push Nexus Visit Data up to SF

Nexus send basic visit data up to SF and stores that data in a new custom object called the Briefing Center Visit (BCV). This also links Accounts, Opportunities, and contacts to this BCV Object giving your SF team access to this data for reporting within SF directly.


SSO Access from SF into Nexus

Link within the App Launcher provides a direct link into Nexus without having to request a visit

This uses SF to authenticate a user into Nexus. If they already have a user account hey will be auto-logged into that account. If they do not have a Nexus account, one will be created for them through this process.

User will land on their main menu in Nexus where they can view/update their existing Nexus visits, check availability at a center, request a non-customer facing visit.

Initiate Visit Request from SF

User initiates the request process from an Account or Opportunity in Salesforce

Intermediary screen allows user to identify Opportunities and Contacts relevant to visit request

Visit Data is passed from SF into Nexus based on field mapping configuration

User is authenticated and transitioned into Nexus, directly into the request form. Custom welcome message can Nexus defined for users.

Once a date is selected and a Visit ID is assigned, the SF data is pre-populated into the request form in the corresponding fields om each screen

Pull SF Data into Nexus Request Form

Users can lookup their Salesforce accounts, opportunities and contacts while working on a request in Nexus and pull additional Saleforce data directly into the request form.

Each of the corresponding screens in Nexus have a button that allows the requester to lookup and retrieve their Salesforce data.

This option is also available after the initial request has been submitted, allowing requesters to update the attendee list with their Salesforce contact data.

Automated Opportunity Tracking

Nexus automatically synchronizes opportunities values with SF to gather updates Opportunity tracking and reporting.

Nexus seeks updates on all Opportunities with a valid Salesforce Opp ID that are not yet closed, and has the ability to track changes in opportunity values from pre —> post engagement.

This pre—>post visit opportunity values drive some powerful Opportunity Impact reports within Nexus...

Nexus Visit Data Sent to SF

Once a Visit is requested, Nexus can send the visit data up to Salesforce, where it is stored in the Engagement Object.

The Accounts, Opportunities, and Contacts associated with this visit are linked as Related SF Objects.

A SF Event can also be auto-created for the briefing and linked to the Account/Opportunity.


All the data sent from Nexus is available in Salesforce reporting, with Sales Impact Dashboard included in the package.