The problem
What was broken before AI
After client meetings, financial advisors or their teams had to reconstruct the conversation, capture action items, draft a polished client recap, and update Salesforce manually. That work competes with the advisor’s attention during the meeting and creates lag after the meeting, especially when an advisor has several client conversations in a day.
What changed
What the use case made possible
Morgan Stanley embedded AI into the existing meeting workflow: with client consent, Debrief processes the meeting, summarizes key points, surfaces next steps, drafts an email for the advisor to review and send, and saves a note into Salesforce. The advisor remains responsible for reviewing, editing, and finalizing the output.
Why this matters
Why this use case is worth studying
This case shows what enterprise AI looks like when it is treated as an operational layer rather than a standalone chatbot. Morgan Stanley placed the model between the meeting, email, and CRM systems, which means the AI does useful work at the moment where context usually gets lost. The workflow also respects the trust boundary: AI can prepare the record and draft the message, but the advisor approves the client-facing output.
Use this when
When this pattern applies
Use this when important conversations create follow-up work that is too slow, inconsistent, or dependent on manual note-taking, especially when the relationship owner must remain in control of what the client sees.
