A private comment inside the conversation — for the team, never the customer.
Internal note. An internal note is a private comment attached to a customer conversation that only teammates can see. Internal notes let a support team discuss a case — ask a colleague, record what was tried, brief the next owner — inside the thread itself, instead of forwarding the email or moving the discussion to a chat app.
Support tools give notes their own compose mode, visually distinct from the reply box — a different color, a different frame — and an @mention in a note notifies the named teammate without touching the customer. The note stays pinned in the thread’s timeline, between the messages it refers to, so anyone opening the conversation later reads the customer’s words and the team’s reasoning in one pass.
The value concentrates at handover. An escalated conversation with good notes carries its own working file — what was tried, what the customer already confirmed, what is still unknown — so the next owner starts from the middle instead of from zero, and the customer is never asked the same question twice by two different people. The notes also become an audit trail: months later, “why did we refund this?” has an answer sitting exactly where the refund happened.
Without notes, case discussion has two homes, both bad. Forwarding the email splinters the thread into private copies that stop updating the moment they are sent. Discussing in a chat app keeps the thread clean but strands the reasoning where the next reader will never find it — the decision is in the mailbox, the “why” is in a channel that scrolled away.
There is also a sharper risk notes exist to manage: the wrong-box mistake, where a comment meant for a colleague goes out as a public reply. Tools that make note mode loud — unmistakable color, separate button — are guarding against the single most embarrassing failure in team email. Treat a note’s privacy as a seatbelt, not a vault: write notes you could survive the customer seeing.
Adopt one rule: if it is about the case, it goes in the case. Questions to teammates, half-finished theories, “waiting on engineering” — all of it as notes, none of it as DMs. Write notes for the next reader, not for yourself: “tried re-sending the invoice, waiting on billing to confirm the VAT number” ages better than “looking into it.”
Two habits pay off disproportionately. Note before you escalate — a summary note is the difference between handing over a case and dumping one. And note the reason when you close anything unusual, because the odd cases are precisely the ones someone will reopen and puzzle over in six months, and the closing note is the only thing standing between them and re-solving it from scratch.
Notes do their best work where conversations change hands — these entries cover those moments.
Give your customers faster answers and your team their evenings back.
Desktop and mobile. Free for solo.