All articles

Client calls that do not lose context between check-ins

Account management across calls — remember commitments without digging through email

Account managers juggle dozens of relationships. Each check-in sounds warm and productive, then three weeks pass and neither side remembers exactly what was promised. Email threads help but bury nuance — tone, caveats, and the moment someone said "we can probably do that by end of month." Client context lives in conversations; your tools should preserve conversations, not just calendar events.

One archive per account

Create a Scriba project for each major client or engagement. Link every call — kickoff, QBR, escalation, renewal — to that project. Cloud sync keeps the archive on every Mac you use. Before a call, spend five minutes in project chat: "Summarize open commitments and risks from our last three meetings." You walk in knowing what you owe and what they expect, without scrolling Slack or guessing from CRM fields.

  • Pre-call: open items, last agreed next steps, stakeholders mentioned.
  • On-call: record locally; no bot changes how the client experiences the invite.
  • Post-call: confirm action list while memory is fresh; update Brain if a key fact changed.

Names and promises matter

Clients remember who said what. Assign contacts in Scriba so people reappear across meetings. When the VP of Ops is introduced for the first time, that name should surface automatically the next time they join. Ask the transcript: "What did we promise Sarah's team about the integration timeline?" You get an answer tied to spoken words, not a generic summary that smoothed over uncertainty.

Trust erodes when you forget a commitment the client can quote verbatim. A searchable transcript is professionalism, not surveillance.

Handoffs within your firm

When coverage changes, the new owner inherits the project archive — not a forwarded email chain and a vague verbal briefing. They read the last two transcripts, skim Brain memory, and ask chat what escalations are still live. Internal handoffs are where context loss hurts most because the client never sees the gap until something slips.

Sensitive calls

Local-first recording means audio and transcripts stay on your machine by default, with sync under your authenticated account. For confidential discussions, you control what lives in the cloud and what stays on device. Ghost mode keeps Scriba off screen shares when you are walking through slides with the client on the line.

Close the loop in writing

After every client call, send a short recap email with three bullets: decisions, actions with owners, next meeting date. Draft it from the transcript so wording matches what was actually said. Clients reply to correct errors immediately; you fix the record before it fossilizes. Over a year, that project becomes the institutional memory of the relationship — and every check-in feels like a continuation, not a reset.

Keep reading