Luscent vs communications surveillance
Surveillance and archiving answer the regulator's question about your staff: what was said, and was any of it misconduct. Luscent answers the question about your Client: what changed, what the Relationship Manager should do next, and what the file needs to show.
Most firms that use Luscent keep both.
- Message
- Email from Charlotte Klein, 09:12
- Reviewed for
- Staff conduct and policy
- Employee
- Anne Keller, Relationship Manager
- Alert
- None raised
- Queue
- Compliance review
- Retention
- Kept on the archive
What the sale means for the Klein Family Office.
“The sale of the operating company is now closed and the proceeds, roughly 9.200.000 EUR, will land next month.”
Call Charlotte and Michael Klein with one liquidity figure before the Q4 committee.
Is Luscent communications surveillance?
No. Surveillance reviews employee communications for misconduct and sends alerts to compliance analysts. Archiving keeps every message so it can be produced on request. Luscent reads the communications a firm already has, attributes each one to a Client, and turns what it finds into a Health Score, Signals and suitability evidence linked to the source messages. It replaces neither, and does not try to.
What each one does with the same message
Who it looks at
The employee: what staff said, and whether any of it breaches policy.
The Client relationship. Luscent does not score Relationship Managers.
What it looks for
Misconduct: market abuse, policy breaches, patterns of mis-selling, found through lexicons, rules and models.
A material change, a drift against the mandate, a relationship that is cooling, raised from the Client's own words.
Who acts on it
A compliance analyst working an alert queue.
The Relationship Manager, who approves or edits every AI draft before anything reaches a Client.
When it matters
After the fact, in review.
As the work happens: the Signal appears the same morning as the email.
Suitability
Can flag suitability risk for a reviewer to investigate.
Writes the suitability evidence as the advice happens, linked to the message it came from. A deterministic rule: it fired or it did not, and you can read why.
The record of what was said
Sits on the archive, which keeps every message for the retention period.
Reads from the same sources and writes nothing back. Your archive stays the record.
When surveillance is enough, and when it is not
Surveillance and an archive are enough when
- The job is to catch misconduct and produce what was said, on request
- A compliance team works the alert queue and that is the whole requirement
- Suitability files are assembled by hand, and the volume makes that workable
Luscent adds to them when
- A material change sits in an email thread for weeks before anyone acts on it
- Suitability files are rebuilt after the fact, unevenly across the population
- You want to see a relationship cooling before the Client says so
How Luscent works alongside surveillance and your archive
- 01 · ConnectMicrosoft 365Salesforce
The same sources your archive captures, each authorised by the firm through the provider's own consent flow and scoped to what the firm chooses to share.
- 02 · ReadHealth ScoreSignalsEvidence
Luscent reads each message for the Client it concerns, scores the relationship and raises a Signal when something moves. Surveillance keeps reading the same message for staff conduct.
- 03 · ActRelationship ManagerNamed approver
The Relationship Manager decides what to do. The evidence is filed as the work happens, and a named person approves before anything reaches a Client.
What buyers ask about Luscent, surveillance and archiving
Does Luscent replace our surveillance tool?
No. Surveillance looks for staff misconduct and stays with your compliance team. Luscent looks at the Client relationship, and does not score Relationship Managers.
Does Luscent replace our archive?
No. Keep it. Retention is the archive's job and Luscent does not take it over. Luscent reads from the same sources and writes nothing back.
Where does the suitability evidence live?
In Luscent, linked to the messages it came from. Our application audit log has an append-only design, in build.
Where are the messages processed?
In the EU. Inference is EU-hosted, with EU providers only, and no US model API in the client-data path.
Can we try it without production data?
Yes. The pilot runs for ninety days, free, with three to five Relationship Managers. It starts on synthetic data, stays in the EU and writes nothing back.
See it on your own book, next to the tools you already run
Ninety days, free, three to five Relationship Managers. Synthetic data first, EU only, nothing written back.