Meeting follow-up, filed as real tickets
by AGNTOfficialAgent template
From a transcript or notes, an agent extracts decisions and action items, files them in your tracker, and drafts the follow-up email.
Opens in AGNT and takes about a minute.
Didn’t open? AGNT may not be installed here yet. Download AGNT free · Download the .json
- 5
- Tools connected
- ~10 min
- Setup, 4 steps
- Local
- Runs on your machine
- Per category
- You approve
- Any model
- Uses the one you have
What the agent actually does
Nothing that was agreed gets forgotten
A summary tells you what was discussed. The agent extracts what was actually decided, what was explicitly deferred, and what was raised and never resolved — which is usually the most valuable line in the whole document and the one summaries reliably lose.
Actions land in your tracker
Each action item becomes a real ticket in Jira, Linear or Asana with an owner and a due date, linked back to the moment in the transcript where it was agreed. No separate list to transcribe, and no ambiguity about who took it.
Follow-up drafted
The recap email is composed while the meeting is still fresh: decisions, owners, dates, open questions. It waits as a draft for whoever ran the meeting to check and send.
The tools this job needs
Google Calendar
Where the work arrives. The shared clock your workflows can read and write. The agent watches it and reads what turns up in full, rather than matching a rule against a subject line.
Jira
Context the agent pulls in before deciding. The ticket system of record for engineering work. It is read, not just referenced — which is what lets the decision account for it.
Linear
Context the agent pulls in before deciding. Fast issue tracking that deserves fast automation. It is read, not just referenced — which is what lets the decision account for it.
Asana
Where the result lands. Team tasks, due dates and the follow-through between them. Nothing is written here until the agent has formed a view and, where you asked for it, you have approved it.
The brief it works from
This is the actual instruction set the template installs — what the agent is told to do, and what it is told never to do. Every line of it is yours to edit in AGNT after install.
Read the full brief
You turn what was said in a meeting into work that is tracked and owned.
Extract three different things
Decisions — what was actually settled. Actions — what somebody committed to do. Open questions — what was raised and never resolved. That third category is usually the most valuable line in the whole document and the one every summary tool loses, because it looks like an absence rather than a finding.
Owners and dates are the hard part
"We should look at the onboarding drop-off" is easy to extract and useless on its own. Determine who took it, when it is due, and what it depends on. Read the whole conversation to work that out. Where ownership genuinely was never established, say so explicitly rather than assigning it to whoever spoke last — a fabricated owner is worse than a flagged gap, because it looks handled.
File it properly
Create real tickets with owners and dates, following the user's conventions for titles, projects and defaults. Link each one back to the moment in the transcript where it was agreed, so anyone can check what was actually said rather than relying on your paraphrase.
Then draft the recap: decisions, owners, dates, open questions. Leave it for whoever ran the meeting to send.
When the meeting decided nothing
Say that. List the open questions instead. A manufactured action list from a meeting that reached no conclusions is a small lie that wastes real people's time, and it hides the more useful finding — that this meeting may not need to exist.
Never assign work to someone who was not in the meeting without flagging it as a suggestion.
Shown exactly as it ships. The agent inherits whichever model you already use.
The gap between the transcript and the work
Transcription is solved and summarisation is close behind, yet the follow-through problem is untouched by either. The failure is not that nobody knows what was said; it is that turning what was said into tracked, owned work is manual, tedious, and therefore done inconsistently. That gap is where commitments quietly disappear.
Owners and dates are the hard part
Extracting "we should look at the onboarding drop-off" is easy. Determining that Priya took it, that it is due before the next review, and that it depends on the analytics work already in flight requires reading the whole conversation and knowing the team. An agent with access to your tracker can do exactly that, and can flag the items where ownership was genuinely never established rather than inventing one.
Better meetings as a side effect
Once every meeting reliably produces a public list of decisions and owners, the meetings themselves change. Items that were never really agreed become visible as unagreed. Recurring meetings that generate no decisions become obvious candidates for deletion. The artefact ends up improving the process that produces it.
Common questions
Do I need a specific meeting recorder?
No. The agent works from whatever text you have — an exported transcript, shared notes, or a rough paste. It is not tied to one vendor’s recording product.
What if the meeting had no clear decisions?
It says so, and lists the open questions instead. That is a more honest and more useful output than a manufactured action list.
Can it handle recurring meetings differently?
Yes — a standing meeting can carry its own conventions, including which project new tickets land in and which items to check against last week’s.