# How to Follow Up on Customer Feedback You Didn’t Act On

> Revisit customer feedback that never became a task. Recover the original context, check what changed, and prepare a useful follow-up without assuming a problem.

- URL: https://www.hemory.com/blog/searchable-memory/follow-up-on-customer-feedback/
- Language: English (en)
- Author: Hemory Team
- Published: 2026-11-02
- Last updated: 2026-11-02
- Summary: Reopen useful customer feedback without assuming it was an unresolved promise or a proven problem. Recover the original observation, check later updates, ask a neutral question, and decide the next step from the response. A shared-tablet training example separates the customer’s statement from possible implications. Hemory and a connected agent can help retrieve context and draft the follow-up.
- Tags: customer feedback, customer follow-up, conversation context

While preparing the next customer training session, you remember a comment from months ago: staff shared tablets during onboarding. It never became a task. Now you are designing exercises that assume everyone has a device, and the old comment suddenly matters.

Recover the original context, check whether the situation has changed, and ask a focused question. The goal is to find out whether the feedback affects today’s work—not to assume every unaddressed comment is a complaint or an unfinished commitment.

## Decide why the comment matters now

Start with the current decision. In the training example, you need to know whether individual exercises fit the available devices. That gives you a reason to revisit the observation.

Other comments may remain useful background without needing follow-up. A remark about an old office layout does not require a new message unless it affects the work you are preparing.

Distinguish this task from following up on a promise. If you agreed to send an exercise and never established its delivery, use the [client commitments routine](/blog/searchable-memory/client-follow-up-commitments/). Here, the original comment did not create an agreed action.

## Recover the observation before interpreting it

If the discussion was captured in Hemory, search using the customer, training topic, and clues you remember. For help with incomplete recollection, see [finding customer comments without tags](/blog/searchable-memory/find-customer-comments-without-tags/).

Once you locate a relevant conversation, ask its built-in Q&A:

> What did the customer say about shared tablets, and which activity or group were they describing?

Read enough of the exchange to establish the scope. “We share tablets during onboarding” does not establish that employees share accounts in daily work. Nor does it establish that sharing caused difficulty. The distinction matters when you write the follow-up.

A working note can separate three things:

| Item | Shared-tablet example |
|---|---|
| Original observation | Staff shared tablets during onboarding |
| Possible implication for today’s task | Individual exercises might need a different arrangement |
| Question to confirm | Does sharing still apply, and did it affect the exercises? |

Hemory preserves spoken details that may not have seemed actionable at the time. You can return when a new task gives them a purpose instead of trying to predict every future use during the customer conversation.

## Check whether later information already answers the question

Look for relevant updates before asking the customer to repeat themselves. A later note might say that one pilot group received individual devices. Check whether that update covers the group in the upcoming session before treating the issue as resolved.

If a current account record already answers the question, use it. If no update is found, say the present setup needs confirmation. Missing search results do not establish that the situation is unchanged.

For several related discussions, ask an AI agent connected to Hemory:

```text
Help me revisit the earlier comment about shared tablets at Westhaven.
Use the available training discussions and the current session details
I provide. Identify the original audience and activity, and any later
update that applies to the upcoming session.

Separate the customer's observation from possible implications for our
exercises. Draft a neutral follow-up only for details that remain unclear.
Do not assume device sharing caused a problem or that we promised a fix.
Include relevant sources in the preparation note where available.
```

Supply current messages or session plans through the agent’s other supported tools when they are not available in Hemory context.

## Write a follow-up the customer can answer

An illustrative message is:

> You mentioned that staff shared tablets during onboarding. Is that still the setup for the next session, and did it make any part of the exercises difficult? We’re preparing the activities and want to make sure they fit how the group will participate.

The message explains why you are asking now. It also leaves room for the customer to say that sharing worked well, that the setup changed, or that a specific exercise was difficult.

Avoid writing, “We know shared devices were a problem, so we’ve redesigned the session.” That turns your interpretation into a customer finding and implies a solution before you have confirmed the need.

If a commitment was made and missed, acknowledge it directly. Do not use the neutral wording above to avoid addressing an actual obligation.

## Choose the next step from the answer

Suppose the customer replies that tablets are still shared and that paired discussion exercises work well, but individual timed quizzes do not. This is new feedback, not something established by the original comment.

You can now propose a targeted change:

> We can replace the individual timed quiz with a paired exercise for this session. Would that fit the group? We’ll keep the final activity plan open until you confirm.

Record the distinction between the finding and the proposal:

```text
Current finding
Shared tablets remain in use. Customer reports that paired discussion
works well, while individual timed quizzes are difficult.

Proposed response
Replace the individual timed quiz with a paired exercise for this session.
Customer confirmation pending.

Next step
Confirm the proposed activity, then update the session plan.
```

If the customer says the setup has changed and the current plan works, close the question. If the feedback belongs to another team, preserve that scope instead of applying it to the whole account.

## FAQ

### Should every old comment get a follow-up?

No. Revisit it when it could affect a current task or when the customer would benefit from an answer. Useful background does not always need an action item.

### What if I cannot find the original discussion?

Describe your recollection cautiously and ask for confirmation. Do not put an exact quote in the message unless you have a record that supports it.

### Where should the result go?

Put an agreed change in the working plan and any action in the system used to track it. Keep enough source context to explain the change without maintaining a second account history.

Use [Hemory](/features/) to recover a customer observation that has become relevant again. Then ask the question today’s task needs, rather than turning an old remark into an assumed problem.