Skip to content
Docs menu

Use

How to track client follow-ups with Claude

Three ways to keep client follow-ups from slipping when you work out of Claude — a Project, a spreadsheet, or a CRM Claude can write to — and when each one stops working.

Claude can draft the follow-up, remember what you discussed and tell you who has gone quiet. What a chat cannot do on its own is come back to you on the day something is due. Remembering a follow-up and being reminded of it are different problems, and the second one needs somewhere durable to keep a date.

There are three honest ways to solve it. Pick by how many people you are tracking.

1. A Claude Project, for a handful of people

Put a notes file in a Claude Project and keep appending to it. Claude reads the project every time, so it knows the history without you re-explaining.

Where it stops: nothing is due-aware. The file holds “follow up Tuesday” as text, so you only hear about it if you remember to ask, and you have to re-read the whole file to find what is overdue. Fine for five people; it falls apart around twenty.

2. A spreadsheet Claude edits, for a list you maintain

Keep one sheet with: person, company, last contact, what was discussed, next action, follow-up date, status. Ask Claude to summarise a call and add the row.

Where it stops: it is durable and free, and the structure is yours to keep correct. You are the index: there is no “what is overdue” unless you sort for it, duplicates creep in as “Priya” and “Priya S”, and nothing stops a date landing in the past.

3. A CRM Claude can write to, when the list is real work

This is what Sambandh is. You say what happened in plain language; the contact, the note and the follow-up are saved as records with real dates, and “what is due” becomes a question with an exact answer instead of a memory.

Log that I called Priya at Acme. She wants a demo Tuesday.

What should I follow up on this week?

Which clients with open deals have gone quiet?

The date is stored in your timezone, the overdue list is a query rather than a scroll, and the records outlive the conversation — a new chat, a new device or a new month all see the same list. Setup is one connector URL: see Quick start, or open the live demo to look at a filled-in workspace before you sign up.

Which one to choose

  • Under about ten people, loosely tracked: a Claude Project is enough. Do not add a tool.
  • A list you already keep by hand: a spreadsheet, if you genuinely maintain it.
  • Follow-ups you are paid to not drop: something with dates and an overdue list.

What to watch for, whichever you pick

  • Ask Claude to repeat what it saved. If a note was not written down anywhere, you want to know inside the same message, not next week.
  • Two people with the same first name. Say the company as well. Guessing between them is how the wrong person gets your note.
  • Relative dates. “Next Tuesday” depends on which day you are saying it; check that what came back is the date you meant.
  • Getting your data out. Whatever you use, be sure you can export it, including after you stop paying.