Customer & Prospect 360 Inbox
The banker opens one inbox and knows exactly what changed, who owns it, and what happens next.
Here is what changed, who owns the next move, what the banker should say, and which relationships are stuck before they cost the bank production.
Relationships
16
Changed overnight
6
Calls due today
7
Value at stake
$28M
Executive pulse
Are relationships moving, or just sitting in lists?
Moving relationships16
Stuck relationships8
Open commitments38
Captured events34
Morning changes
6
Relationships changed since the last briefing
Calls due
7
Owned banker actions for today
Stalled
6
Needs follow-up or manager help
Timeline events
34
CRM, calls, email, meetings, core
Source proof
Demo
Demo workspace
These relationships changed overnight
Call these today
Stalled follow-ups
Expansion signals
Source proof and banker-safe language
Source
Riverstone Community Bank relationship workflow | relationship_360_inbox
Observed
2026-06-14 | refreshed 2026-06-14
Every relationship fact must carry source proof: source name, source table or URL, observed date, refresh date, confidence, and demo/prod flag.
Use relationship service and banker workflow language; do not use this surface for credit decisioning or prescreening.
Do not say a prospect banks with a named competitor unless that fact is sourced or customer-provided.
Prospect timelines must not expose internal customer account behavior; internal signals are shown only inside the bank workspace.