# How to Prepare Client Call Talking Points That Build on Past Decisions

> Prepare client call talking points from past conversations. Carry decisions forward, ask about open items, and recognize when new facts justify a review.

- URL: https://www.hemory.com/blog/searchable-memory/client-call-talking-points/
- Language: English (en)
- Author: Hemory Team
- Published: 2026-11-02
- Last updated: 2026-11-02
- Summary: Prepare a client call around one desired outcome. Use relevant discussions in Hemory directly or through a supported connected agent to draft talking points early. Separate decisions that still apply, open questions, and new facts that may justify review. A copyable template and rollout-support example show how to carry an agreement forward without inventing owners, dates, or readiness. Review the claims that would change the call.
- Tags: client call preparation, talking points, past decisions, conversation memory

Your client chose a phased rollout on the last call. As you prepare for the next one, you remember the choice but not why it was made. “Should we reconsider the rollout?” feels like a reasonable question—until the client has to repeat an explanation they already gave.

Useful talking points carry the earlier decision forward, surface what still needs an answer, and identify any new development that deserves discussion. Here's how to build them from past conversations without turning the next call into a repeat of the last one.

## TL;DR

- Recover the decision and the reason that matters to this call, then distinguish open questions from agreed choices.
- A changed constraint can justify reopening a decision. Forgetting the original reasoning is a reason to retrieve it first.
- With Hemory, use captured discussions to prepare talking points directly, or let a supported connected agent retrieve the background and draft them.
- Review statements that imply approval, responsibility, deadlines, or changed scope. A short speaking outline is the goal.

## Decide What the Next Call Needs to Achieve

Start with one outcome: agree on a launch dependency, resolve a remaining support question, or explain the effect of new information. This tells you which parts of the earlier discussion are relevant.

For example, a call about staffing the first rollout phase needs the agreed scope, the staffing assumptions, and unresolved ownership. It probably doesn't need a recap of every option considered during procurement.

Write the outcome in a sentence you can use while preparing:

> Leave the call with an owner for first-week support and a date for confirming availability.

This is more useful than “catch up on the rollout.” It gives the conversation a destination and keeps your retrieval focused.

For the broader preparation process, see our guide to [preparing a client follow-up call](/blog/searchable-memory/how-to-prepare-for-a-client-follow-up-using-conversation-memory-without-rereading-threads/).

## Retrieve the Background and Start a Draft

Hemory preserves captured discussions as transcripts and organized Memory, including decisions, discussion points, and unresolved questions. You can use that material to recover the client's reasoning without having to write a fresh account of the earlier call.

If you use an AI agent connected to Hemory through a supported connection, give it the task and the clues you remember. It can work from the accessible conversation context to help prepare the draft. Add current information from outside those discussions when it changes the call—for example, a staffing update you received today.

If your AI agent is connected to Hemory, you can ask:

```text
Prepare talking points for my next call with Northstar about
first-week support for the phased rollout.

Use the relevant Northstar discussions available through Hemory.
Start with the rollout decision from our last client call and check
for any later explicit changes in the available discussions.

Find:
- the agreed scope and the reason for choosing it;
- unresolved support questions;
- any agreed condition for revisiting the rollout decision.

Draft a short opening, up to three talking points, and a closing question.
Include a point about changed circumstances only when relevant.
Keep the agreed scope separate from new proposals. Include source
references for the decision and any important condition.

Current information: our support lead can attend the next call.
Call objective: agree on an owner and a date for confirming coverage.
```

The connection determines which conversations the agent can access. Supply an important update separately if it lives elsewhere. You can also prepare the outline yourself from Hemory's summaries and follow-up questions; the structure below works either way.

## Sort the Material by What You Should Do With It

Finding a decision isn't enough to decide how to discuss it. Separate the material into three groups:

| What the record shows | How to use it on the call | Example wording |
|---|---|---|
| A decision that still governs the work | State it briefly and discuss the next step | “We're proceeding with the two-location rollout. Let's settle the support coverage.” |
| A question left unanswered | Ask for the missing choice or information | “Who will own support during the first week?” |
| A new fact that may change the decision's basis | Explain the change and propose a focused review | “One location will close for refurbishment. We need to check whether the agreed rollout still makes sense.” |

An old objection does not automatically become an open question again. Equally, calling a decision “settled” should not prevent the client from changing it. The question is whether you have a relevant reason to revisit it now.

When the record shows a choice but no clear rationale, you can still state the choice. Ask for the missing reason only if it affects the current task. A call about support ownership doesn't always require reconstructing why every alternative was rejected.

## Build Talking Points That Sound Like a Conversation

Talking points should help you speak, not require you to read a meeting transcript aloud. Each point needs a purpose and enough detail to make the next question useful.

Use this short template:

```text
Call outcome:

Opening:
What we agreed, with the reason relevant to this call.

1. Progress or consequence:
What follows from the decision, and the current information to share.

2. Open item:
The specific choice or answer needed from this conversation.

3. Change, if relevant:
What new information affects the earlier agreement, and what part
of the decision needs review. Omit this point if nothing changed.

Close:
The next action, proposed owner, and timing to agree.

Preparation references:
The earlier discussion and any current update used above.
```

Keep the references in your preparation notes. You don't need to announce a transcript date before every point. Mention the earlier conversation naturally when it helps the client follow the connection: “When we discussed the rollout last week…”

## Example: Move From an Agreed Rollout to a Support Decision

Suppose the client chose two locations for the first phase so the operations team could support the rollout with its existing staff. Support ownership was left open. The client also said they would revisit the scope if the staffing plan required additional hires. No later change to the rollout scope appears in the available discussions.

A useful outline could read:

**Call outcome:** Agree who will coordinate first-week support and when coverage will be confirmed.

**Opening:** “We agreed to start with two locations so your operations team could support the rollout with its existing staff. Today I'd like to settle first-week coverage.”

**Talking points:**

1. “Our support lead is available to help plan coverage. Let’s map the support each location will need.”
2. “Who on your side should coordinate that first week, and what availability still needs confirming?”
3. “If the coverage plan requires additional hires, we'll need to revisit the scope we discussed. Does today's plan raise that concern?”

**Close:** “Can we agree on the coordinator and a date for confirming availability?”

The third point checks a relevant condition; it doesn't claim that hiring is already required. The outline also avoids inventing a support owner or presenting the rollout as ready to launch. It moves from an agreed scope to the next unresolved decision.

## Review the Few Details That Could Change the Call

Before using the outline, check the claims that would create a different understanding of the work:

- **Agreement:** Does “we agreed” describe an actual accepted choice?
- **Scope:** Is the point about the first phase, a later phase, or the whole project?
- **Responsibility and timing:** Are owners and dates confirmed, or are you proposing them?
- **Change:** Is the new information enough to justify a review, and do you have its source?

Return to the relevant passage when one of these is unclear. If the answer is genuinely missing, ask a narrow question. “Did we settle who would cover the first week?” is more useful than reopening the entire rollout plan.

For your next call, use [Hemory](/features/) to bring forward the relevant discussion before building the outline. You can spend the preparation time deciding what needs to happen next, with less time spent remembering and retyping what happened last time.

## FAQ

### What if the client wants to revisit an agreed decision?

Ask what has changed or what concern remains. Restate the earlier reason briefly, then discuss whether the new information affects it. The purpose of preparation is a useful conversation, not preventing the client from reconsidering.

### What if I can't find the original agreement?

Check another likely record or a more specific conversation clue. A missing search result doesn't prove there was no agreement. If the distinction matters to the call, prepare a focused confirmation rather than presenting your recollection as settled.

### How is this different from a client follow-up email?

Talking points prepare you for a live exchange. They include questions, possible changes, and an outcome to reach together. An email usually needs a clearer self-contained message and a specific request the recipient can answer asynchronously.

### Do I need to summarize past calls before an agent can help?

When a supported agent can access the relevant Hemory context, give it the goal and useful clues rather than rewriting the calls first. Add information outside that accessible record and review important commitments in the draft.