4. Post-Call Processing
Note: The video covers material not in the guide below — please watch in full.
Action Step
Complete this before moving on.
Use your Fireflies skill to pull your test transcript and save it locally, then confirm it pulled the right one. Next, process the BrightLoop kickoff transcript — extract action items, decisions, open questions, and key dates, then format everything as Teamwork tasks and push them into your test Teamwork project. Do not close this Claude Code session when you are done — the next training picks up where you left off. Submit a screenshot of the Teamwork project with the task lists loaded.
Training Guide
The call just ended. You've got a Fireflies recording and a client expecting a recap by end of day.
Wait until tomorrow and half of it fades. If you do it manually — relistening, typing up notes, building task lists from memory — it takes an hour. Maybe two.
You're going to do it in fifteen minutes. And the tasks are going to land directly in Teamwork.
(You already know the pieces. Now you connect them)
Step 1: Pull the Transcript from Fireflies
You connected to the Fireflies API in a previous training. Now you use it for real.
Open Claude Code. You're going to pull the kickoff transcript directly — no opening Fireflies in a browser, no downloading a file, no copy-pasting.
Type this:
"Connect to the Fireflies API using my API key and pull the transcript from the BrightLoop kickoff call. It was recorded today."
Claude hits the API, finds the meeting, and pulls the full transcript into your session.
If you don't have Fireflies API access set up, that's fine. The transcript is in your Academy-Practice-Assets/Post-Call-Processing folder — kickoff-call-transcript-brightloop.md. Feed it the file path instead:
"Read this kickoff call transcript. I need to process it for action items, decisions, and next steps."
Then paste the file path below the prompt.
Either way, the transcript is now in your context window. Everything else builds from it.
(Now you turn a conversation into structure)
Step 2: Process the Transcript
A kickoff call is messy. People interrupt each other. There are tangents — CloudCoach competition, a webinar running over, Rachel joking about ugly spreadsheets. You're pulling signal out of noise.
"Process this kickoff call transcript and extract the following: 1) Action items — who owns it, what it is, when it's due. 2) Decisions that were made on the call. 3) Open questions that still need answers. 4) Key dates or deadlines mentioned. Format it as a structured document I can reference."
The AI comes back with structured output — action items with owners, decisions that were made, open questions that still need answers. Read through it.
Did it catch everything? The AI sometimes misses things said casually or buried in a tangent. Amit's comment about Nina wanting to be part of the ICP conversation? Easy to miss. The CloudCoach competitive pressure driving the ICP urgency? Easy to miss too.
If it missed something, tell it:
"Add to the action items: schedule a preliminary ICP review with Amit and Nina for end of week two. Also note under open questions that CloudCoach is moving into their mid-market segment — this is driving urgency on ICP definition."
(Now turn those notes into tasks)
Step 3: Format for Teamwork
"Take the action items from the processed transcript and format each one as a Teamwork task. Each task needs: task name, assignee, due date, and a description that includes enough context that someone reading it cold would know what to do. Use today's date as March 17 for calculating due dates."
Claude structures each task with the name, assignee, due date, and description. Review them — the AI sometimes makes due dates too aggressive or too loose. You know the real timeline better than it does.
(Now push them where they belong)
Step 4: Push to Teamwork
Same pattern as Fireflies. You connected to the Teamwork API in a previous training. Now you use it.
"Connect to the Teamwork API using my API key and create these tasks in my BrightLoop project."
Claude connects, creates the project if needed, and pushes each task with the assignee, due date, and description intact. You'll see confirmation for each task created.
If you don't have Teamwork API access yet, set it up now — same way you learned before. Go to Teamwork, grab your API key from profile settings, and give it to Claude.
Once the tasks are in, open Teamwork in your browser and verify. Check that the task names make sense, the due dates are right, and the descriptions have enough context.
(One more step)
Step 5: Write the Recap Email
Cam told the client a recap was coming today. Time to write it.
"Write a client-facing recap email for the BrightLoop kickoff call. It should include: a brief summary of what we discussed, the three engagement phases confirmed, the action items with owners and due dates, the weekly sync schedule, and a note about the board meeting timeline. Tone should be professional but warm. Address it to Rachel, Amit, and Priya."
Read the draft. Look for:
- Does it mention the board meeting moving to March thirty-first?
- Does it reference the quick-fix lead routing decision — something we pulled forward from phase two because deals are being lost now?
- Does it feel like you? Edit anything that sounds generic.
Once you're happy with it, copy the email into your actual email client and send it. Or if this is practice, save it as a file in your Academy-Practice-Assets/Post-Call-Processing folder.
Before You Close — Read This
Do not close this Claude Code session.
Your context window right now has everything loaded — the kickoff transcript, the processed action items, the Teamwork task format, the recap email, the API connections, and every prompt you used to get here. That's valuable context.
The next training picks up right where you are. If you close this session, you lose all of that context and have to rebuild it from scratch.
Keep the session open. Move to the next training.
Submission
Screenshot the TeamWork Project with your test tasks all loaded in there.
What You Just Did
Pull the transcript, process it, push the tasks, send the recap. That's the pattern.
(But doing it manually every time? That's not the move. Next up: you make this repeatable)
Comment in Slack
Post your answer in your onboarding channel.
What was your biggest takeaway(s) from this training?