Skip to main content

Athena 101 · Lesson 10 · Turn a meeting into decisions

In this lesson, you’ll turn a finished meeting into decisions, owners, tracker rows, and a draft follow-up.After a call, the decisions and action items are already waiting for you. Northwind’s carrier review is in Athena. Open it from Meetings, under Sessions. Overview gives you the summary first. Under Follow-ups are the decisions and action items Athena found in the call. That’s a good start. The work is turning them into something your team acts on.Now get each decision and each owner, traced back to the call. Click Ask about this on the summary. The meeting goes into a new question. Ask for each decision and action item, with an owner, a date, and where it was said. Athena answers from the call. A line with no owner stays without one, so nothing is made up. Every line carries a citation. Click one, and you land on that moment in the meeting. Check who actually said it before anyone acts on it.Next, the action items land on the tracker your team already uses. A list in chat gets lost. Ask Athena to add the dispute items to the Disputes tracker, one row per dispute ID. That way, a dispute that already has a row is updated, not added twice. The card names the rows it wrote. Click Scroll to cell, and the tracker shows them.Last, the follow-up to the carriers waits as a draft your team can review. Type slash, choose Attach Project, and pick Northwind freight exceptions, so Athena uses your team’s instructions. Ask for the draft, and say plainly not to send it. It’s created as a document and added to the project. Open Comments and mention Sam, so he checks the dates before it goes out. Sending is a separate step, covered in lesson 16.You decide which calls Athena records. Here, Join all by default is on for the connected calendar. For a call Athena shouldn’t record, click Prevent on that meeting. If your firm limits the meeting bot, use a meeting someone shares with you.Quick check. How does Sam check an action item was really agreed? Click its citation. It opens the moment in the call where it was said.Here’s how a project team uses this. After the weekly status call, they ask for decisions and owners. The action items go straight to their tracker. And the follow-up stays a draft in the project until someone checks it.Try it on one of your own meetings with this prompt. Look for a meeting citation on every line.

Before you start

Upload these files from the Northwind starter kit: Lesson 10/Northwind carrier review.txt, Lesson 10/Disputes tracker.xlsx, and Northwind dispute SOP.pdf. A finished tracker is in Checkpoints/Lesson 10. The supplied transcript lets you practice without a calendar connection or recording. Upload it and use its written timestamps to check passages. Ask your admin about meeting capture if you want to follow the recorded-meeting steps; uploads do not create a meeting recording or clickable timed citations.

Steps

1

Open the finished meeting

For the starter-kit route, start a chat and @-mention Northwind carrier review.txt. If you have a captured meeting, open it under Sessions and read Overview and Follow-ups.
2

Ask for decisions and owners

Ask for decisions, owners, dates, and citations. Check passages against the transcript’s written timestamps. For a captured meeting, use Ask about this and open the citation or recording.
3

Update the tracker

Ask Athena to add action items to the tracker, using one row per dispute. Use Scroll to cell and check the entries.
4

Draft the follow-up

Mention the uploaded tracker and procedure, or attach the freight exceptions Project if you created it. Request a follow-up without sending it, then use Comments to ask a teammate to review.
5

Choose which meetings are recorded

If meeting capture is enabled, check Join all by default for your calendar. Click Prevent on a meeting Athena should skip.

Try it

@[Northwind carrier review.txt] List each decision and action item with an owner and a due date. Cite where it was said.
Look for a source and timestamp beside each decision.

Next

Save your method as a skill