Responding to difficult employee feedback

The first critical comment a manager receives decides a lot. Reply well, and the person, and everyone they talk to, learns that honesty is safe. Go quiet or defensive, and the next pulse gets polite answers and nothing useful.

This template is for managers replying to confidential feedback, such as a pulse comment or a message sent any time. In Pulsido these arrive in the feedback inbox, where you reply by name and never see who wrote them.

Every reply needs three things

1. Acknowledge. Show you read it and understood it. Restate the point in your own words, briefly.
2. Thank, and mean it. Telling a manager something hard takes effort. Say so.
3. Say what happens next. A question, an action, a date, or an honest "I don't know yet, and here's when I'll come back to you."

Reply within a few days, even if you don't have an answer yet. A fast "I've read this" beats a perfect reply two weeks later.

Sample replies

Adapt the wording to sound like you. They're starting points, not scripts.

When the feedback is about you

Thank you for telling me this. It isn't easy to say to your own manager, and I'd much rather know. You're saying [restate: the way I run planning meetings leaves no room for the team's views]. I'm going to [concrete change: send the agenda a day ahead and open each meeting with your questions] from next week. If it doesn't feel different in a month, I'd like to hear that too.

When it's angry

I can tell this has been really frustrating, and I'm sorry it's got to this point. You're right that [the part that's fair: the on-call rota has fallen on the same three people]. I'm raising it at Thursday's leads meeting, and I'll reply here by Friday with what we decided.

Respond to the substance, not the tone. If something crossed a line, address the behavior separately and in general terms, never by guessing who wrote it.

When it's vague

Thanks for flagging this. I want to make sure I understand: when you say [communication is bad], is it more about [decisions not being explained], or [hearing about changes too late], or something else? Even a word or two helps me know where to start.

When you can't do what's asked

Thank you for raising pay so directly. I'll be honest: salaries are set once a year in [month], and I can't change that before then. What I can do is [make sure your team's market data is part of that review / explain how the review works at the next team meeting]. I'll come back to you here after [date].

Saying no clearly is better than a vague "we'll look into it" that everyone knows means no.

When it's about someone else

Thank you for trusting me with this. I'm going to look into it. I won't share anything that could identify you, and I won't ask who you are. If you're comfortable telling me more here, about when or how often it happens, it would help. If this involves harassment or safety, please also contact [HR contact or process], who can act on it formally.

Confidential feedback isn't a formal complaints channel. Point people to the right process for serious matters, and follow your company's policy.

When it's a complaint you've heard before

Thank you. You're not the first to raise this, and that tells me we haven't done enough. Here's where it stands: [what's been done, honestly]. Here's what's next: [action, owner, date]. I'll post an update in [place] by [date].

When it's praise

This made my week, thank you. I'll pass it on to [the team / the person you mentioned].

Don't skip the positive ones. Replying to praise shows you read everything, not only the problems.

What not to write

• "Who is this?" or anything that tries to identify the writer. Even a joke ends honest feedback on your team.
• "Let's discuss this in person." You can't: you don't know who wrote it. Offer it as an option instead: "If you'd like to talk it through, my door's open, but you don't have to."
• A defense. "Actually, the deadline was set by the client" may be true, but lead with understanding, not correction.
• A promise you can't keep. One kept commitment beats three broken ones.

Follow-up checklist

• Replied within a few days.
• Recorded any commitment as an action, with an owner and a date. In Pulsido, add it from the conversation under Add action; the action never shows what was written or who wrote it.
• Came back to the conversation when the date arrived, even if the answer was "not yet".
• Shared the outcome more widely, where it's safe to, so others see the loop close. In Pulsido, a finished action can be shared as "You said, we did".
• Archived the conversation once it was done.

Drafting help, with care

If your company has turned on Help me reply, Pulsido can draft a reply for you to edit. It sends the conversation's text to Anthropic's Claude to write the draft, and nothing is sent until you send it. Treat the draft as a first pass: make it sound like you, check it says what you'll actually do, and never send it unread.

Sources and limits

The inbox, actions, and Help me reply behavior described is Pulsido's, as documented in Replying to feedback on 7 November 2026. The sample replies are written for this guide. For serious concerns such as harassment, safety, or legal issues, follow your company's formal process; this template isn't a substitute for it.