What's the Difference Between CCs, Followers and Requesters in Zendesk?

In Zendesk, a CC is copied on the public conversation and can be a customer or an agent, while a follower is an agent or admin who watches the ticket privately and also receives internal notes. The requester is the person the ticket is for, the submitter is whoever created it, and the assignee is the agent responsible for solving it. A ticket can carry up to 48 email CCs, and an agent added as a CC has their email address shown to every end user on the thread, which is why colleagues belong in the follower field. Everything below was checked against Zendesk's CC and follower documentation on September 24, 2026.

Who is who on a Zendesk ticket?

Keep the third column in mind: a CC is on the customer-facing conversation; a follower watches from behind the glass. That single difference causes most Zendesk CC mistakes.

What is the difference between the requester, submitter and assignee?

These three define the core of every ticket. They're set when a ticket is created and rarely change, but the distinction trips up new admins. (For how tickets are created and flow in the first place, see our guide to the Zendesk ticketing system.)

• Requester: the person the ticket is for. Almost always the customer with the problem. Replies go to them, and the ticket belongs to them for reporting and SLA purposes. Every ticket has exactly one requester at a time, though you can change it.
• Submitter: whoever actually created the ticket. Usually the submitter is the requester, because a customer emails in. They diverge when an agent creates a ticket on behalf of a customer, or a phone agent logs a call: the agent is the submitter and the customer is the requester. That split matters for reporting, since "submitted by agents" versus "by end users" shows how much of your volume is proactive versus inbound.
• Assignee: the agent responsible for resolving it. One agent (and optionally a group) owns the ticket, and the work is measured against them. Reassignment moves accountability. The customer never sees an "assignee" label; they see replies from your brand or the agent's name, depending on your settings.

The most common search here is requester vs. assignee, and the answer is short: the requester is the customer the ticket is for, and the assignee is the agent who has to fix it. They sit on opposite sides of the conversation.

What does a CC do on a Zendesk ticket?

A CC works the way CC works in email: the person is copied on the public ticket conversation. Per Zendesk's docs, CCs can be end users or agents, they get email notifications when the ticket is updated, and they can reply on the public thread. A ticket can have up to 48 email CCs, which is plenty for normal use but worth knowing if you mirror large email threads into Zendesk.

CCs are visible. Zendesk's documentation says agents added as CCs have their email addresses visible to all end users in the thread, and end users see other CCs in the ticket header, just like a normal email chain. So a CC is the right tool when you want someone on the customer-facing conversation: a second customer contact, a teammate on the requester's side, or occasionally an agent whose involvement the customer is allowed to see.

Common uses for CCs:

• Adding a second stakeholder on the customer's side (the requester's manager, say) so they get updates.
• Looping in a colleague who needs to reply publicly to the customer.
• Mirroring an existing email thread where several people were already on the To or CC line.

What does a follower do on a Zendesk ticket?

A follower is the private counterpart to a CC. Followers are internal users only, agents and administrators, and they let your team watch and collaborate on a ticket without the customer knowing.

Per Zendesk, a follower's name and email address don't appear in the email notifications sent to other people on the ticket, and they stay hidden from CC'd end users and other followers. Followers get notified about updates, and they receive both public comments and private (internal) comments, so they see the full internal picture.

Be precise about one thing, because many write-ups get it wrong: a follower is a full agent, and Zendesk's docs say followers can make both private and public comments. They are not restricted to internal notes. Following exists for silent monitoring, though, so in practice followers participate through internal notes and @mentions. A public reply from a follower lands on the customer-facing thread and surfaces them in the conversation, which defeats the reason you made them a follower rather than a CC.

To pull another agent into the internal discussion, @mention them in an internal note (type @ and their name). That notifies them without exposing anyone to the customer.

Common uses for followers:

• A team lead or manager watching an escalated ticket without stepping into the customer thread.
• A subject-matter expert who needs the internal discussion and adds private notes.
• Cross-team collaboration, such as an engineer following a bug ticket, where the customer shouldn't see internal staff.

Should you add a colleague as a CC or a follower?

Add them as a follower. Here are the two side by side:

The practical rule: to bring another agent onto a ticket, add them as a follower, not a CC. A CC'd colleague has their email exposed to the customer, which invites the customer to contact them directly off-channel. Followers keep your internal team structure private, which is almost always what you want when the extra person is staff.

How do you turn on CCs and followers in Zendesk?

The "CCs and followers" experience replaced Zendesk's older email-only CC behavior, and an admin controls it. Accounts created before May 2019 may still need to migrate to it. If you don't see a Followers field on your tickets, it hasn't been turned on.

An admin goes to Admin Center > Objects and rules > Tickets > Settings and expands CCs and followers on tickets. The key settings, using Zendesk's labels:

• Allow followers: turns on followers and adds the Followers field to the ticket interface.
• Allow CCs: lets agents and end users add CCs and adds the CC line to tickets.
• CCs and followers blocklist: blocks specific email addresses or whole domains from becoming a CC or follower (only available when Allow CCs is on).
• Allow light agents to be added to tickets: lets requesters, agents and existing CCs add light agents and contributors as CCs or followers.
• Allow end users to add CCs to requests: lets signed-in customers CC others from email replies and the help center.
• Automatically make a CCed agent a follower: when an agent is successfully added as a CC through email or the Support interface, Zendesk also adds them as a follower, so they receive internal notes. They stay a CC, so their email is still visible to end users. The setting doesn't apply when the agent is CC'd from a help center form or through the API.

One gotcha: if Allow end users to add CCs to requests is on but Anybody can submit tickets is off, a non-registered user a customer tries to CC won't be copied and won't get notifications. (For where these settings sit relative to the fields and forms customers fill in, see ticket fields vs. forms.)

How does each person on a ticket get notified?

Notifications are where the public/private split shows up in practice:

• Requester: gets the standard public email notification for every public agent reply.
• CCs: receive the public ticket email when the ticket is updated, and can reply by email or in the interface. Agent CCs appear in the email header that everyone, including end users, can see.
• Followers: receive notifications for both public and private comments, and those notifications don't reveal them to anyone else on the ticket.

So one ticket update fans out differently: the customer and CCs see a clean public thread, while followers also see the internal commentary.

Can light agents be CCs or followers?

Yes, if an admin turns on Allow light agents to be added to tickets. Light agents are a limited role that can view tickets and add internal notes but not reply publicly, so they pair naturally with following. Two quirks: light agents can't add or remove themselves as a CC, which another agent has to do, and light agents can't add CCs to tickets at all. Role restrictions like these can also stop a light agent becoming a CC in the first place, so following is the cleaner pattern for them.

What are the common CC and follower mistakes?

• CC'ing an agent who should have been a follower. This exposes the agent's email to the customer. Add them as a follower instead. The auto-follower setting doesn't fix this, because the agent stays on the CC line.
• Assuming a CC can see internal notes. CCs only see the public conversation. If someone needs private notes, make them a follower.
• Forgetting that CCs can reply publicly. Anyone you CC can post on the customer-facing thread. Don't CC a customer contact you didn't mean to give a voice.
• CC'ing a customer who shouldn't see prior context. The new CC sees the existing public conversation. If earlier replies held details meant only for the original requester, you've now shared them.
• Wondering where Followers went. If the field is missing, it's the Allow followers setting, not a bug.

Can an AI agent keep CCs and followers updated?

Once you know who's on a ticket, the next job is keeping them informed without manual babysitting. Macha is an AI agent layer that runs on top of the help desk you already use (Zendesk, Freshdesk, Gorgias, Front, HubSpot or Intercom); it isn't a help desk itself. It can handle the busywork around stakeholders: summarizing an escalated thread as an internal note for a following manager, drafting an update for CC'd contacts, or routing a ticket to the right group so the right people end up watching it. Macha bills per ticket rather than per resolution: one conversation, charged once however many summaries, drafts and routing steps it takes, from $299 a month for 750 tickets. A per-resolution vendor earns more when its own definition of "resolved" is loose; a per-ticket bill tracks the volume you actually handle. It's only as good as the knowledge and rules you give it, so it supports your team's judgment rather than replacing it. You can try it on a free trial ($50 of usage, no credit card required).

Frequently asked questions

What's the difference between a CC and a follower in Zendesk? A CC is on the public conversation and can be an end user or an agent; CC'd agents' email addresses are visible to the customer, and CCs can reply publicly. A follower is an agent or admin only, is hidden from the customer, sees both public and private comments, and watches silently. Use CCs for customer-side or public participants and followers for internal staff.

What's the difference between the requester and the assignee? The requester is the customer the ticket is for. The assignee is the agent responsible for resolving it. They sit on opposite sides of the conversation.

What's the difference between the requester and the submitter? The requester is who the ticket is for; the submitter is who created it. They're usually the same person, but differ when an agent opens a ticket on a customer's behalf: the agent is the submitter and the customer is the requester.

How do I add a CC to a Zendesk ticket? If your admin has enabled Allow CCs, open the ticket and add the person on the CC line in the conversation header, or CC them from an email reply. A CC is public, so to add a colleague privately, add them as a follower instead.

How do I turn on followers in Zendesk? An admin opens Admin Center > Objects and rules > Tickets > Settings > CCs and followers on tickets and switches on Allow followers. That adds the Followers field to your tickets.

Can a CC see internal/private notes? No. CCs only see the public conversation. Followers see both public and private comments, so if someone needs internal notes, make them a follower, not a CC.

Does "Automatically make a CCed agent a follower" hide the agent's email? No. The agent is added as a follower as well as staying a CC, so they start receiving internal notes but their email address is still visible to end users on the thread. To keep a colleague's email private, add them only as a follower.

Feature behavior checked against Zendesk's help documentation on September 24, 2026 (the CC settings article was last edited September 4, 2026). Zendesk updates its interface periodically, so confirm exact menu labels in your own Admin Center.