# What should I write down after a call or meeting so nothing is lost?

Turn meeting notes into action items: who, what, by when, the next step and the reason, written from one sentence after the call.

Published: 2026-10-12  
Canonical: https://felesh.ai/blog/what-to-write-down-after-a-call-or-meeting

## What to write down after a call or meeting

A call ends. The other person says they will send the figures over, and you say that sounds fine. You put the phone down, turn back to the work in front of you, and the promise settles into the back of your head. Later the figures have not arrived. You know the conversation happened. You are no longer sure what you agreed.

The list of what to write down is short. Write who you spoke to. Write what was decided; the exact wording matters less than the direction. Write what each person promised, and by when. A date is what lets you notice a promise is late. Then write the next step, the thing that should happen because of the call, and who will do it. Finally write the reason. The reason lets you look at the note later and know whether the decision still holds.

People often skip the reason. They keep the fact and lose the context. Then a customer asks for a change, and the note cannot explain why the original decision made sense.

The next step goes missing too. You leave the call knowing exactly what to do. The moment you start another task, that knowledge goes quiet.

The list is short enough to keep by the phone, and easy to skip. When the call runs long, the note becomes "spoke to the supplier, all fine". Later that sentence has no weight. The promise is gone, and the reason is gone with it.

In short: who, what was decided, who promised what and by when, the next step, and the reason.

## From meeting notes to action items

Meeting notes often fail because they are written as a record of the past. An action item is a promise about the future. When the two are mixed, the promise hides. You read the note to find it, and if you are short of time you read the opening line and move on.

The usual notes look thorough. They record the discussion, the objections and the point where everyone agreed. Then they stop. The decisions are buried in paragraphs, and the paragraph does not say who is responsible or when the work is due.

An action item with no owner has no one to notice when it slips. One with no date has no moment when it becomes late. It sits in the note, waiting for someone to remember it. The note looks finished: it was written, it was filed, and nobody looked at it again.

"Action items: follow up" fails because it names the task but not the person, the date or the reason. A useful action item has a verb, a person, a date and a reason. If any part is missing, you will need another conversation to find out what was meant.

Write for the person who reads the note after the meeting, who is usually you. Ask while writing: will this note tell me what to do next? If it will not, the meeting may have been useful, but the note will not be.

## Client call notes that stay useful

A client call note is not a record of the conversation. It is a record of what changed because of it. A useful note answers three questions: what did we agree, who is doing what, and when will we know.

Plain facts beat good feeling. "Explained the delay, apologised, promised revised dates" is better than a paragraph about the mood of the call. It tells you what the customer was told and what you now owe them. It also tells you whether the next call starts with an apology or with news.

Record the customer's own words where it matters. If the customer said the deadline is fixed, write that down. Your paraphrase may soften it later into "the customer was a bit worried", and the original words keep the note honest.

The test is simple. Read the note when the call is no longer fresh. If it brings back the promise, the date and the reason, it works.

## A client communication log that does not need evenings

A communication log starts well. Entries are written while the call is fresh. Then the day fills up, and the entry becomes a chore. The log is meant to be the memory of the business, but it depends on someone giving it an evening, and after a busy stretch it falls silent.

The evening write-up is the weak point. It depends on memory, and memory has moved on. The call that mattered at the time is hard to separate from the rest of the day. The later note is shorter than it should be.

The fix is to cut the write-up down to the part that cannot be reconstructed afterwards: what happened, said once, straight after the call. Everything else, the note, the dates and the follow-up, can be drafted from that.

## One sentence instead of a write-up

This is how it goes in Felesh. You type one sentence about what happened. That is the whole input.

Felesh drafts the note, the promise with its date if you gave one, and the next step. Each draft shows its reason beside it and waits for your yes. If the next step is a task, the task is added directly, with no approval step.

Imagine the call ends. The customer says they will look at your proposal and send an answer. You type a sentence that says exactly that. If the customer named a date and you included it, the promise carries it. The note, the promise and the next step come from that one sentence, and you decide whether they stand.

The sentence can be plain. It needs to say what happened, and nothing more.

Later, when you need to recall what a customer promised, ask Felesh a question in your own words. It answers from your own records, so the log is something you can use rather than something you maintain for its own sake.

## Try it after your next call

After your next call the conversation will still be with you. Type a sentence about what happened, and see the note, the promise and the next step come back as drafts with their reasons. Say yes to the ones that are right.

You can talk to Felesh in plain words, and see how [the note after a call](/features#after-the-call) works.