For data and Salesforce owners
Look under the hood
You’re the person who will be asked whether these numbers hold up, and whether this package belongs in your org. This page gives you the specifics, with the Salesforce terms used the way you use them.
Data model
A form template defines the questions, and every question belongs to a scoring category. Each completed form is stored as a Form record with one Response record per answer, and a Category Score record per category. Scores and comparisons are calculated when a form is saved, so dashboards read stored values.
OutcomeLens scores in three ways:
- Score-based. Each answer carries points. Points roll up into categories, and each category classifies into tiers your admin defines.
- Value-based. A raw number, such as income or a credit score, classifies directly, with no points step.
- Experience measures. NPS, CSAT, and CES are reported on a shared percent-favorable scale.
Polarity is set per category, so on an instrument where lower is better, a falling score reads as improvement. OutcomeLens ships with no default classifications.
Every form is compared with the participant’s baseline and their previous form. Goals and outcome targets track goal against actual. Templates support form chaining, where a completed form opens the next one, conditional logic, and repeat groups for questions asked more than once, such as one entry per household member.
Where data lives
OutcomeLens is a managed package in the MJRSCO namespace: Apex classes, Lightning Web Components, and custom objects installed into your org from AppExchange. It runs on Nonprofit Cloud, NPSP, and Health Cloud, and it doesn’t need OmniStudio.
Your data stays entirely in your org. Templates, forms, responses, scores, and snapshots are records there, alongside your contacts. Reports are built from those records in the browser when you open them. There is no outside database holding a copy.
Consent and SMS
Participants reach forms in one of two ways, and both use the same templates and the same scoring.
- Experience Cloud guest access. Participants open a link to a form on your Experience Cloud site as guest users. They don’t need a Salesforce license of their own (your org needs an Experience Cloud site license, see pricing), and they don’t sign in. The link carries a token that opens only their form.
- Flow, for staff. A staff member runs the form inside a screen Flow, for example during intake, and the answers are saved the same way.
Invitations go out by email or by text. Texts are handed to your org’s texting service through a delivery Flow. Before any link is created, OutcomeLens checks the person’s text opt-out through Mogli. If they have opted out, or the opt-out can’t be read, nothing is sent, and the reason is logged.
Install and admin
From install to first form, without leaving the app. After you install the package from AppExchange, in-app admin setup walks your admin through assigning permission sets, configuring settings, and reviewing email templates, with no trip to Salesforce Setup.
Form Studio holds the whole form lifecycle on one canvas: pre-fill, questions, branding, logic, repeat groups, scoring, and mapping answers back to Salesforce fields.
The Review Queue keeps participant answers safe when a write can’t finish on its own, such as when an answer matches two existing contacts. OutcomeLens won’t guess. It holds the write, keeps the answers, and your admin resolves it in place.
Want to see it in a real org? Talk with us.