How to keep track of client conversations
Seven clients, and every one of them is a running conversation — half of it in email, some of it on calls, the rest in meeting notes and the aside on the way out of the room. Here's how to keep a record of client conversations you can actually get back, with tools you already own, and where each method quietly hands the job back to you.
You don't lose client conversations. You lose the thread of them. The scope discussion with Acme started in a March email, moved to a call, was revised in a meeting, and got its last word in a text on a Friday afternoon. Ask yourself "what did Acme say about scope?" and the answer is true in four places and complete in none of them.
Most advice on this question is written for a sales team logging touches in pipeline software. If you're a partner, a principal, or a solo operator with a handful of long relationships, your need is different: not a log that a conversation happened, but a record of what was said, retrievable next March without a twenty-minute hunt. Below is the system that works for that — real methods first, each one honestly ceilinged — and then the part nobody has solved well.
1. Keep one conversation log per client — not one per channel
The unit you care about is the conversation, not the medium it happened in. The moment you keep email in folders, call notes in one app, and meeting notes in another, every question about a client becomes a reconstruction project across three places. So the first move is a client conversation log: one dated timeline per client, newest entry at the top, one entry per conversation wherever it took place.
- One log per client, no exceptions. Acme's scope conversation never shares a page with another client's renewal. When you open Acme's log, everything on it is Acme.
- One line per conversation, dated, with the channel. A working entry looks like:
12 Mar — call — Jordan Kim — Scope: dropping the reporting module. She owns the revised SOW by 19 Mar.Short enough to write in the gap before the next thing; specific enough to be useful in a year. - Names and dates in full. "Jordan, 12 Mar," never "JK, today." Search only finds what you typed, and "today" is meaningless by Thursday.
Where the log lives — a running note, a spreadsheet tab, a CRM record — is section 3. The structure matters more than the container. If your bigger problem is keeping eight clients from blurring into each other, start with our guide to keeping track of multiple clients, then come back for the log itself.
2. After every conversation, write down three things — and a pointer
A conversation log fails in one of two directions: it becomes a word-for-word account nobody rereads, or it's so thin that "spoke to Acme" is all it says. The fix is a fixed shape. Every entry captures three things, and a fourth that tells you where to find the original.
| Capture | Write it as | Why it matters later |
|---|---|---|
| The decision | "Dropping the reporting module from the scope." Or, just as useful: "No decision — she wants the CFO's view first." | What was settled, or explicitly left open, is what you'll be asked about in November. "Discussed scope" tells future-you nothing. |
| The owner | "Jordan owes the revised SOW." "I owe the pricing memo." | Every conversation ends with someone holding the next step. When that someone is you, this line is the only place it's written down. |
| The next date | "Due 19 Mar; check-in call Thursday the 26th." | A conversation without a next date isn't tracked — it's hoped for. This is what turns a log into something you can act on. |
| The pointer | "See thread 'Q3 scope', 12 Mar." "Voice memo, 12 Mar." | The log holds your summary. When the client says "that's not what we agreed," you'll want their words — and the pointer is how you find them. |
Write it in the minute after the conversation, not in a tidy-up session at the end of the week. Recall is sharpest and fading fastest in that first hour. If you're walking between meetings, dictate the entry instead of typing it — a rough line made in the moment beats a clean one reconstructed the next day. The post-call note and the meeting note are the same discipline with a longer form; the log entry is the one line that points at them.
3. Pick the simplest tool you'll still be using in March
The tool is the least important decision here, and the one people spend the longest on. The test is not features — it's the number of steps between hanging up and the entry existing. Every extra step is a day the entry doesn't get written.
| Tool | Good at | Where it breaks |
|---|---|---|
| Notes app, one running note per client | Fastest to open on a phone between meetings, which is when entries actually get written. Search finds any name you typed. | Scanning across clients — "who owes me something this week?" — means opening every note. |
| Spreadsheet, one row per conversation | Columns for date, client, channel, decision, owner, next date. Sort by next date and you have a follow-up list for free. | Entries that need more than a cell. And it's the app you're least likely to open standing in a corridor. |
| Email folders, one per client | The email half of the conversation is already there, in the client's own words, with dates. | Only the email half. Calls and meetings never enter it unless you email a recap to yourself or the client — which, as it happens, is a good habit. |
| CRM | Several people working the same client; notes that need to sit next to pipeline or billing. | Logging a call is a form. For one person and a handful of relationships, it's more system than the problem deserves, and the notes field goes quiet by week three. |
For most client-facing professionals, the running note wins on the only metric that matters: it gets used. Pick it, or the spreadsheet if sorting across clients is the thing you need daily, and stop evaluating. The log you keep beats the log you configure.
4. Make the log the merge point for every channel
The reason conversations get lost is that they cross channels. A record of communication with clients has to be the one place where every channel lands, which means each channel needs its own thirty-second move into the log:
- Email. The thread is its own record; don't copy it. Add one entry with the decision and a pointer to the thread. After a call, send the client a two-line recap by email — it confirms what you heard, gives them a chance to correct you, and puts the call into the one place you already search every day.
- Calls. The one-line entry the moment you hang up. Dictate it if you're moving.
- Meetings. Paste the decisions and owners from your meeting notes into the log — not the whole note. The log is the index; the note is the archive.
- Texts and hallway asides. These are the ones that vanish, because they never feel like a conversation until they matter. A screenshot or one line, the same day.
The same shape works for keeping track of conversations at work more generally — one running log per person or per project, same three fields — which is why a few people end up with a log for their own boss. Then the last habit: before you speak to a client, reread the last three entries. Ninety seconds, and you walk in knowing where the conversation left off. Our guide to keeping track of follow-up emails covers what to do with the "owner" and "next date" columns between conversations.
Where every conversation log breaks
Look at what every method above has in common: you write the log. You carry the decision from the call into the note, the pointer from the thread into the entry, the screenshot of the text into the client's page. It's a good system, and it has three honest limits.
First, the log is exactly as complete as your busiest day. The reply that lands at 3:42 on Thursday, while you're in another client's session until seven, is the one that never gets an entry — and it's the one Friday's 9 AM call is about. The conversations you most need in the log are, by their nature, the ones that happen when you have no time to log them.
Second, the log holds your summary, not the source. When the client says "that's not what we agreed in March," your log says what you wrote down. Their words are in a thread you now have to find, and a pointer only helps if you wrote one.
Third, the merge is manual, and it doesn't scale. Four channels into one log is fine for three clients. At seven, the log is a fifth channel to maintain, and the one you're carrying entries into is the one that falls behind.
A different answer: an assistant who keeps the log for you
This is the gap Equerry is built for. It's a personal assistant, not another place to type. You keep having conversations the way you do now; what changes is that the record assembles itself from the conversation's own sources, and you ask it what was said.
- CC the thread once. Add your Equerry address (something like
chris@mail.getequerry.app) to the Acme scope thread. Every reply that lands after that is kept automatically — no line to write, no pointer to add, no re-forwarding each new version of the SOW. - After a call, dictate the entry as a voice memo. Sixty seconds — the decision, the owner, the next date — and it's remembered alongside the emails, without you typing it up.
- The rest goes in the way you already capture it. The revised SOW the client sent as a PDF, the whiteboard from the meeting, the screenshot of Friday's text — share them in and they're remembered together with the thread and the memo.
- Ask, and get the source. "What did Acme say about scope in March?" comes back with the answer and a source chip pointing to the exact email or voice memo it came from — the client's words, not your summary of them.
- Walk into the next conversation briefed. Before Thursday's call, Equerry can brief you on where the scope conversation stands, including the reply that arrived while you were in another session. If Jordan owes you the SOW by the 19th, ask to be reminded and you will be.
- It's on only the threads you choose. Equerry is never connected to your inbox. It knows the threads you CC or forward and the notes, memos, and files you share — and everything it remembers is visible and deletable in Settings, any time.
The difference from the log isn't a nicer template. It's that the log stops being something you write and becomes something you ask. The conversation's own sources — the thread, the memo, the document — are the record, and retrieval, with the source attached, stops being your job.
Start with the system above today: one log per client, three fields and a pointer, the simplest tool you'll keep using. It costs nothing and it works. When you find that the entries you skip are the ones you needed, the fix isn't more discipline — it's an assistant who is on the conversation. See how the same approach keeps a record of client calls and stays on top of the replies you're waiting for.
Frequently asked questions
What is a good program to keep track of clients?
For one person running a handful of long relationships, a notes app with one running note per client — or a spreadsheet with a tab per client — is usually enough, and simple is the point: a conversation log only works if you can write in it within a minute of each conversation, from your phone, between meetings. A CRM earns its place when several people work the same client or when notes need to sit next to billing and pipeline. Whatever you choose, judge it on one thing: how quickly it hands back what the client said last March, not how neatly it stores it.
How do I keep track of my clients?
Keep one conversation log per client, write three things after every touch — the decision, who owns the next step, and the date the conversation is due to continue — and reread the last few entries before you speak to them again. That covers the tracking. What breaks is the writing: on the busiest days the entries don't get made, and those are exactly the conversations you'll need later.
What is the simplest software to organize client conversations?
The simplest is whatever has the fewest steps between hanging up and the entry existing. A notes app with one note per client, opened from your phone, usually wins; a spreadsheet is a close second if you want to sort and filter across clients. Anything that makes you fill in a form to log a call gets abandoned by week three. Simpler still is not writing the entry at all — an assistant you CC on the thread keeps the conversation from its own source, and you ask it what was said.
How do freelancers keep track of client messages across platforms?
By choosing one place as the log and treating every other channel as a feed into it: an email thread gets a one-line entry with a pointer to the thread, a call gets a line the moment it ends, a text gets a screenshot or a line the same day. The honest limit is that you are the one carrying every message across, so the log is only as complete as your busiest week. The step past that is an assistant who is on the conversation itself — CC'd on the email thread, handed the voice memo after the call, sent the screenshot — so the record assembles itself and you ask it what was said.
Last updated 2026-09-07.