Banking & Capital Markets

Relationship Manager Intelligence Copilot

Designed for Relationship manager

Prepare a relationship manager for every client conversation by merging holdings, transaction behaviour, CRM history, and approved research into a cited briefing, with suitability review before any recommendation is shared.

Contract BAN-01 · primary aggregate ClientRelationship · mode loading

Decision brief

Approve the client-facing briefing: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Relationship manager and supervisor

The named role remains accountable for the consequential decision.

Governed evidence

5 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

Before a quarterly review the copilot shows a client group holding 31 percent cash after a business sale, cites the approved fixed-income commentary, proposes a laddered deployment, flags that the mandate caps duration at five years, and holds the idea until the supervisor approves the suitability rationale..

Decision to make

Prepare a relationship manager for every client conversation by merging holdings, transaction behaviour, CRM history, and approved research into a cited briefing, with suitability review before any recommendation is shared.

Outcome to show

Released briefing and logged advice record gives Relationship manager and supervisor the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Assemble relationship and holdings context
  2. 2Detect portfolio drift and cash build-up
  3. 3Ground ideas in approved research
  4. 4Run suitability and conflict screening
  5. 5Approve the client-facing briefing

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Relationship manager and supervisor verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved ClientRelationship evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Prepare a relationship manager for every client conversation by merging holdings, transaction behaviour, CRM history, and approved research into a cited briefing, with suitability review before any recommendation is shared.
Primary aggregate
ClientRelationship
Primary container
clientRelationships
Hierarchical key
/tenantId + /clientGroupId
Schema version
1

Sample scenario

Before a quarterly review the copilot shows a client group holding 31 percent cash after a business sale, cites the approved fixed-income commentary, proposes a laddered deployment, flags that the mandate caps duration at five years, and holds the idea until the supervisor approves the suitability rationale.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
clientRelationships Primary /tenantId + /clientGroupId ClientRelationship, PortfolioPosition, InteractionNote, NextBestActionCandidate
approvedResearchLibrary Reference /tenantId + /researchId ResearchNote

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
ClientRelationship clientRelationships /tenantId + /clientGroupId relationship::{clientGroupId} None
PortfolioPosition clientRelationships /tenantId + /clientGroupId position::{clientGroupId}::{accountId}::{instrumentId} None
InteractionNote clientRelationships /tenantId + /clientGroupId interaction::{clientGroupId}::{interactionId} summaryVector
ResearchNote approvedResearchLibrary /tenantId + /researchId research::{researchId}::{chunkIndex} bodyVector
NextBestActionCandidate clientRelationships /tenantId + /clientGroupId action::{clientGroupId}::{candidateId} rationaleVector

Query patterns