I get my AI to turn messy meeting notes into a tidy Doc (prompt included)

What does the call leave you with?

Here is the before. The call ends and you are looking at half a screen of fragments: "Priya - re pricing, wait till Q3?", "Tom owns the migration doc", an arrow pointing at nothing, a phone number, two names you spelled wrong. You know there were three real decisions in there and a couple of things someone agreed to do, but they are buried under the shorthand you wrote at speed. The notes made sense while you were typing them. A day later they are archaeology.

Here is the after. You paste those same fragments to your agent and twenty seconds later you have a clean section in a Doc: who was there, the points that mattered, the decisions in plain sentences, and an action-items list with a name against each one. You did not reformat anything. You handed over the mess and got back the record.

That gap, between the notes you can take in real time and the notes you can use later, is the whole problem this solves.

What does your agent do with raw notes?

It reads them the way a good assistant would and rewrites them into a fixed shape. You do not have to label anything or put things in order. You give it the pile, in whatever sequence it came out, and it sorts it.

The shape is the part worth being deliberate about. A useful meeting record answers four things: who was in the room, what was discussed, what got decided, and who is doing what next. So your agent writes every entry under those headings. Attendees and a one-line summary up top, key points as bullets, decisions stated as decisions ("Holding the pricing change until Q3"), and action items as a list with an owner and, where you mentioned one, a due date. Because the structure is the same every time, the tenth meeting reads like the first, and you always know where to look for the thing you half-remember.

The trick is that you are not the one applying the structure. You brief it once (these are the headings I want), and from then on the formatting is the agent's job, not yours.

How does it pull out the decisions and action items?

This is the part people do badly by hand, because decisions and actions are scattered through a conversation, not announced. Someone says "fine, let's hold off until the new quarter" and that is a decision. Someone says "I'll get the doc to you by Thursday" and that is an action item with an owner and a date. In the moment you write neither down cleanly.

Your agent goes back through what you gave it and lifts those out. A line like "Tom owns the migration doc, end of next week" becomes an action item: owner Tom, due end of next week. A line like "we agreed not to touch the pricing page yet" becomes a logged decision. You can tell it how strict to be: only record a decision when something was genuinely settled, and flag the loose ends ("Priya to confirm budget, no date given") rather than inventing certainty that was not in the room. It reports what was said, it does not pad it.

What if I paste a transcript instead?

Same job, more raw material. If you record your calls and have an auto-transcript, paste the whole thing. Your agent reads the transcript, throws away the filler and the crosstalk, and writes the same structured entry: the points that mattered, the decisions, the actions with owners. A transcript is the easy case, because nothing is lost to your typing speed. You can also hand it your scrappy live notes and the transcript together and tell it to reconcile the two, so the bits you flagged as important do not get drowned out by the verbatim record.

This is also where a Doc earns its place over a chat message. Ask for a tidy-up in a one-off conversation and the result is gone when the conversation ends. A Doc is a real Markdown-native document that lives in your account, so your agent can write into it, read it back, and build on it next week. That continuity is the same reason the weekly review lives in a Doc rather than a thread.

Can it keep every meeting in one place?

Yes, and that is what turns a tidy-up into something useful over time. Instead of a folder of separate files, each meeting goes into the same Doc as a new dated section at the top, with the previous ones left underneath. The most recent meeting is always first, and everything before it stays as a log you can scroll.

A few weeks in, that running Doc answers questions a pile of loose notes never could. Because your agent both reads and writes it, you can ask across the whole thing: "What did we decide about pricing in the last three calls?", "What action items are still open and who owns them?", or "Pull everything Tom agreed to this month." You get a straight answer instead of opening five files. You can have it spin the open actions into a Database to track them like a task list, or draft a follow-up message straight from a meeting's action items, with no copy-paste between tools. It is the same upkeep principle behind the CRM: the structure is easy, and letting your agent do the maintenance is what keeps it current.

And because it is built on Stash with the same Google sign-in as the rest of your account, the record is not locked to one assistant. Ask Claude after today's call and ChatGPT after next week's, and both are writing into the same Doc. On cost: AgentDocs has a free tier with no per-seat fees, you connect over one link with no install and no card, and there is a Pro tier for heavier use. It is a new product, so pricing may change as it settles.

The exact prompt

Paste this to your AI agent once AgentDocs is connected. Edit the brackets to match how you run meetings:

Set up a meeting-notes Doc for me in AgentDocs.

Create a Doc called "Meeting notes". For each meeting, write a new section
at the TOP of the Doc headed with the date and a short title
(e.g. "## 2026-06-17 - Pricing sync"). Leave previous meetings below it
untouched, so the Doc stays a running record.

Use this structure for every entry:
- Attendees
- Summary (one or two lines)
- Key points (bullets)
- Decisions (only things that were genuinely settled, stated as decisions)
- Action items (a list, each with an owner and a due date if one was given)

How to handle what I give you:
- I'll paste either my raw notes from a call or a full transcript. Read it,
  drop the filler, and fill in the structure above.
- Pull action items out even when they're buried in a sentence
  ("I'll send the doc Thursday" = owner me, due Thursday).
- Don't invent decisions or owners. If something was left open, note it as
  an open question rather than forcing it into a decision.
- Keep it tight and honest. Don't pad the summary.

Then create the Doc, confirm it's set up, and ask me for the notes from my
first meeting.

That is the whole thing. No template to download, no headings to format. You describe it once, your agent builds the Doc, and from then on you hand it the mess and it keeps the record.

This is the fourth in our "Built in AgentDocs" series, real things built by talking to an AI agent, with the prompt included every time. Next up: a Notion-style workspace your agent keeps current, built on Pages.