Relationship manager
- The relationships that need attention, with the reason
- A drafted note to start from, never sent without you
OutcomeTime goes to the right conversation.
Replies slow down, a review is moved twice, another firm's name appears in a thread. Each on its own is noise. Luscent reads the communications the firm already has, shows the pattern in the Health Score with the messages behind it, and puts the next right conversation on the relationship manager's list.
A reply takes a week. A review moves twice. A forwarded thread names another firm. Each is noise on its own, and together they are a relationship going quiet.
The Signals are linked into one pattern, and the Health Score moves, with the messages behind the change beside it.
A Task with a drafted note reaches the relationship manager, who decides what to say and when. The follow-up is on the record.
Reading 90 days of email, calendar and CRM activity. No open Signals yet.
Klein Family Office, Luxembourg. Anne Keller's client for six years. Nothing looks wrong on any single day.
Demo environmentSynthetic data. Klein Family Office and everyone named here are fictional.
OutcomeTime goes to the right conversation.
OutcomeClient care that can be shown.
OutcomeFewer relationships go quiet unnoticed.
OutcomeRetention acted on early, not explained late.
Relationship Drift works on retention: relationships noticed early enough to act on. This is the part of the homepage estimate it addresses.
12 relationship managers × 10 clients × 10 % annual attrition × 375.000 EUR fee income (75 bps on 50 m) × 20 % of at-risk relationships kept. The same model and assumptions as the estimate on the homepage. Modelled from time-and-motion assumptions, not measured client results.
“... an investment firm act honestly, fairly and professionally in accordance with the best interests of its clients ...”
The duty does not pause when a client goes quiet. A relationship that has drifted is where advice goes stale and service slips unnoticed; seeing it early is how the firm keeps acting in the client's interest instead of finding out at the transfer request.
Our reading, not legal advice. The rules engine applies the firm's own configuration of these rules, and the relationship manager decides.
The state of a client relationship on a 0 to 100 scale, read from the communications and activity the firm connects: 80 to 100 healthy, 60 to 79 neutral, 40 to 59 at risk, below 40 critical. The trend matters as much as the number, so Luscent shows both, with the Signals that moved it.
No. It means the relationship has changed in ways worth a conversation: slower replies, a meeting moved, a new name in a thread. Luscent shows the messages behind the change; the relationship manager decides what it means and what to do. The score describes the client relationship, not the person managing it.
Before a relationship manager sends a rebalance, Luscent checks each trade against the mandate and the strictest jurisdiction, and names the smallest fix.
See it run Use case 02 · Comms to ComplianceAn email changes the client. The advice waits.When a client email says their circumstances changed, Luscent reads the change, holds the advice that relied on the old picture, and opens a reassessment.
See it run Use case 03 · Cross-BorderTwo rulebooks. One household. One defensible answer.A household booked in Luxembourg and São Paulo sits under MiFID II and CVM at once. Luscent evaluates one action under both and shows a path to proceed.
See it runNinety days, at no cost, with three to five relationship managers, starting on invented clients. Success metrics are agreed in writing before anything is connected, so at the end there is a decision rather than an impression.
The terms