Arc by Rival IT • Client case study • Financial services
Working with an advisory firm to solve an operational problem, Rival IT designed a workflow connecting Microsoft Teams transcripts, AI-generated meeting summaries, and Wealthbox CRM through Arc, our AI automation tool and platform. It is a practical example of starting with a firm’s process and turning it into a connected workflow.
Every advisory firm has its own way of documenting meetings, managing client records, and handling prospective relationships. For one registered investment adviser, the opportunity was to automate part of the work that happens after a meeting while preserving the firm’s chosen rules for where information should go.
Rival IT designed and built this initial implementation in collaboration with the client. Together, we identified the meeting-documentation challenge, established the routing requirements, and shaped a practical solution using Arc.
Your firm’s opportunity may look different. A different CRM, an additional approval step, or an entirely different administrative bottleneck can all change the design. This case study offers a starting point for that conversation.
From a meeting transcript to the right destination
The workflow uses scheduled Microsoft Teams meeting context, checks for an available transcript, and uses AI to generate a structured summary of the interaction. It then routes that summary according to the firm’s CRM matching rules.
One meeting. A clear path for the notes.
Designed by Rival IT with the client, from meeting to CRM.
Microsoft Teams
Identify the scheduled meeting and its participants.
Transcript available?
Yes → Use the transcript as source material.
No transcript to summarize.
Arc creates a summary
Turn the conversation into structured meeting notes.
File in Wealthbox
Add the summary to the matching client’s CRM profile.
Email the advisor
Send the summary for review and manual filing in the appropriate record.
The aim is to reduce repeated copying and filing while giving the advisor a clear path for exceptions. The workflow does not create a new CRM record simply because an email address is unfamiliar.
Designed with the client to solve an operational problem
The choice to email unmatched summaries was deliberate. An unfamiliar address could belong to a prospective client, an existing client using another email address, or a spouse participating in a household conversation.
Working with the firm, we established a clear boundary for this implementation: automatically file summaries when the client email matches, and send other cases to the advisor. The advisor can then determine the appropriate record or next step.
The email match controls the filing destination. It does not independently establish that the generated summary is accurate, complete, or ready for every downstream use.
Your workflow can have different rules. This implementation reflects the process we developed with one advisory firm. Arc provides a way to connect systems and implement the process your firm wants to support.
Other possibilities start with your requirements
A firm with a different process might want to extend the workflow in other ways. Potential designs include:
Prospect record creation
Create a CRM entry when the required information is available and the firm’s defined criteria are met.
Household-aware routing
Use approved relationship information to route spouse or household interactions to the appropriate record.
Advisor approval
Require review before a generated summary is added to a client profile.
Follow-up tasks
Route proposed next steps into the firm’s task or approval process.
These are possibilities for future or alternative implementations, rather than features included in this client’s initial deployment. Each would need its own decision rules, handling for incomplete information, and appropriate review.
Automation within the firm’s compliance framework
For an advisory firm, automation design must account for how client information is accessed, processed, shared, and retained. It must also fit the firm’s documentation, supervisory, and information-security requirements.
For SEC-registered advisers, relevant obligations can include customer-information safeguards under Regulation S-P and applicable books-and-records requirements under Advisers Act Rule 204-2. The applicable requirements depend on the firm, the information involved, and the workflow’s use.
Defined matching rules and visible exceptions are useful parts of this implementation. The broader compliance assessment also needs to address access permissions, service-provider data handling, required retention, summary accuracy, and supervisory review. Automatically posting a summary to a CRM is not, by itself, a determination of regulatory compliance.
The firm’s compliance team defines its requirements. Rival IT’s role is to connect those requirements to the technical implementation. Our RIA compliance implementation checklist explores how that work connects policies, systems, and documentation.
A focused first step, with room to grow
This project connects a real source of information, a repeatable documentation task, and a defined destination. It illustrates how AI can become part of an operational process, with clear handling when the information does not meet the firm’s rules.
It is also one example of Rival IT’s broader AI and business automation work. Another client started with a different problem: moving warehouse photos into a shared Microsoft 365 repository. The business process determines the implementation.
What could a connected workflow look like for your firm?
Perhaps your team spends time transferring meeting notes, preparing follow-up tasks, gathering onboarding information, or updating several systems with the same information. Those recurring steps can be useful starting points for an automation conversation.
Bring us the process, the friction, or the idea. We can help explore the systems involved, the rules that matter, and a practical first implementation through Arc.
Let’s talk about your workflow