Automate follow-up on promises made in client meetings
Promises made in client meetings get forgotten once the call ends. A scheduled agent reads the notes you share, lists each commitment with owner and due date, and its department head reviews the list before you approve.
What you’ll set up
Connections
Works from files you share
Inputs
Clients to track · Optional
List, no default
Reminder tone · Required
Choice of friendly, formal, or brief, default friendly
Ready by · Required
Time, default 08:00
Brief · Required
Text, prefilled and editable during setup.
Runs
Runs every Monday at 08:00
Done by Business analyst
Email to new contacts, and follow-ups nobody has answered, waits for your approval by default. Replies in threads a contact has answered, and email to your own team, can send automatically depending on your settings.
You approve every report · Free to start
How it runs
One agent does the work. Its department head reviews it, then you approve.
- 1Business analyst
Runs every Monday at 08:00 and prepares the report from your connected sources.
- 2COO · Review
The department head reviews the report before it reaches you.
- 3You
Email to new contacts, and follow-ups nobody has answered, waits for your approval by default. Replies in threads a contact has answered, and email to your own team, can send automatically depending on your settings.
What you get
Sample, not live data. Names, dates and meetings are invented.
Open commitments, week of 9 March (sample)
You owe Example Co
- Send revised quote. Promised 3 March, no date given. Undated, please set one.
- Introduce their buyer to a supplier contact. Promised 5 March, due 12 March.
Example Co owes you
- Share the brand files. Promised 4 March.
Reminder drafts attached. Needs your approval before anything is sent.
What counts as a commitment
A commitment is a sentence in which someone says they will do something for someone else: send a quote, share a document, introduce a contact, fix a problem. Calendar standards treat this the same way. The JSCalendar specification (RFC 8984) defines a task as an action item, assignment, to-do item or work item that may be due at a certain time, though a due date is not required. The iCalendar standard (RFC 5545) gives a to-do the status value NEEDS-ACTION. The agent captures similar fields for each promise: what, who owns it, who it was promised to, the date mentioned, and a status.
How the scheduled job works
You share meeting notes or a transcript as a file after each call. On its weekly schedule the agent reads everything shared since the last run and pulls out each commitment in the speaker's own words. It separates promises you made from promises the client made, and marks items with no date as undated instead of inventing one. It also checks later notes for signs that an item is done. For each open item that belongs to you, it drafts a short reminder or update message. It reads the files you share alone and does not join calls or log in anywhere.
Review and approval
Before you see anything, the department head agent checks the list against the notes: is every item traceable to a sentence, are owners and dates read correctly, and is any drafted message promising more than the notes say. You then approve, edit or skip each draft, and nothing reaches a client until you do. The list is labelled as AI-written, and it can miss a promise made in a side conversation that never reached the notes.
Using the list
Open with the overdue items, then those due this week. A client-facing promise with no date is the easiest one to lose, so give it a date when you approve the draft. When an item is finished, say so in your next notes. The agent is asked to look for that when it reads them and to mark the item as possibly done, for you to confirm. If a client keeps appearing with several open items, treat that as a signal to schedule a catch-up call.
Questions
Related jobs
Chase late invoices without chasing people who already paid
A morning list of overdue invoices with a drafted, checked follow-up for each. Nothing goes out until you approve it.
Connects to: Invoicing or accounting tool (read) (required)
Weekly business report from your till and accounts
One weekly page that joins till or POS sales with your accounting figures, compares last week and the same week last year, and notes anything odd.
Connects to: Till or POS system (read access) (required), Accounting tool (read access) (required)
Automate a weekly CRM clean-up list for duplicates and gaps
A weekly list of likely duplicate contacts and records with missing fields, ready to review.
Connects to: Remote MCP server with CRM read access (required)