Use case 02 / 04 · Comms to ComplianceNot sure which fits? Find your firm type

An email changes the client. The advice waits.

When a client's message says their circumstances have changed, Luscent reads the change, holds the advice that relied on the old picture and opens a reassessment. Nothing moves until a relationship manager confirms what was read and signs.

Join the pilot programme Watch it run
CLIENT EMAIL · 09:12PROFILE · LIQUIDITYDRAFT HELD
FIG. 02.1 · One sentence, one field, one hold
Trigger
A client email in Microsoft 365, read-only
Reads
Changes the client states, never inferred ones
Holds
Advice that relied on the old picture
Decides
The relationship manager, with a stated reason
§ 01 · The story

From one inbox to the client file.

  1. 01 · Today

    The client said it in the second paragraph.

    A sale, a move, a new liquidity need, mentioned in passing. It sits in one inbox, and the profile the last advice relied on is now out of date without anyone noticing.

  2. 02 · The moment

    Read in the EU, not decided there.

    The sentence is read, the field that moved is named, and the advice that relied on the old figure is held until a person looks.

  3. 03 · With Luscent

    Confirmed, signed and kept together.

    The relationship manager confirms with a reason, the reassessment is signed, and the before and after stay side by side on the file.

One finding, one decision at a time.

Clients / Klein Family Office · Luxembourg · São PauloHealth Score 76
Connect · Microsoft 365 · read-only
From
Charlotte Klein
Received
Today, 09:12
Subject
Good news, and a question
The sale of the operating company is now closed and the proceeds, roughly 9.200.000 EUR, will land next month. Michael asks again for a liquidity figure before the Q4 committee.
Material change · email 09:12DR 2017/565 · 54(7)
Awaiting the relationship manager

Demo environmentSynthetic data. Klein Family Office and everyone named here are fictional.

Step 1 of 6: An email becomes a finding
§ 02 · Who gets what

One workflow, four people who stop chasing it.

Relationship manager

  • The change flagged the day the client mentions it
  • The reassessment opened with the sentence attached

OutcomeAdvice stays on the current picture.

Compliance officer

  • A record that the firm acted on what the client said
  • Rejections kept with reasons, counted for the firm as a whole

OutcomeUp-to-date client information, demonstrably.

Head of advisory

  • Held advice visible before it is sent
  • Nothing depends on one person's inbox

OutcomeChanges do not wait for the annual review.

Management

  • Fewer gaps between what clients say and what the file shows
  • EU-served models, nothing written back

OutcomeLess exposure to advice given on a stale profile.

§ 03 · The business case

Fewer stale profiles, less reconstruction.

Comms to Compliance works on the compliance effort of keeping client information current and showing that the firm acted on it. This is the part of the homepage estimate it addresses.

  • 01Changes captured from the messages the firm already has
  • 02Reassessments opened with the evidence attached
  • 03Before and after kept together, not rebuilt for a review
  • PilotMeasured on your own book in the pilot, against success metrics agreed in writing before anything is connected.
Your firm
Compliance effort addressed
195.840 EUR a year
40 % of the compliance effort addressed
Hours returned
2.304 h a year
Per relationship manager
192 h a year
The working

12 relationship managers × 10 h a week × 48 weeks × 85 EUR an hour × 40 % of the effort addressed. The same model and assumptions as the estimate on the homepage. Modelled from time-and-motion assumptions, not measured client results.

The full estimate, with investment and payback
§ 04 · Boundaries

What it always does, and what it never does.

Always

  • Quotes the sentence it read, word for word.
  • Names the field that changed and the ones it left alone.
  • Freezes the advice that relied on the old picture instead of editing it.
  • Asks the relationship manager to confirm or reject, with a reason.

Never

  • Writes to the client. No client-facing message leaves without a relationship manager's approval.
  • Updates the client profile without a signature.
  • Sends the email outside the EU. The model is open-weight and served in the EU.
§ 05 · The rule

Our reading of Delegated Regulation (EU) 2017/565, Article 54(7)

“Investment firms having an on-going relationship with the client ... shall have, and be able to demonstrate, appropriate policies and procedures to maintain adequate and up-to-date information about clients ...”

When the client tells the firm something has changed, the firm has to be able to show it acted on it. An email that sits in one inbox is the gap; a finding with the sentence attached is the record.

Our reading, not legal advice. The rules engine applies the firm's own configuration of these rules, and the relationship manager decides.

§ 06 · Questions

Questions

Which messages does Luscent read?

The mail, calendar and CRM activity the firm connects: Microsoft 365 and Salesforce, read-only, authorised by the firm through the provider's own consent flow. Nothing is written back into those systems.

What happens if the model reads the email wrong?

The relationship manager rejects the extraction and says why. The hold is released with the profile unchanged, and the rejection is recorded. Rejections are counted for the firm as a whole, never per relationship manager.

§ 07 · The same Loop

Three more triggers, one way of working.

Use case 01 · Suitability GateEvery trade checked before the advice leaves.

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 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 run Use case 04 · Relationship DriftRelationships rarely end loudly. They drift.

When a client relationship starts to slip, Luscent shows it in the Health Score, links the messages behind it, and puts the next conversation on the relationship manager's list.

See it run
The pilotCohort open

Find out before you move a single client record.

Ninety 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.

Apply for the pilotHow the pilot works

The terms

Length
90 days
Cost
Nothing
Seats
3 to 5 relationship managers
Data
Synthetic first
Client data
Stays in the EU
Writes back
Nothing
  1. DAY 0Metrics agreed, in writing
  2. ConnectWeek 1 to 4
  3. WEEK 4The book, ranked
  4. First Signal acted onWeek 5 to 8
  5. WEEK 8A decision on the record
  6. ReviewWeek 9 to 13
  7. DAY 90Written review