How do I write scores and segments back to Salesforce?
A score is only useful where reps and automation can see it: on the record, in Salesforce.
Write scores and segments back to Salesforce by putting Fit, Health, and segment on native fields on the Account and Contact, so reps see them on the record, list views and reports filter on them, and Flows can fire from them. A score that lives in a separate tool changes nothing.
This guide covers writing SignalRx scores onto native Salesforce fields through the managed package. Scores are computed from enriched, deduplicated healthcare records and land where your team already works.
Why write back to native fields?
If the score sits in an external dashboard, reps have to leave their workflow to see it, and Salesforce automation cannot act on it. On a native field, the score is part of the record: visible next to the identity and firmographic fields, filterable in a list view, and available to a Flow. SignalRx writes to managed-package fields, so it never overwrites your existing data. Those scores earn their weight because of how they are built: SignalRx scores both accounts and contacts by combining public healthcare data with your own internal signals of revenue, support, and product usage tracked over time, letting inference settle which source to trust, and it does this even for records that arrived sparse by filling their gaps from public sources first. Write-back is the last step that turns those Fit and Health scores, segments, and tags into Revenue Plays and list views your team can act on.
What should be written back?
| Written back | Values | What it powers |
|---|---|---|
| Fit tier and score | High, Moderate, Low, No Fit | Prospecting list views and routing |
| Health tier and score | Expand, Maintain, Triage, At Risk | Retention and expansion plays |
| Segment | Specialty and ownership segments | Reporting and targeting |
| Score reasons | The drivers behind each score | Rep understanding and trust |
How does write-back enable everything else?
List views (clean list views), automation (triggering automation), and reporting all read these fields. Write-back is the hinge between scoring and action.
Illustrative example
Illustrative, based on how SignalRx customers work. A multi-site orthopedics group is enriched from registry, web, and review sources and scored Fit High with a Health tier of Expand. Because the tier and its reasons are written to native fields, the account surfaces at the top of the rep's list view and its Health tier drives an expansion play, all without anyone opening a separate tool.
Key takeaways
- Put Fit, Health, and segment on native Salesforce fields through the managed package.
- Include the reasons so reps understand the score next to the identity and firmographic fields.
- Write-back is what makes list views, automation, and reports work.
See it in action: Discover High-Fit Prospects with SignalRx.
Related: How do I trigger automation from a score? and Fields, Sync, and Permissions Reference
.avif)