Guide
How do I make sure follow-ups actually happen after client meetings?
You make sure follow-ups actually happen after client meetings by ending the call with named owners and dates, sending a recap the same day, then turning each we-owe line into a follow-up that still fires. A transcript is a record of that hour. A recap is a list. Follow-through is the later nudge, and a person still sends.
By The Concrete team · Published
We make Concrete.
What the job actually is
You make sure follow-ups actually happen after client meetings by ending the call with named owners and dates, sending a recap the same day, then turning each we-owe line into a follow-up that still fires. I'll send the recap is the leak. The transcript sitting in a notes app is a record of that hour. The recap is a list. Follow-through is the later nudge, and a person still sends.
Account leads, consultants, and founders run these calls back to back. Atlassian's Workplace Woes survey of 5,000 knowledge workers found 54% frequently leave meetings without a clear idea of next steps or who owns which task, and 77% are frequently in meetings that end in a decision to schedule a follow-up meeting. A Zoom-commissioned Morning Consult survey of 11,023 knowledge workers, cited in Zoom's 14 October 2025 meeting-statistics roundup, found 54% of employees say summaries and action items should often or always be sent after meetings, and 39% say they are actually sent. A Databox survey of 48 agencies found almost 70% of account managers handle fewer than 10 clients each. ClearFeed's agency guide, updated 31 October 2026, says an account manager can usually keep 10 client channels straight, someone misses a ping around 40, and at 50-plus channels you need unanswered-message alerts. Mursa publishes 4 business hours for standard client Slack, 1 business hour for urgent, and the next business day after hours. Its July 2026 workspace audit logged about 3,100 client-side messages across 14 client channels over 27 weeks.
The buying prompt collapses four jobs: notes after the call, a recap a person sends, a task once someone copies it into a tracker, and a follow-up that still fires on Friday. Prep before the next check-in is a neighboring job, on how to prepare for a client check-in. Promises you typed in email are on how to stop forgetting emails you promised. Lines spoken in Slack threads are on commitments from Slack threads. Quiet clients you are waiting on are on how to follow up with clients who go quiet.
Which tool wins which job
Fund the row that matches the leak. Notes after the call, a recap draft, a task in a tracker, and a follow-up that still fires are neighboring jobs.
| Job | Wins it | Why |
|---|---|---|
| Notes and a transcript after the call | Fireflies, Otter | Fireflies joins as Fireflies.ai Notetaker, records, and writes action items. Pro is $10 per seat per month billed annually, or $18 billed monthly, as of 12 November 2026. Otter Notetaker joins as FirstName's Notetaker (Otter.ai) and cannot join anonymously. |
| Bot-free notes plus a recap draft you send | Granola | Device audio, no bot. Follow-up emails need a paid plan or trial, Google, an external guest, and no more than 10 people. You click Send. Undo is about 10 seconds. Business is $14 per user per month, as of 12 November 2026. Outlook is unsupported. |
| A drafted follow-up email that never auto-sends | Fyxer | Fyxer drafts a follow-up after the meeting on Pro and above. It does not send emails on your behalf. You decide what gets sent. Pro is $37 per person per month billed annually, or $49 billed monthly, as of 12 November 2026. It also records the call when you let it join. |
| Carry-forward of open action items into the next meeting | Fellow | Fellow records and transcribes, then surfaces outstanding action items in the pre-meeting brief for the next session. The recap can go to every participant. The item still has to be done. |
| A task once someone copies the line into a tracker | Asana | Once the item is in Asana, the owner and due date live there. Asana's Anatomy of Work, surveying 10,000-plus knowledge workers, found 60% of time goes to work about work, and 88% say time-sensitive projects have fallen through the cracks. The leak is the line that never left the recap. |
| A reminder you already remembered to set | Slack To-dos | Hover a message and pick Add to-do, or type /remind. Creating a to-do does not set a reminder by default. Shared client channels sit on paid Slack plans on both sides. Pro is $7.25 per user per month billed annually, or $8.75 billed monthly, as of 12 November 2026. |
| A morning list of still-open Slack and Gmail promises, a person still sends | Concrete | Each morning it nudges the owner of every open follow-up. Send / Edit / Skip cards; no auto-send mode. Before each Google Calendar meeting it posts a brief of what is still open. It never joins, records, or transcribes. Design-partner preview; see what it is. |
I'll send the recap is the leak
People on r/SaaS put it as a rule: if it is not assigned, it does not exist. Assign the owner during the meeting. Urgency drops the moment you hang up. I'll look into that is a social gesture until it has a name and a date. People on r/projectmanagement spend the last three minutes reading the actions back with owners and due dates, then run a 48-hour Slack ping to see who has started.
Granola's recap guide says send the recap within 24 hours, and treat same-day as the standard for client kick-offs and other high-stakes calls. HubSpot's customer-meeting guide uses a 40/20/40 split: 40% of the effort is follow-up, and the recap goes out the same day with owners and dates. Atlassian keeps the list to three to five items that actually need to happen before the next checkpoint. Sarah: send the revised proposal to legal by Friday is an action item. Follow up on the proposal is a topic.
A recap that stays in the notes app is still notes. Granola drafts the follow-up from the transcript, calendar, and recent Gmail, then waits for Send. Fyxer drafts in the inbox. Fireflies Pro can generate a follow-up email from the meeting with AI Skills. A draft in the inbox is still a draft. Friday still has to fire. The next check-in starts from that owed list, on how to prepare for a client check-in.
The caveat that should decide the setup
The failure operators name first is a bot on the call. A visible notetaker changes the room. Some clients get stiff. Otter cannot join anonymously. Fireflies appears as Fireflies.ai Notetaker. Fyxer asks to join like any other attendee. Granola listens on the device and offers a watermark or chat message so the room knows. Concrete never joins, records, or transcribes. Follow-through does not require a bot on the call. The notes-versus-prep split is on Fireflies vs a meeting prep tool that doesn't join.
The quieter failure is an AI that sends the recap on its own. Fyxer states that it drafts replies in your inbox, and you decide what gets sent. Granola waits for Send, with about 10 seconds to Undo. A prompt that says draft only is not a send gate. Worst case with a draft is you delete it. Worst case with auto-send is you explaining the email on Monday.
A third caveat is public chase. People in a Slack Connect channel can see messages from bots and apps. A reminder posted in the client thread shows the client you are chasing your own team. Keep the owner's nudge off the thread the client can read. Safety of putting an agent in that channel is on the shared-channel page.
A fourth caveat is the spoken line that never became a message. Concrete reads Gmail and Slack. I'll send the deck Friday said only on the Zoom, then never typed, is a notes job. Fireflies, Otter, and Granola win that capture. Write the line in the recap before you hang up, or it stays in the transcript. Turning meeting notes into tasks is a different setup.
Concrete is an AI employee that works in existing Slack channels and reads Gmail alongside them. It keeps every promise made in a thread, and every thread waiting on a reply, as a follow-up. Each morning it nudges the owner. It drafts the follow-up as a Send / Edit / Skip card in Slack. A Gmail send needs the same tap. There is no auto-send mode. Follow-ups survive reboots. Before each Google Calendar meeting it posts a brief in Slack or Telegram: who is attending, the last emails and Slack threads with them, and what was promised to them and is still open. It does not join, record, or transcribe the meeting. It is in design-partner preview; the longer thesis is on the vision page. It does not run sequences. Spoken promises that never hit email or Slack stay a notes job.
Step by step: the setup for a 3-to-30 person shop
This is the boring version that holds when the founder or account lead still owns the client call. Pin it before the next back-to-back block.
- Step 1: Name owners and dates in the last three minutes. Read the we-owe and they-owe lines back out loud. One owner, one date, each line. If nobody volunteers a date, assign one and let them push back. A line with no owner is still a hope.
- Step 2: Send the recap the same day, a person sends. Decisions, named owners, dates, open questions. Granola treats same-day as the standard for client kick-offs. HubSpot says send it ASAP. Draft from the notes if you want. Send stays a tap.
- Step 3: Turn each we-owe line into an owned follow-up. The recap is a list. Copying it into Asana, a Slack to-do, or a morning board is the step that fails. I'll send that Friday has to fire on Friday even if they reply in between.
- Step 4: Keep the owner's chase off Slack Connect. Nudge the owner in a private channel or a DM. People in a shared client channel can see bot messages. The recap the client sees still waits for a person to send.
- Step 5: Run a 48-hour started check. A Slack ping, not another meeting. If nobody has started or flagged a blocker, escalate before it becomes a problem two weeks later. Atlassian checks in before the deadline, not after.
- Step 6: Sweep still-open promises every morning. Channel history hides thread replies unless you open them. Use a private digest or a morning list. Keep that list off the shared channel. The setup is on the daily summary page.
- Step 7: Open the next meeting from the owed list. Last meeting's transcript is a record of that hour. The next check-in starts from what is still open. Recorders win notes. The standing brief from calendar, Gmail, and Slack is on AI that preps you before every meeting.
- Step 8: Write a reply-time target. Mursa's rule is 4 business hours for standard messages, 1 business hour for urgent, and the next business day after hours. ClearFeed uses 4 hours standard, 1 hour high-touch, and 30 minutes for VIP or launch. Write the window in the recap when you ask them for something.
Questions people ask
What is the difference between a meeting recap and a follow-up that still fires?
A recap documents decisions, named owners, and dates from that hour. Follow-through is the later nudge that still fires when Friday comes. Granola treats the recap as same-day work for high-stakes calls. The we-owe line still needs an owner and a reminder that survives the next back-to-back block.
How soon after a client meeting should I send the recap?
Send it within 24 hours. Granola's recap guide treats same-day as the standard for client kick-offs and other high-stakes calls. HubSpot's customer-meeting guide says send a recap ASAP after the meeting. Waiting longer means you are reconstructing the hour instead of locking the list.
Should a notetaker join the client meeting?
Only if you also want notes. A visible notetaker changes the room. Otter cannot join anonymously. Fireflies joins as Fireflies.ai Notetaker. Fyxer asks to join like any other attendee. Granola listens on the device. Concrete never joins, records, or transcribes. Follow-through does not require a bot on the call.
Should an AI send the follow-up without me tapping send?
For a client-facing recap, a wrong send is the failure that costs the relationship. Fyxer drafts and you decide what gets sent. Granola's follow-up emails wait for Send, with about 10 seconds to Undo. Concrete has no auto-send mode. Draft the chase. A person still sends.
What if the promise was only spoken on the call and never typed?
That line lives in the notes product. Fireflies, Otter, and Granola capture what was said. Concrete reads Gmail and Slack. A spoken I'll send the deck Friday that never hit email or Slack is outside that list. Write it in the recap before you hang up, or it stays a notes job.
Should I chase the follow-up in the Slack Connect channel the client can read?
Keep the owner's nudge off that thread. People in a Slack Connect channel can see messages from bots and apps. A reminder in the shared channel shows the client you are chasing your own team. The recap the client sees still waits for a person to send.
How many action items should come out of a client meeting?
Atlassian recommends three to five items that actually need to happen before the next checkpoint. If every discussion point becomes an action item, nothing is prioritized. Name an owner and a date on each one. A line with no owner is still a hope.
What should happen in the last three minutes of the call?
Read back the we-owe and they-owe lines with owners and dates. People on r/projectmanagement treat those last three minutes as the whole job. Confirm out loud. Then send the recap the same day. The next morning's list is those same lines, still open.
Sources
- Atlassian: Workplace Woes, Meetings Edition (survey of 5,000 knowledge workers), read November 12, 2026
- Zoom: 34 meeting statistics for better time management in 2025, read November 12, 2026
- Zoom: Solving the collaboration paradox (Morning Consult survey of 11,023 knowledge workers), read November 12, 2026
- Databox: Account manager burnout, how many clients are too many (survey of 48 agencies), read November 12, 2026
- ClearFeed: Slack for client communication, a guide for agencies, read November 12, 2026
- Mursa: Slack for clients, manage communication and scope, read November 12, 2026
- Asana: How work about work gets in the way of real work (Anatomy of Work Index), read November 12, 2026
- Granola: How to write and send a meeting recap email (with templates), read November 12, 2026
- Granola: Follow-up emails (paid, Google-only, Send, 10-second Undo), read November 12, 2026
- Granola pricing, read November 12, 2026
- Fireflies pricing 2026: which plan is right for you, read November 12, 2026
- Fireflies: AI notetaker, read November 12, 2026
- Fyxer pricing (never sends on your behalf), read November 12, 2026
- Otter Notetaker overview (visible name, cannot join anonymously), read November 12, 2026
- Slack pricing, read November 12, 2026
- Later is now To-dos (Slack), read November 12, 2026
- Slack Connect guide: Work with external organizations, read November 12, 2026
- HubSpot: How to host the perfect customer meeting (40/20/40, same-day recap), read November 12, 2026
- Atlassian: How to turn meeting action items into trackable work (3-5 items), read November 12, 2026
- Fellow: AI meeting action items (carry-forward in pre-meeting briefs), read November 12, 2026
- r/SaaS: What usually breaks after meetings in SaaS teams, read November 12, 2026
- r/projectmanagement: How do you prioritize and follow up on action items, read November 12, 2026
If your team already runs its work in Slack, start with one role in one channel. Concrete is an AI teammate that works in your Slack channels and asks a person to approve before anything goes out. It is not a chatbot builder, and it never sends on its own.