Internal Notes vs Public Replies in Zendesk: The Complete Guide (2026)

That choice comes down to internal notes vs. public replies. This guide explains the difference, exactly who can see each, how to switch between them safely in the Agent Workspace, how @mentions, CCs, followers, and side conversations fit in, how to stop accidental public replies, and how to automate comment privacy with triggers — all verified against Zendesk's current documentation.

A quick disclosure: we build Macha, an AI agent layer that runs on top of Zendesk, so we live in this composer every day. This is a practical guide first; there's one honest aside near the end about where AI fits.

The core difference: public reply vs. internal note

Zendesk gives every ticket comment one of two privacy states:

• Public reply (public comment): visible to the ticket requester and anyone CC'd on the ticket. Adding a public comment normally triggers an email notification to the requester and CCs (Zendesk: Adding comments to tickets).
• Internal note (private comment): visible only to agents — never to the requester or to any end users CC'd on the ticket. Customers cannot see internal notes (Zendesk: Can customers see private notes?).

"Internal note," "private note," and "private comment" all refer to the same thing. Use a public reply to talk to the customer; use an internal note to talk to your team about the customer — diagnostics, escalation context, account flags, "I already issued the refund, closing out."

The visual cue that prevents disasters

The fastest way to know which mode you're in: internal notes show a yellow background in the composer and on the ticket timeline. That yellow is your visual confirmation that what you type will stay private (Zendesk: Composing messages in the Agent Workspace). No yellow means you're in a public reply and the customer will see it. Train every new agent to glance at the color before they hit submit — it's the cheapest insurance against a costly mistake.

How to switch between public reply and internal note in Agent Workspace

In the Zendesk Agent Workspace, the composer sits at the bottom of the ticket. Above the comment box there's a dropdown (or tab) that toggles between "Public reply" and "Internal note." Select the one you want before you type, and the composer's appearance updates to match — including the yellow background for notes (Zendesk: Composing messages in the Agent Workspace).

One behavior that surprises almost everyone the first time: the composer keeps a separate text buffer for each mode. If you draft something as an internal note and then switch to a public reply, your typed text does not carry over to the public reply (and vice versa). Zendesk does this on purpose so you can flip between an internal aside and a customer-facing reply without one overwriting the other (Zendesk: Composing messages in the Agent Workspace). The upside is you'll never accidentally dump your private note into a public reply by switching tabs. The downside is you can't "write it privately, then move it to public" by toggling — you'd have to copy it across.

Who can see what (the full picture)

It's worth being precise here, because "agents only" has a few wrinkles:

• Public comments are readable by the requester, everyone CC'd, and all agents with access to the ticket. The requester is emailed unless the relevant notification trigger is disabled (Zendesk: Adding comments to tickets).
• Internal notes are restricted to agents. End users — including end users on the CC line — never see them (Zendesk: Can customers see private notes?).
• Light agents and followers can read and create internal notes but cannot post public replies — useful for SMEs who need to weigh in without ever facing the customer.

A related gotcha: end-user replies sometimes land as internal notes. If someone who is not the requester or a CC replies to the ticket email, or if a recipient uses Reply instead of Reply all, Zendesk records their message as a private comment so it isn't accidentally broadcast (Zendesk: Why do end-user comments appear as internal notes?; Understanding when email replies become public or private). If you ever wonder why a customer's email shows up yellow, that's why.

@mentions, CCs, followers, and side conversations

These four collaboration tools interact with comment privacy in ways that trip people up.

@mentions. Typing @ followed by an agent's name inside a comment loops them in. Depending on your settings, the mentioned agent is added as a CC or a follower and gets the corresponding notifications (Zendesk: Using @mentions). For messaging conversations specifically, you can @mention a colleague in an internal note but not in a public reply — and the mentioned agent is added as a follower and pinged in the Agent Workspace (Zendesk: Collaborating on messaging conversations using @mentions). Practical rule: use @mentions inside internal notes to pull a teammate in quietly.

CCs vs. followers. CCs can include end users and agents, and they receive and can respond to updates; agent CC email addresses are visible to end users in the thread. Followers are internal-only and invisible to end users — they get update notifications and can make private comments (Zendesk: Understanding CCs and followers). Crucially, you cannot add a CC on an internal note (Zendesk: Using CCs and followers). If you need an internal collaborator who stays hidden from the customer, use a follower (or an @mention), not a CC.

Side conversations. When you need to pull in a vendor, another team, or a Slack channel without cluttering the main thread, use a side conversation. It runs in parallel to the ticket and doesn't disturb the customer-facing conversation. Note that adding someone as a CC/BCC on a side conversation does not add them as a CC on the ticket (Zendesk: Collaboration overview). Think of side conversations as the right tool for external collaboration, internal notes for quick in-thread team context, and followers/@mentions for looping in colleagues silently.

How to prevent accidental public replies

The nightmare scenario — a private aside sent to the customer — is preventable:

1. Check for the yellow. Make "glance at the composer color before submitting" a team habit.
2. Set a safer default. Admins can change the default comment privacy for the account (and adjust it per group), so the composer opens on internal note by default and agents must consciously switch to public (Zendesk: Changing the default privacy of ticket comments). Teams whose work is mostly internal triage often prefer this.
3. Use draft mode. Agent Workspace now supports a draft mode in the composer, so you can write a public reply and have it held as a draft rather than sent — no more composing in an internal note and copy-pasting to public just to be safe (Zendesk: Draft mode in composer).
4. Know you can recover. If something does go to the wrong audience, you can change a public comment to private after the fact (within Zendesk's conditions) to limit further exposure (Zendesk: Changing a ticket comment from public to private). It won't un-send the original email notification, but it stops the comment from showing publicly going forward.

Automating comment privacy with triggers and automations

Zendesk's business rules can both read and set comment privacy:

• Conditions. Use Comment | Is | Public (or Private) to branch on the privacy of the latest comment, and the Ticket: Privacy condition — Ticket has public comments — to tell whether a ticket is public or private overall (no public comments = private ticket) (Zendesk: Automation conditions and actions reference).
• Actions. A trigger can add a customer-facing comment via Autoreply or add an internal note for agents only — so your automations can post status updates publicly while logging diagnostics privately (Zendesk: Automatically adding comments and notes to tickets using triggers).
• A default to watch. When a comment is private, Zendesk suppresses the "Email user (requester and CCs)" action — so an internal note won't notify the customer even if a trigger would otherwise email them (Zendesk: Adjusting your business rules to handle private tickets). If you build private-ticket workflows, account for this so notifications fire where you expect.

For deeper automation patterns, see our guide to automating Zendesk with AI.

Best practices

• Public for the customer, private for the team. If a sentence is about the customer rather than to them, it's an internal note.
• Set the default to match your workflow. Internal-first defaults suit triage-heavy teams; public-first suits frontline reply teams.
• Prefer followers/@mentions over CCs for internal collaborators so they never appear to the customer.
• Use side conversations for external parties, not public replies or a long chain of internal notes.
• Write internal notes as if they could be read by the customer. Privacy controls fail occasionally; professional notes age better and survive subpoenas, audits, and exports.

Where an AI agent fits (the honest aside)

Because internal notes are agent-only, they're a natural home for AI assistance. An AI agent layer like Macha can draft a customer-ready public reply for an agent to review and send, and drop internal context — a summary of the conversation, the likely root cause, suggested next steps, relevant past tickets — as a private note, so the human always decides what actually goes to the customer. The privacy line stays exactly where Zendesk draws it; the AI just does the legwork on both sides of it. If you want to try that, Macha offers a 7-day free trial, no credit card required. More on the approach in AI agents for Zendesk: what they are and how to add them.

Frequently asked questions

Can customers see internal notes in Zendesk? No. Internal (private) notes are visible only to agents — never to the requester or to end users CC'd on the ticket (Zendesk).

How do I tell a public reply from an internal note at a glance? Internal notes have a yellow background in the composer and timeline. A standard background means you're in a public reply (Zendesk).

Why did my internal note text disappear when I switched to public reply? It didn't disappear — the composer keeps a separate text buffer for each mode, so text typed as an internal note isn't carried into the public reply (and vice versa) (Zendesk).

Can I make a public comment private after sending it? Yes, you can change a public comment to private after the fact, subject to Zendesk's conditions — though it won't recall the original email notification (Zendesk).

Why is a customer's email showing up as an internal note? If the sender isn't the requester or a CC, or replied with "Reply" instead of "Reply all," Zendesk logs the message as a private comment to avoid broadcasting it (Zendesk).

Can I add a CC to an internal note? No. You can't add a CC on an internal note. To loop in a colleague privately, use a follower or an @mention instead (Zendesk).

The bottom line

Internal notes and public replies are the same composer with two very different audiences: notes are agent-only and yellow, replies are customer-facing and emailed. Master the dropdown, watch for the yellow, set a default that matches how your team works, use followers and @mentions for silent collaboration and side conversations for external parties, and let triggers enforce privacy at scale. Get those habits right and you eliminate the most common — and most embarrassing — Zendesk mistake there is, while giving your team the shared context that resolves tickets faster.

If you'd like AI to draft replies and leave internal context for your agents without ever crossing the privacy line, see Macha on Zendesk.