Meeting notes summarizer

System prompt: 

Review the meeting notes and create a clear, concise summary highlighting key takeaways and action items. Use a professional tone and format with headings and bullet points. Clearly identify responsibilities for each action item to ensure accountability and easy follow-up.

Example User prompt:

Transcript – Weekly Team Meeting (April 22, 2025)

Attendees: Sarah Kim, James Li, Priya Desai, Mark Chen, Anna Lopez
Start Time: 10:00 AM

Sarah: Alright, let’s kick off with campaign performance. So, March was... okay. We hit a 7% click-through rate, which is under our 8% goal.
James: That’s not too far off, though. Do you know where it underperformed?
Sarah: Email, mostly. The subject lines didn’t land. Instagram did really well though—actually better than expected.
Anna: Should we consider shifting more budget to Instagram for May?
Sarah: Yeah, I was going to suggest that. Maybe cut back a bit on email and go heavier on social.
Mark: Makes sense. Just let us know if you need help tracking metrics on the backend.

James: Alright, Product update—new dashboard feature is basically done on our end. Internal testing wrapped up yesterday.
Sarah: Nice! When do we launch the beta?
James: We’re thinking May 5. It'll be a two-week window. I’ll need Engineering to prep the test environment.
Mark: I can have that ready by May 3.
James: Awesome. And I think it’d be good to loop in Customer Success too, just in case we get any early user feedback.
Priya: Good call.

Priya: On HR—two new engineers are starting May 1. We need to update some onboarding docs, a few policies are outdated.
Anna: Do you need help reviewing them?
Priya: Yeah, if you can take a quick look at the finance stuff. Also, any ideas for the welcome kits?
Sarah: Maybe branded mugs? Notepads? Something fun but simple.
James: What about a short welcome video from the team?
Priya: Love that. Can you all send me ideas by Friday?

Anna: Quick finance update—we’re a little over budget on Product due to some contractor hours, but it’s manageable.
James: That was the UI work, right?
Anna: Yep. I’ll reallocate some funds from the general reserve. I’ll send a revised Q2 budget by Thursday.
Sarah: Marketing’s fine for now. We’ll reassess in May.

Mark: Engineering-wise, backend’s ready for the beta feature. I just need a couple of days to finish the secure test environment.
James: Perfect.
Mark: Only concern is server load during testing. I’ll set up monitoring and alerts to be safe.