Every agency and consultant knows the same-day recap is the right thing to do. Almost nobody does it consistently, and the reason is not discipline. It is that the recap costs thirty to forty minutes of writing at exactly the point in the day when you have another call, and it is the one deliverable no client has explicitly paid for.

So it slips to tomorrow, then to "I'll cover it in the weekly", and then a month later there is a disagreement about what was agreed and no written record on your side of it.

Why the same-day recap is worth more than it looks

Three things happen when the recap lands before the client's day ends.

It sets the record while it is uncontested. A recap sent an hour after the call is a summary. The same recap sent three weeks later, during a disagreement, is a position. The first gets a "yes, that's right"; the second gets scrutinised line by line. Getting agreement cheaply, in writing, at the moment nobody is arguing, is the single most valuable thing a recap does.

It makes the work visible. Clients do not see the thinking between meetings. A recap that says what was decided and what happens next is often the only evidence of momentum they receive that week. Agencies that send them are perceived as more responsive than agencies doing identical work silently.

It stops scope from moving quietly. Briefs do not usually change in one dramatic conversation. They drift, one reasonable request at a time, each said in passing on a call. A written record of each one is what turns "but we always assumed that was included" into a normal, unemotional change conversation.

Why it does not happen

The honest answer is that the recap is unpaid, unglamorous admin that competes with billable work, and it lands on whoever is most conscientious — usually the same person every time.

The conventional fixes do not work well. Assigning a junior to take minutes means the most junior person is deciding what mattered. Recording the call and sending the recording is not a recap; it is homework you have given your client. And templates only address the formatting, which was never the slow part — the slow part is going back through an hour of conversation and working out what actually got decided.

The workflow that does work

The recap needs to be drafted by the time the call ends. Not easier to write, not templated — already written, waiting for you to read it.

That means three things have to be true.

The capture has to be invisible to the client

This is the part agencies underestimate. A notetaker bot appearing in the participant list on a client call creates a moment: what is that, who else is listening, is this being stored somewhere. Some clients will not care. Some will ask you to remove it. A few have policies that say no.

Lunar is a desktop app that captures your microphone and your computer's system audio directly, so nothing joins the call on Zoom, Google Meet or Teams. There is no participant to explain and no link to send. The wider case for that is in recording meetings without a bot.

None of this removes your obligation to tell people you take AI notes — consent norms vary by country and by client, and the courtesy is worth more than the convenience. What it removes is the third party in your data path, not the conversation.

The summary has to be written for someone who was not there

A transcript is not a recap. Neither is a list of everything said. What a client needs is decisions, approvals and next steps, in the order they matter, with no filler.

That shape matters because the recap has a second job: it is read by people who were not on the call. The stakeholder who missed it, the finance contact who approves the change, the developer who picks up the work. If it needs the context of having been present, it does not do that job.

The next steps have to land somewhere real

The recap tells the client what happens next. Something has to make it true.

In Lunar the action items from a call become Jira issues in that client's project — each client folder is bound to its own project once, with a default issue type and assignee, so nothing crosses over between accounts. You review the proposed issues, click, and the backlog matches the recap you are about to send. The mechanics are in turning meeting action items into Jira issues.

This is what stops the recap from being a promise. The email and the backlog say the same thing, on the same day.

What a good client recap contains

Keep it short enough to be read on a phone between meetings.

• What we decided. Three to five lines, the decisions only.

• What we agreed to change. Anything that moved scope, timeline or budget — stated plainly, not softened.

• What happens next, and who owns it. Names and dates, on both sides. The client's actions belong here too.

• What we still need from you. The most-skipped section and the one that saves the most time.

• Anything raised and parked. Ideas that came up and were not taken forward. This is the section that prevents "we mentioned that months ago" later on.

Read it before sending. Always. An AI draft that reaches a client unread is how a misheard number becomes a written commitment — the tool removes the typing, not the judgement.

Frequently asked questions

Will my client see that I am recording?

Nothing appears in the participant list, because Lunar captures on your machine rather than joining the call. Whether you tell them is a separate question, and you should — consent rules vary by jurisdiction and "I take AI notes, I'll send you the summary" is an easy sentence that usually improves the relationship rather than damaging it.

Can I send the summary as it is written?

It is written to be read by someone who was not in the room, so usually yes after a read-through and a tone adjustment. Treat it as a strong draft, not outgoing mail.

How does it handle several clients?

Each client gets a folder bound to its own Jira project with its own defaults, so action items land in the right backlog automatically and nothing bleeds between accounts.

What if a client asks where the audio goes?

Sessions stay on your machine until you sign in, and transcription can run fully on-device if you choose — which makes that a much easier question to answer than explaining a sub-processor chain. See on-device meeting transcription.

Does this work for calls that are not on Zoom?

Any call that makes sound. Capture happens at system audio level, so the platform is irrelevant.

The point

The same-day recap is the cheapest trust-building mechanism in client work, and it fails for an entirely mechanical reason: it costs an hour you do not have, right when you do not have it.

Remove the hour and the habit becomes automatic. So does the paper trail.