The internal note: where your team's context lives
The most useful thing on a feedback post is often the part customers never see.
Nº 22 · HeedPost team · Oct 3, 2026 · 2 min read
A customer posts a request. Over the following weeks your team learns things about it: sales hears the same ask from two prospects, support finds a workaround, an engineer thinks it's a day's work, a designer has concerns. Where does all that go?
Usually: Slack threads, meeting notes, someone's head. Then, three months later, the person who picks up the work starts from the post's title and nothing else.
Put the context on the post
An internal note is a comment only your team can see, on the same thread as the customer's conversation. It keeps everything about a request in one place: what customers said in public, and what your team knows in private.
What belongs in a note
- What sales and support hear. "Two prospects asked about this on calls this week." This is demand that never shows up as a vote.
- Workarounds. "You can do this today with the API. Here's the script we sent Acme." Now everyone can send it.
- Sizing and risks. "Probably two days, but it touches billing." The first thing whoever plans the work will want to know.
- Decisions and why. "Discussed in planning, parked until after the import work." So the next person doesn't re-open it from scratch.
Mention people instead of messaging them
The best part of notes is pulling a teammate into the thread rather than into a separate chat. "@Raj can we size this?" Raj gets one email, answers right there, and the answer stays with the request forever.
Keep notes and replies separate
The risk with internal notes is writing one when you meant to reply publicly, or the reverse. A few habits help: write public replies as if the customer is reading over your shoulder, because they are. Write notes as if a new colleague will read them in a year, because they will.
Notes make the board a memory
A board without notes is a list of requests. A board with notes is your team's memory of what customers want and what you've learned about it. When people leave, change roles or just forget, the context stays. That's worth a lot more than the minute it takes to write each one.