Internal Notes vs. Public Replies in Zendesk: How to Use Both

If you're still getting your bearings on how tickets work in general, our Zendesk ticketing system explainer is the place to start; this post zooms in on the comment box specifically. Everything below is verified against Zendesk's own documentation, but Zendesk revises its UI periodically, so confirm labels in your own account.

The core distinction: who sees what

The two comment types differ on exactly one axis — audience — and everything else follows from it.

• Public reply — the customer sees it. Specifically, it goes to the requester (the person the ticket is for) and to anyone CC'd on the ticket, and it shows up in their email and in the help center view of the request. This is how you actually talk to the customer.
• Internal note — agents see it; the customer never does. An internal note is "only visible to agents, not to the ticket requester or any other end-users who might be copied on the ticket," per Zendesk's documentation. No notification email reaches the customer, and it doesn't appear in their help center view. This is how your team talks about the ticket.

So a public reply is customer-facing correspondence, and an internal note is a private backchannel stapled to the same ticket — context, questions for a teammate, a heads-up about a difficult account — all kept in one place instead of scattered across Slack or email. Because the requester and CCs are the audience for public replies, it's worth knowing exactly who falls into each bucket; our guide to requesters, CCs, and followers breaks down who gets notified when you hit submit.

The yellow background: your most important visual cue

Zendesk gives internal notes a deliberately unmissable signal: a yellow (highlighted) background. In the Agent Workspace, when you select Internal note, the entire composer shifts to a yellow tint, and once submitted the note stays yellow in the conversation log. Public replies stay on a plain white background.

Train your eye on this one cue and most mistakes disappear. White = the customer is reading this. Yellow = only my team is reading this. Before you ever click submit, the colour of the composer tells you, at a glance, who is about to receive what you just typed.

How to switch between public reply and internal note

Switching is a single click, and it's the same in every ticket.

1. Open a ticket in the Agent Workspace.
2. Above the comment box, you'll see two tabs: Public reply and Internal note.
3. Click Public reply to write to the customer, or Internal note to write to your team. The composer changes colour to confirm the mode (white vs. yellow).
4. Type your comment, then submit the ticket.

You can mix both on a single update if you need to — for example, leave an internal note for a colleague and send the customer a public reply in the same session — by switching tabs between comments before you submit. The tab you're on at the moment you click submit is the type that comment is saved as.

The #1 risk — and the famous Zendesk mistake

Here is the mistake every support team makes at least once: an agent means to leave a private aside — "this customer is being unreasonable, let's just refund them and move on" — but the composer is on Public reply, and they submit it. That note doesn't go to a teammate. It's emailed directly to the customer.

It happens because the two modes look similar at a glance, the composer defaults to public, and a busy agent's muscle memory is to type and hit submit. The stakes are real: internal notes are where agents put candid assessments, pricing leeway, account warnings, and half-formed theories — none of which should ever reach a customer.

Can you undo it? Only partly, and the nuance matters. Agents and admins can convert a public comment to an internal note after the fact, but it's irreversible (you can't switch it back to public, and it doesn't work on AI agent tickets) — and crucially, converting it does not un-send the email. The customer was notified the instant you submitted; hiding it in the log afterward only cleans up the record. The fix lives before you click submit, not after: check the colour every time (yellow for a private remark, white for the customer), read the tab, and — if your team collaborates more than it replies — default the composer to internal note (next section) so the safe mode is the one you fall into by accident.

Make the composer default to internal note

By default, Zendesk opens the composer on Public reply. For many teams — especially ones doing a lot of internal triage and collaboration — flipping the default to internal note is the safer choice, because the worst-case accident becomes "I left a note no customer saw" rather than "I emailed a customer something private."

This is an account-wide setting, so an admin makes the change once for everyone:

1. Go to Admin Center → Objects and rules → Tickets → Settings.
2. Find the Comment options for agents section.
3. Deselect Set composer to public channel by default.
4. Deselect Allow agent comments via email to be public by default as well, so replies coming in by email follow the same private-first rule.

A couple of things to know: this applies to the whole account, not per-agent — there's no individual override. There's also one sensible exception baked in: a ticket that has only internal notes and no public comments yet will always open on internal note regardless of the setting, and live channels (chat, messaging, social) aren't affected by it.

One more path worth knowing, because it catches teams off guard: comments can also become public from inbound email. When an agent replies to a ticket notification from their own inbox, a plain Reply is treated as private by default, while a Reply all (which copies the requester or other recipients) can post as a public comment — and Zendesk's mail API honors a #public true / #public false command in the body to force the privacy of an emailed comment either way. If your agents work tickets from email as much as from the Agent Workspace, set the "Allow agent comments via email to be public by default" option deliberately and tell them which reply button does what.

The trade-off is real, so decide deliberately. If your agents spend most of their time replying to customers, a private-by-default composer just adds a click to every reply and can cause the opposite error — forgetting to switch to public and leaving the customer waiting. Set the default to match where your team actually spends its time.

@mentions: loop in a colleague from inside a note

Internal notes aren't just a private scratchpad — they're how you pull a specific teammate into a ticket. Inside an internal note, type @ followed by the start of a colleague's name (e.g. @Jan) and pick them from the list. That person gets a notification in the top-right of their Zendesk interface, is notified in the Agent Workspace, and is automatically added as a follower so they keep getting updates on the ticket.

One constraint to know: @mentions only work in internal notes, not public replies — you can't accidentally @mention a customer into a reply. It's the cleanest way to ask "can you take a look?" without leaving the ticket, keeping the context, the customer's message, and your question in one thread instead of a Slack ping that loses the link back.

Who can add and see internal notes

Internal notes are visible to your internal team — agents and light agents — and never to end users. That second group is worth understanding, because light agents exist specifically to collaborate through internal notes.

A light agent is a free (on most plans) internal collaborator — think an engineer, a product manager, or a finance approver who needs to weigh in on tickets but isn't a frontline support rep. The defining rule: light agents can add internal notes, but they cannot send public replies. They read tickets and contribute privately to the team conversation, full stop. That's a feature, not a limitation — it lets you bring subject-matter experts into a ticket with zero risk of one of them accidentally messaging the customer.

One nuance to plan around: light agents (along with contributors and Chat-only agents) can't use the @mentions feature themselves and can't add followers. So a light agent can leave an internal note, but to pull one in, a full agent should @mention them or add them as a follower / CC — see the followers and CCs guide for the mechanics.

How notes interact with triggers and notifications

The public/private split also governs notifications and automation:

• Public reply → the requester and any CCs get an email notification (assuming your notification triggers are on).
• Internal note → no customer notification, ever. The only people pinged are agents following the ticket or @mentioned in the note.
• Triggers can read comment privacy. A condition like "Comment is Public" sends a customer-facing email only on an actual public reply, while internal notes update the ticket silently. You can also build triggers that add an internal note automatically (e.g. stamp context on a VIP ticket) without touching the customer thread.

The practical upshot: if a customer says they never got your reply, check first whether the comment was public or internal — a note on the yellow background never sends.

Best practices and common mistakes

A handful of habits keep this clean — and their opposites are the errors that bite teams repeatedly:

• Make the colour check a reflex. Yellow for team-only, white for the customer, confirmed before every submit. The headline mistake — submitting a private remark as a public reply — disappears once this is muscle memory.
• Keep candid talk in notes, not replies. Frustrations, pricing flexibility, and account warnings belong on the yellow background. But watch the mirror-image error too: a great answer left on the yellow background never reaches the customer, so a "why no reply?" is often just an internal note that should have been public.
• Use @mentions instead of side channels — and only in notes. Looping a teammate in via @mention keeps the question and answer attached to the ticket; it won't work in a public reply by design.
• Match the default to your workflow. Heavy on internal collaboration? Default to internal note. Heavy on customer replies? Leave it public.
• Remember CCs are part of "public," and a privacy change is one-way. A public reply reaches everyone CC'd, not just the requester — and converting public→private is one-way, so you can't switch a comment back to public once it's hidden.

Where AI fits in

If accidental public replies are a recurring problem on your team, it's usually a symptom of agents moving fast under volume — and that's the part AI can take pressure off. An AI agent layer like Macha sits on top of your existing Zendesk (it's not a help desk and not a Zendesk replacement). It reads the ticket and drafts a context-aware reply from your knowledge base and past tickets, so the agent is reviewing and approving a draft rather than typing every word from a cold start.

The honest framing: a human still owns the public/private decision — Macha proposes the reply, your agent reads it and chooses to send it publicly, keep it as an internal note, or escalate. It can also leave its own internal notes (a triage summary, suggested next steps) so the human picks up the ticket with full context already on the yellow background, while the customer-facing send stays a deliberate human action. On cost, Macha bills per AI action — any automated step it takes, like drafting a reply or summarizing a ticket — not per closed ticket, since most of that work isn't a "resolution," it's groundwork along the way. You can try it free — 7-day free trial, no credit card required.

Frequently asked questions

What's the difference between an internal note and a public reply in Zendesk? A public reply is sent to the customer — the requester and anyone CC'd on the ticket see it in their email and the help center. An internal note is visible only to agents and light agents; the customer is never notified and never sees it. Internal notes appear on a yellow background in the Agent Workspace so you can tell the two apart at a glance.

Can the customer see internal notes in Zendesk? No. Internal notes are "only visible to agents, not to the ticket requester or any other end-users who might be copied on the ticket," per Zendesk. They don't trigger a customer notification and don't appear in the customer's help center view of the ticket.

How do I switch between a public reply and an internal note? In the ticket composer, click the Public reply or Internal note tab above the comment box. The composer turns yellow on internal note and stays white on public reply. The mode you're on when you submit is the type the comment is saved as.

I accidentally sent an internal note as a public reply — can I undo it? Agents and admins can convert a public comment to an internal note after the fact, which hides it from the customer in the ticket and help center. But it's irreversible (you can't switch it back to public), it doesn't work on AI agent tickets, and — most importantly — the customer was already emailed the moment you submitted, so converting it afterward doesn't recall that email. Prevention before submit is the only real fix.

How do I make Zendesk default to internal note instead of public reply? An admin goes to Admin Center → Objects and rules → Tickets → Settings → Comment options for agents and deselects Set composer to public channel by default (and, ideally, Allow agent comments via email to be public by default). It's an account-wide change, not per-agent.

Can light agents add internal notes in Zendesk? Yes — internal notes are exactly what light agents are for. Light agents can read tickets and add internal notes but cannot send public replies, which makes them a safe way to bring engineers, PMs, or approvers into a ticket. Note that light agents can't use the @mentions feature themselves, so a full agent should @mention or add them to loop them in.

The bottom line

Two comment types, one decision: public reply reaches the customer (and CCs); internal note stays between agents and light agents, marked by a yellow background. Switch between them with the tabs above the composer, lean on the colour cue to never leak a private remark, use @mentions to pull teammates into notes, and — if your team collaborates more than it replies — flip the account default to internal note so the safe mode is the default one. The whole discipline comes down to a one-second habit: check the colour before you submit. For the bigger picture of how the agent's workspace fits together, see our Agent Workspace guide.

Internal-note and public-reply behavior verified against Zendesk's official documentation, June 2026. Zendesk updates its product periodically — confirm labels in your own account before relying on them.