The questions that actually get asked.
Short answers on data, evidence, and what is actually shipped.
If the one you need is not here, ask and it will be.
No. A CRM records what happened. Luscent reads the same substrate and tells you what it means and what has been missed. A native CRM exists as a separate Luscent product for firms that do not have one, and it is in build; firms on Salesforce keep Salesforce.
No, and it is built so that it cannot. No client-facing output leaves Luscent without a person approving it. Every Signal is a recommendation, and the relationship manager decides.
No. Nothing is written back into Microsoft 365, Salesforce or any system of record. Luscent reads, and your systems of record stay exactly as they are.
On European infrastructure. Scaleway, Paris primary with Warsaw for disaster recovery. Identity and mail run on Microsoft's EU platform.
No. There are no international data transfers, and no US model API sits in the client-data path.
Open-weight models, served on Scaleway's EU platform in Paris. Open weight is what they are; where they are served is the claim that matters, and no OpenAI, Anthropic or Google API sits in the client-data path.
Identifiers are removed before inference. Pseudonymisation controls are applied to language-model calls, so what reaches the model carries the situation and not the identity.
By a deterministic rules engine, never by a model. A compliance outcome carries the rule that fired and no confidence score at all, because a regulatory result is not a guess. Signals produced by a model carry a confidence, and the two are drawn differently everywhere on purpose.
Yes. Every Signal carries the rule that gated it, the source messages it was drawn from, and the model and version involved. A Signal acted on records the decision, who took it, and when.
Luscent is a vendor under your process, not a DORA feature. You run the outsourcing assessment under CSSF 25/882 and DORA Article 28, and we supply a DORA Article 28 information pack and register inputs on request. DORA is company readiness on our side; it is not something the product does for you.
Ninety days, free, three to five relationship managers, starting on synthetic data. Success metrics are agreed before day one, so at the end there is something to judge rather than an impression.
No. The pilot starts on synthetic data, and you decide if and when real correspondence enters it.
Microsoft 365, with or without Salesforce. That is the whole dependency today.
Data exports and a GDPR data processing agreement are standard, and source-code escrow is available.
No completed pilots yet. The first working version was shown at the Luxembourg House of Financial Technology AI Experience Centre on 13 April 2026, and the first cohort runs in the fourth quarter of 2026. Applications close on 30 September 2026.
Product version 1.4. Signals generate live on real books in production, the Signal lifecycle is complete, and the suitability gate is auditable with every override recorded. The surfaces are Dashboard, Clients, Client Detail, Tasks, Signals, Strategy Director, House Views, Data Hub, the Compliance Home dashboard and the Audit Trail Viewer, with Microsoft 365 and Salesforce connected. In build, and described as in build: the native Luscent CRM, the Chatbot page and the Notes tab. Multi-seat access control is release 1.5. The second engine for structured portfolio data is release 2.0, and it is not dated.
A release ships when its bar is met, not on a date. Every release, what it changed and when it landed is in the changelog. Anything not listed there has not shipped, whatever else you may have been shown.