# Client meeting follow-up: draft action items from the transcript, confirm before sending > A proposed professional services workflow: transcript-quoted action items, unclear owners left unclear, scope flags and nothing sent to a client unreviewed. Canonical URL: https://techtideai.io/blog/client-meeting-follow-up-drafting Markdown URL: https://techtideai.io/blog/client-meeting-follow-up-drafting.md Publisher: TechTide AI, Columbus, Ohio (https://techtideai.io) Author: Alex Cinovoj, Founder & CTO, TechTide AI ยท CTO & Co-Founder, CPG Playbook Type: Field Note Published: 2026-10-29 Collection: September 2026 editorial collection (a label, not the publication date) Reading time: 4 min Topics: meeting follow-up automation, professional services workflow, meeting transcript action items, client communication review Site index: https://techtideai.io/llms.txt Offer summary: https://techtideai.io/offers.md --- A consulting team finishes a client call with six agreed next steps. By the time the follow-up email goes out the next afternoon, two steps have been forgotten, one has the wrong owner, and one describes a commitment the client never actually made. Nobody was careless. People were reconstructing an hour of conversation from memory and scattered notes. Meeting transcripts make a better first draft possible. A workflow can read the transcript, propose action items with owners and dates, and quote the lines each one came from. The consultant then confirms, edits and sends. What the workflow must not do is send anything to a client on its own, or present a guess about a commitment as if it were agreed. This is a proposed workflow for professional services teams. Recording and transcription rules, client agreements and firm policies vary, and they decide whether a given meeting can be transcribed and processed at all. ## Start with permission to use the transcript Before any automation, confirm that the meeting was transcribed with appropriate notice under the firm's policies and the client's agreement. Some clients prohibit recording; some matters are too sensitive to process outside a narrow set of systems. The workflow should check a matter-level flag and skip meetings where processing is not allowed. Access is also controlled by the platform. Microsoft's documentation for the [Graph API to get a meeting transcript](https://learn.microsoft.com/en-us/graph/api/calltranscript-get?view=graph-rest-1.0) lists `OnlineMeetingTranscript.Read.All` as the least-privileged delegated permission for online meetings, states that application access requires tenant administrators to create an application access policy granted to a user, and describes tenant administrator settings that govern transcript access. I would use the narrowest arrangement that fits, and agree it with the firm's IT administrator rather than requesting broad permissions to make development easier. ## Extract proposals, each with its quote For each candidate action item, the workflow should capture the action, the proposed owner, any date mentioned, and the exact transcript lines that support it. The quote is what makes review fast: the consultant can see in a few seconds whether the client actually said "we will send the data by Friday" or only "we might be able to get you something." Where the transcript is ambiguous, the proposal should say so. "Owner unclear" and "no date discussed" are useful outputs. A model filling in a likely owner or a reasonable date creates exactly the kind of error the workflow is meant to prevent. ## Distinguish commitments from discussion Meetings contain ideas, options and hypotheticals as well as decisions. The draft should separate items into agreed actions, open questions and topics discussed. I would ask the model to classify conservatively: when in doubt, an item is an open question, not an agreed action. Commitments the firm makes deserve particular care. If the transcript suggests a consultant promised extra work, a new deliverable or a change in timing, the draft should flag it for the engagement lead rather than include it as an ordinary action. Those statements may affect scope and fees. ## Confirm before anything is sent The consultant reviews the draft in a simple screen: each proposed item with its quote, editable fields, and accept or remove buttons. Only accepted items go into the follow-up email draft, which the consultant then edits and sends from their own account. I would not connect the workflow directly to outbound email in the first release. The cost of a wrong statement to a client is high, and the time saved by skipping one review step is small. ## Update the project tracker carefully Accepted actions for the firm's team can be created in the project tracker, linked to the meeting and the transcript lines. Actions for the client can be tracked as dependencies rather than tasks assigned to client contacts, unless the client uses the same system by agreement. Avoid creating duplicate tasks when the same action comes up in consecutive meetings. The workflow can propose linking a new item to an existing open one, for the consultant to confirm. ## Keep transcripts and drafts contained Transcripts often contain more than the project discussion: personal remarks, other clients' names, or sensitive business information. Keep processing inside the firm's approved environment, store drafts with the engagement's access controls, and set a retention period for transcripts and drafts that matches the firm's policy. If a model service processes the transcript, confirm that its data terms are acceptable for client information before any meeting is sent to it. ## Measure what the consultant changed In a pilot, track how many proposed items consultants accepted, edited or removed, and how many actions they added that the draft missed. Ask whether the draft saved time or created more work. A draft that consultants must rewrite each time is not helping. The acceptance condition I would agree: every proposed item quotes its supporting lines, unclear owners and dates are labeled rather than guessed, nothing is sent to a client without the consultant's edit and send, and meetings flagged as restricted are never processed. Bring a sample transcript you are permitted to share, your current follow-up template and where actions are tracked. [Send the project brief](https://techtideai.io/contact). ## Sources - [Graph API to get a meeting transcript](https://learn.microsoft.com/en-us/graph/api/calltranscript-get?view=graph-rest-1.0) ## Related Field Notes - [Client status reports from project evidence, with missing facts left visible](https://techtideai.io/blog/consulting-delivery-status-reports) ([Markdown](https://techtideai.io/blog/consulting-delivery-status-reports.md)): A proposed client reporting workflow that drafts status reports from bounded project evidence and leaves missing facts visible for the delivery lead. - [Consulting scope changes: turn client requests into approval decisions](https://techtideai.io/blog/consulting-scope-change-workflow) ([Markdown](https://techtideai.io/blog/consulting-scope-change-workflow.md)): A proposed scope-change workflow that compares client requests with the current agreed scope and prepares the decision for the delivery owner to approve. - [Client onboarding automation for professional services: from signed scope to ready delivery](https://techtideai.io/blog/professional-services-client-onboarding-automation) ([Markdown](https://techtideai.io/blog/professional-services-client-onboarding-automation.md)): A proposed onboarding workflow connecting approved scope, client inputs, access requests, and delivery readiness without inventing commitments. - [B2B returns triage: assemble the RMA case, keep the credit decision with staff](https://techtideai.io/blog/b2b-returns-rma-triage) ([Markdown](https://techtideai.io/blog/b2b-returns-rma-triage.md)): A proposed RMA process: order matching, quoted return terms, safe evidence uploads, separated complaints and return decisions made by authorized staff. All Field Notes: https://techtideai.io/blog