Financial services use case · Salesforce + OpenAI + ServiceNow + Snowflake
Underwriting referral pack
Referred submissions arrive with documents and exposure extracts that an underwriter must connect to the applicable authority and acceptance guidelines. Underwriters receive one source-linked referral pack showing the submission, exposure context and guideline conditions that require their decision.
Systems involved
What each system contributes
External exposure or market data is included through the institution's authorized provider interfaces with source and version references. No pre-built insurance or market-data connector is implied. Core banking, lending, policy administration, claims, identity verification, KYC and sanctions screening have no pre-built Nexus connector. They are reached through the institution's approved APIs, database access or vendor interfaces, or as Rules + Code, inside the same workflow and with the same approvals and audit.
Architecture
One governed run
How it starts: An insurance submission is referred under the insurer's rule-based acceptance or underwriting-authority policy.
Step by step
How the process runs
- 01
Establish the referral
Read the Salesforce submission context and create or link the ServiceNow referral case with its source and referral-rule references.
- 02
Assemble exposure and guidelines
Retrieve the permitted Snowflake exposure dataset and the applicable guideline and policy context through the authorized insurance-system interfaces.
- 03
Prepare the model brief
The selected model summarizes the submission and identifies the guideline conditions relevant to referral, placing the corresponding source text beside each observation.
- 04
Validate the referral context
Rules check established threshold calculations, exposure units, source versions and the underwriter authority required for the case.
- 05
Capture the underwriting decision
The named underwriter records the reviewed terms, request for information, escalation or acceptance decision before any separate interface action updates the authoritative underwriting system.
Control
Human decision and exception path
Human decision
The named underwriter decides the terms and outcome within their authority, with escalation where the case requires a different approver. Changes to premium, coverage or binding status are applied only through the separately authorized system action.
Exception path
- Missing exposure inputs or an unidentified guideline version holds the pack for completion.
- A model observation without a supporting passage returns to review alongside the original submission.
- Revised submission or exposure values require the affected referral checks and approvals to be refreshed.
Evidence
What gets audited
- Submission version, exposure snapshot and referral trigger.
- Guideline passages, model summary and calculation checks.
- Underwriter decision, authority and approved terms.
- Authoritative system update and linked referral responses.
Nexus runs on premises, in private or sovereign cloud, or air-gapped. Credentials stay in the vault, roles decide who can approve, and the execution record stays inside your deployment boundary.
Sovereignty and deploymentRelated
Patterns, connectors and next steps
- Snowflake-Salesforce integration
Integration pattern · CRM data feeds analysis, while selected analytical results return to Salesforce under explicit ownership rules.
- Salesforce connector
73 pre-built actions
- OpenAI connector
25 pre-built actions
- ServiceNow connector
55 pre-built actions
- Snowflake connector
35 pre-built actions
- Human-in-the-loop
Where approval belongs in a running workflow.
- Lead to account and ERP handoff
Another financial services use case.
FAQ
Questions about this use case
- Does Nexus replace any of these systems?
- No. Each system keeps its own records. Nexus runs the process between them and records each decision.
- How does the run start?
- An insurance submission is referred under the insurer's rule-based acceptance or underwriting-authority policy.
- What if a step is not covered by a pre-built action?
- External exposure or market data is included through the institution's authorized provider interfaces with source and version references. No pre-built insurance or market-data connector is implied. Core banking, lending, policy administration, claims, identity verification, KYC and sanctions screening have no pre-built Nexus connector. They are reached through the institution's approved APIs, database access or vendor interfaces, or as Rules + Code, inside the same workflow and with the same approvals and audit.
- Does the model choose whether a risk is acceptable?
- No; it prepares the comparison with guideline wording, while referral rules establish the review path and the named underwriter decides.
Use case review
Discuss this use case
Bring your version of the process. We will map the systems, approvals and evidence it needs.