Referral Management
Referral Management in Salesforce Industries is a feature set inside Financial Services Cloud, Health Cloud, and Public Sector Solutions that tracks the lifecycle of a referral between parties: from intake (a doctor referring a patient to a specialist, a financial advisor referring a client to a wealth manager, a caseworker referring a citizen to a partner agency), through follow-up (was the referral acted on, was the visit scheduled, was the case opened), to outcome (was the referral successful and what was the result).
Definition
Referral Management in Salesforce Industries is a feature set inside Financial Services Cloud, Health Cloud, and Public Sector Solutions that tracks the lifecycle of a referral between parties: from intake (a doctor referring a patient to a specialist, a financial advisor referring a client to a wealth manager, a caseworker referring a citizen to a partner agency), through follow-up (was the referral acted on, was the visit scheduled, was the case opened), to outcome (was the referral successful and what was the result).
The feature builds on the Account, Contact, Opportunity, and Case data model, adding industry-specific Referral records that capture the referring party, the receiving party, the reason for the referral, the timing requirements, and the consent or privacy considerations that apply. Each industry cloud customizes the referral schema for its regulatory context (HIPAA for healthcare, FINRA-style suitability rules for financial services, FOIA-style transparency for public sector).
Referral Management in Salesforce Industries: data model, lifecycle, consent, and reporting
The Referral data model across industry clouds
All three industry clouds (Financial Services, Health, Public Sector) share a common Referral object pattern, with industry-specific extensions. The Referral record carries the referring party (the user, contact, or account that made the referral), the receiving party (who the referral is for), the reason or specialty needed, the priority level, and the consent record that authorized the referral. Health Cloud adds HIPAA-compliant audit fields and links to clinical record types. Financial Services Cloud adds suitability check fields and client objective links. Public Sector Solutions adds case linkage and agency-to-agency authorization fields. The shared structure means a team familiar with one industry cloud referral model can pick up another relatively quickly; the specifics differ, but the bones are the same.
Referral lifecycle and the status workflow
A Referral record moves through a defined status workflow. New (just submitted, not yet acknowledged) becomes Acknowledged (the receiving party has accepted the referral into their queue) becomes In Progress (an appointment is scheduled, a meeting is set, a case is opened) becomes Completed (the outcome is recorded). Some referrals branch to Declined (receiving party rejected) or Cancelled (referring party withdrew) or Expired (deadline missed). Each transition triggers configurable automation: notify the referring party of status changes, escalate stalled referrals to a supervisor, fire a task to follow up. The lifecycle is the operational backbone of the feature; without it, referrals fall through the cracks at scale.
Consent, privacy, and regulatory considerations
Referral Management sits at the intersection of multiple regulatory regimes. HIPAA requires patient consent before clinical information leaves the originating provider. Financial Services Cloud has client-suitability rules under FINRA and SEC oversight. Public sector referrals involve FOIA-style transparency and inter-agency data sharing agreements. Each Referral record links to a Consent record (or its equivalent) that captures what the consenting party authorized: which information can be shared, with whom, for what purpose, and for how long. The platform automated audit log records who accessed the Referral record, when, and what they viewed. Compliance teams use these audit trails for periodic reviews and for incident response when access patterns look anomalous.
Integration with Account, Contact, and Care Plan or Financial Goal
Referrals do not live in isolation. Health Cloud links each Referral to the patient Care Plan, the provider Account record, and any related clinical records (Encounters, Medications, Care Programs). Financial Services Cloud links each Referral to the client Financial Account, Financial Goal, and any related Opportunity records. Public Sector Solutions links to the citizen Person Account, the partner agency Account, and any active Cases. These linkages let users see the full context of a referral without jumping between records, and let reporting roll up referrals into program-level metrics (referral volume per care plan, referral conversion rate per advisor, partner agency engagement). The cross-record context is what turns Referral Management from a simple workflow into a strategic feature.
Reporting, throughput metrics, and operational dashboards
Referral Management is heavy on reporting because the volume and the regulatory pressure require visibility. Standard reports cover: referrals opened this week by source and destination, conversion rate from referral to scheduled visit (or scheduled meeting, or opened case), median time-to-acknowledge per receiving party, percentage of referrals that escalated to supervisor, and referrals at risk of expiring. Mature implementations build dashboards per role: caseworker dashboards showing pending referrals owed acknowledgement, supervisor dashboards showing team throughput and SLA adherence, executive dashboards showing program-level outcomes. The dashboards drive the operational rhythm; without them, referral teams operate blind.
External referrals and partner integration
Many referrals cross organizational boundaries: a hospital referring to an external specialist, a financial advisor referring to a partner firm, a caseworker referring to an outside agency. Salesforce Industries supports external referrals through three patterns. First, partner-to-partner integration through Direct Messaging (Health Cloud), Open Banking APIs (Financial Services Cloud), or government interoperability standards (Public Sector). Second, Experience Cloud portals where external partners log in and receive referrals through a Salesforce-hosted UI. Third, file-based exchange where referrals export to a structured format (CDA in healthcare, custom XML in financial services) and import into the partner system. Pick the integration pattern based on the partner technical maturity; do not assume everyone has API capability, especially in healthcare and public sector.
Standing up Referral Management in an industry cloud
Standing up Referral Management is a multi-week project that combines platform configuration, regulatory consultation, and partner coordination. The work splits into four phases: install the relevant industry cloud and enable Referral Management, design the referral data model and status workflow for your context, configure consent capture and audit logging, and build the reporting that runs the operation. Each phase touches different stakeholders (admin, compliance, business operations, IT), so plan the project with shared ownership and a clear escalation path for any phase that stalls.
- Install the industry cloud and enable Referral Management
From Setup, install Financial Services Cloud, Health Cloud, or Public Sector Solutions if not already in the org. Navigate to the industry cloud settings page and enable Referral Management. The platform provisions the Referral object, the status workflow, the related record-type metadata, and the default permission sets. Run the post-install validation to confirm Referral objects are visible to the right roles. If the org is migrating from a legacy referral system, plan the data migration before enabling Referral Management widely; new referrals and historical referrals need to coexist in the same object.
- Configure the referral data model and status workflow
Customize the Referral record type to match your operational context: add custom fields for industry-specific data (insurance plan, financial product type, agency program), configure picklist values for status transitions, set field-level security to match your role model. Customize the status workflow if the default does not match your process (some health plans add an additional Triaged status, some financial firms add a Compliance Review status). Document the status transitions and their automation triggers in the operational runbook so caseworkers know what each status means.
- Configure consent capture and audit logging
Work with legal and compliance to define what consent each referral type requires. Configure Consent records (or the industry cloud equivalent) to capture the consent type, the consenting party, the scope of data sharing authorized, and the expiration. Link consent capture to the Referral creation flow so referrals cannot be created without the required consent on file. Enable Field Audit Trail on sensitive Referral fields and on Consent records so the platform writes a complete history. Configure access reports that flag unusual access patterns for compliance team review.
- Build the operational reporting and dashboards
Create the reports the operations team needs. Standard set: referrals opened this week, referrals stalled past SLA, conversion rate from referral to scheduled visit or meeting, supervisor escalations, time-to-acknowledge per receiving party. Bundle the reports into dashboards per role: caseworker, supervisor, executive. Schedule the reports to email at the appropriate cadence (daily for caseworkers, weekly for supervisors, monthly for executives). Train the team on reading the dashboards and acting on the metrics. Reporting is the operational backbone of Referral Management; building it last is fine, skipping it entirely is not.
- Consent rules vary by jurisdiction, by industry, and by referral type. Hardcoding rules in a Flow or trigger creates maintenance debt; surface them as Consent records or custom metadata that compliance can adjust.
- Cross-organization referrals need partner-side capability. Not every external partner has API access or Experience Cloud login; design fallback paths (email, file exchange) for partners with lower technical maturity.
- Status workflows are sticky once in production. Changing a status value or adding a transition retroactively requires data migration for in-flight referrals; plan the workflow carefully upfront.
- Audit logging fills storage fast on high-volume referral programs. Plan for storage growth and archival policy from day one; Field Audit Trail on Referrals can generate substantial Big Object data.
- Reporting on Referrals across industries requires careful field naming because the Referral object schema differs between Health Cloud and Financial Services Cloud. Multi-industry orgs should align the schema explicitly.
Trust & references
Straight from the source - Salesforce's reference material on Referral Management.
- Referral Management in Health CloudSalesforce Help
- Referral Management in Financial Services CloudSalesforce Help
- Referral Management in Public Sector SolutionsSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is Referral Management?
Q2. Which industries use it?
Q3. What should you measure?
Discussion
Loading discussion…