What is Proof Recommender?
After a Gong call or a Salesforce opportunity advances stage, Proof Recommender analyzes the available context and delivers a curated set of recommended proof assets to the rep through their connected channels — Slack DM, email, and/or the Salesforce opportunity record.
The result: reps follow up faster with stronger, more relevant proof.
Requirements
Gong — required for call-triggered recommendations (runs off call transcripts)
Salesforce (optional, recommended) — enables opportunity enrichment, SF stage advance as a trigger, and automatic writeback of recommendations to the opportunity record
Slack (optional) — enables Slack DM delivery of recommendations
How it works
Every time a deal moment occurs, Proof Recommender runs an automated loop:
A trigger fires. A Gong call wraps, or a Salesforce opportunity advances stage.
The Recommender builds context. It pulls available signals: the call transcript (Gong), the opportunity's industry, company size, and stage (Salesforce), or both when applicable.
AI ranks the proof library. Semantic matching does most of the work; Salesforce firmographics boost matches when present.
The top recommendations are delivered. Pushed to the rep through whichever channels their account has connected — Slack DM, daily email digest, and/or the Salesforce LWC on the opportunity record.
The rep acts. They open the recommendations, click into the proof, and use it — share with the prospect, attach to a follow-up email, or build a one-pager in Deal Page. Every view and click is logged for reporting.
Where to find it: Slack DMs, email inbox, and the UserEvidence Content Recommendations tab on the Salesforce Opportunity record page. Notification settings are managed in the UserEvidence web app.
Trigger Exclusivity Rule
When Gong is connected, Gong is the only trigger. Salesforce deal data still flows in as context for matching. Salesforce stage advances only trigger recommendations when Gong is not connected. This prevents reps from receiving duplicate recommendations from both paths.
Experience by Integration Mix
Integration Mix | Trigger | Recommendation Context | Delivery |
Gong + SF + Slack | Gong call | Gong transcript + SF deal data | Email digest + Slack DM + SF LWC writeback |
SF + Slack | SF stage advance | SF deal data | Email digest + Slack DM + SF LWC writeback |
Gong + Slack | Gong call | Gong transcript | Email digest + Slack DM |
Gong + SF | Gong call | Gong transcript + SF deal data | Email digest + SF LWC writeback |
Gong only | Gong call | Gong transcript | Email digest only |
SF only | SF stage advance | SF deal data | Email digest + SF LWC writeback |
Every configuration receives email at minimum. Salesforce, where present, always adds SF LWC writeback. Slack is a delivery upgrade.
Notification Preferences
Contact your Customer Success Manager to manage account-level notification preferences. Individual reps can override these settings for themselves from their in-app settings page using three toggles:
Slack DM — recommendation lands as a direct message in Slack
Digest Email — once-daily email consolidating all recommendations from the past 24 hours
Individual Email — one email per triggering event
Defaults: Slack ON, Digest ON, Individual OFF.
Preferences are checked at send time. If Slack is off, no Slack DM is sent — there is no fallback to another channel. A silent fallback to email occurs only when delivery itself fails (for example, the Slack user can't be resolved). Empty digests are never sent — if there are no triggering events in the past 24 hours, the digest doesn't send.
Recipient Resolution
For Gong-triggered recommendations, the recipient is resolved using Gong's call host/organizer metadata — the recommendation goes to the rep who owns the deal, not every internal attendee on the call. An account-level allow list is available as an override for accounts where host metadata doesn't reliably reflect deal ownership.
The Salesforce Managed Package
UserEvidence for Salesforce is delivered as a managed package. Salesforce admins can install it using the standard Salesforce package installation process. Download the managed package here and find installation instructions here.
Salesforce admins should add the following two Lightning Web Components to the Opportunity record page:
UserEvidence Content Recommendations — the recommendations surface. Calls the UserEvidence API and displays the top recommendations for the deal. Reps view, click, and log engagement from here.
Customer Evidence — the embedded microsite. Renders an iframe driven by the
Opportunity_Assets__cfield. When UserEvidence pushes a microsite URL to that field from the Proof Recommender, the component embeds the microsite inline on the Opportunity record.
The package also includes:
Two permission sets for least-privilege access:
UserEvidence Userfor end users (sales, marketing, RevOps) andUserEvidence Perm Setfor the integration user and adminsA packaged External Client App configured for OAuth Client Credentials — secure server-to-server access without per-user OAuth
Protected custom setting for the UserEvidence API key, scoped so only admins can manage it
An admin-only
Microsite_Generation_Outcome__cfield on the Opportunity that logs the timestamp, HTTP status, and detail of the most recent enrichment callout — the first place to look when a microsite fails to populate
Engagement Tracking & Reporting
Every view and click of recommended content is logged to a packaged custom object (Content_Engagement__c). Each record captures the opportunity, the user, the content asset (ID, title, type, URL), the action (view, click, or share), and the timestamp.
Five reports ship in the package, in a UserEvidenceReports folder:
Content Performance — which assets are getting engagement
Content Usage by Opportunity — what proof is showing up on which deals
Conversion Rate With Engagement — win rate for deals where reps engaged with UserEvidence content
Conversion Rate Without Engagement — the comparison baseline
ROI Attribution — pipeline impact tied to UserEvidence content engagement
A UserEvidenceDashboards folder ships with a dashboard built on top of these reports. Salesforce admins need to share both folders with RevOps or marketing to grant visibility. Defaults are restrictive, so reports remain invisible until a Salesforce admin explicitly shares them.
Privacy note: Engagement tracking captures user, opportunity, and content interaction data. Customers in regulated industries may want to review this internally before broad rollout — worth discussing during the install call.
FAQ
Do reps have to log into UserEvidence to use Proof Recommender?
Do reps have to log into UserEvidence to use Proof Recommender?
No. Recommendations are delivered via email and Slack DM, and viewable on the Salesforce opportunity record, so reps can access proof without logging into UserEvidence.
What if we don’t use Salesforce?
What if we don’t use Salesforce?
You can still use Proof Recommender with Gong alone. Salesforce is optional, but it adds opportunity enrichment, SF stage advance as a trigger, and writeback so the deal team can access recommendations directly on the opportunity.
What if we don't use Gong?
What if we don't use Gong?
Proof Recommender can still run using Salesforce opportunity stage advances as the trigger. Gong is not required, but without it, recommendations will be based on Salesforce deal data only — not call transcript content.
What happens if a Gong call isn't linked to a Salesforce opportunity?
What happens if a Gong call isn't linked to a Salesforce opportunity?
Proof Recommender can still send recommendations based on the transcript, but won't be able to enrich recommendations with opportunity context or write back to Salesforce.
Who should enable Proof Recommender?
Who should enable Proof Recommender?
Proof Recommender works best for teams with consistent Gong and/or Salesforce usage, a strong collection of assets in UserEvidence, and a desire to reduce rep search time and improve proof consistency in follow-ups.
Is Proof Recommender available in Slack?
Is Proof Recommender available in Slack?
Yes — when Slack is connected, recommendations are delivered as a Slack DM in addition to email.