CCs, Followers & Side Conversations: Your Guide to Effective Collaboration in Zendesk

Introduction: from isolated support to collective expertise

In a busy working day, where customers expect quick, precise and personal answers, effective collaboration is a necessity. A single support agent cannot possess all the knowledge required to resolve every enquiry. The question is therefore how to involve the right people without the ticket losing direction, and without exposing the customer to internal noise, technical jargon or strategic considerations. The answer lies in three of Zendesk's central collaboration tools: CCs, Followers and Side Conversations.
The features support internal and external communication by making it possible to involve relevant expertise, keep stakeholders informed and coordinate complex solutions, while ownership and a coherent customer experience are retained. Enquiries can thus be handled as collaborative processes with clear structure. This guide reviews how the tools are used to deliver consistent service and support sharing and learning.

CCs (Carbon Copy) – the bridge to external partners

A CC in Zendesk corresponds to "copy to" in email and is the primary, formal method for involving external parties who are not users in Zendesk but who have a legitimate and documented interest in following a ticket.

What is a CC, and how does it work?

When an external email address is added as a CC, the recipient gains the ability to:

• Receive a copy of all updates: The CC recipient automatically receives an email with every public comment and update on the ticket, which ensures transparency.
• Follow the conversation: The recipient can see the public conversation history and thereby the context, in the same way as the customer, which reduces the risk of misunderstandings.
• See the ticket status: Via email notifications, the recipient can follow whether the ticket is open, pending or solved, without system access.
• Reply (with limitations): The CC recipient can reply to email notifications. The reply is added as a public comment on the ticket, just like the customer's reply. This is significant, as the reply is visible to all other CCs and to the customer.

Important: A CC recipient cannot see internal notes or Side Conversations. The CC recipient only sees what the customer sees and therefore only participates in the public dialogue.

Strategic use: when should CCs be used?

CCs are used with a clear purpose to avoid noise, confusion and unintended data sharing:

• At the customer's explicit request: If the customer wishes to involve a manager, a colleague from another department or an external consultant.
• Project collaboration: When working closely with an external partner or supplier on a task related to the customer's ticket, e.g. a web developer or cloud provider.
• Compliance and legal requirements: In cases where a third party, e.g. an auditor or lawyer, needs to be kept informed of the progress of the ticket on an ongoing basis.

Best practices for effective use of CCs

• Always obtain consent: Before an external party is added, ensure that the customer is informed and has given consent. A usable phrasing is: "Hi [Customer name], would it be okay if [External party's name] is added as a CC on this ticket so we can help resolve [the problem]?"
• Be selective: Only necessary people are added. Too many CCs can create "notification fatigue" and uncertainty about who is expected to respond.
• Use a clear signature: When communicating with a CC present, explicit and clear phrasing can reduce misunderstandings.

Example in practice: project collaboration

A customer experiences problems with an integration between a system and a website developed by an external agency. The agency's technical contact is added as a CC so that the agency can see the customer's information and contribute via replies. Internal discussions about error logs or strategy are handled in a Side Conversation that the agency cannot see. The overall solution is finally presented in the public thread for both customer and agency.

Followers – the internal nerve centre

Where CCs connect the ticket with external parties, Followers are used to establish an internal network around a ticket. A Follower is always an internal Zendesk user who is invited into the ticket's internal collaboration.

Who is a Follower, and what access does it provide?

When a colleague is added as a Follower, they gain insight and the ability to contribute by being able to:

• Follow the ticket closely: Followers receive notifications in Zendesk and via email on updates, both public comments and internal notes.
• See all content: Followers can see the entire ticket, including internal comments and Side Conversations.
• Participate actively: A Follower can add internal notes, comment in Side Conversations, edit ticket fields and, if necessary, take over the ticket as "Assignee".
• Contribute expertise without taking over ownership: Specialists can be involved without changing the assigned agent, so that ownership and the customer's experience of a fixed point of contact are retained.

Types of Followers: from specialists to stakeholders

Followers are used strategically across the organisation, typically in the following roles:

• The specialist: A technical expert, product owner or integration specialist with deep knowledge.
• The mentor/team lead: An experienced colleague or manager who follows along to ensure quality, guide a new agent or monitor a critical ticket.
• The stakeholder: A colleague from sales, customer success or marketing with a business interest in the outcome, e.g. for key accounts.

Best practices for harnessing the potential of Followers

• Be specific in the invitation: When adding a Follower, use an internal note to state the purpose and need, e.g.: "Hi [Name], [Name] is being added as a Follower, as there is expertise in [topic]. The customer has a problem with [description]. A review of the internal note below is requested."
• Remove Followers when they are no longer needed: When the ticket is resolved, or the expertise is no longer relevant, Followers are removed to keep notifications relevant and the system tidy.
• Use as a learning tool: New agents can follow experienced colleagues on complex tickets to learn processes and solutions.

Example in practice: skills development across teams

A new agent receives an enquiry about an advanced software feature that the agent does not know in depth. An experienced colleague, "Mette", is added as a Follower. In an internal note it is written: "Mette, there is uncertainty about the best solution. Can you review the draft reply before it is sent?" Mette can see the entire ticket, comment and guide discreetly. The customer receives a qualified answer, and the agent gains learning.

Side Conversations – the digital meeting room

Side Conversations can be compared to moving an internal discussion out of the customer's view in order to return with a clear answer. In Zendesk, a Side Conversation is a separate, 100% internal thread, attached to a main ticket, which is used for internal debate, problem-solving and coordination.

Why Side Conversations are indispensable

• The customer sees nothing: The content is invisible to the customer and all external CCs, which protects against internal confusion, technical jargon, failed hypotheses and strategic considerations.
• Retains ownership: The original agent remains the owner and primary point of contact, but can involve help without handing over responsibility.
• Centralises communication: Discussions are kept attached to the ticket rather than being moved to Slack, Teams or separate email threads. This retains context and gathers communication in one place.

Concrete use cases: from escalation to product development

Side Conversations are used in several scenarios:

1. Internal coordination and problem-solving

• Scenario: The customer asks a complex technical question about an integration.
• Action: A Side Conversation is started with the integration specialist, where error logs can be shared, questions clarified and hypotheses tested, until a correct answer can be formulated and sent to the customer as a whole in the public thread.

2. Escalation discussions

• Scenario: The customer is very dissatisfied, and the situation risks escalating.
• Action: A support manager, technical manager and assigned agent can, in a Side Conversation, discuss compensation, process cleanup or other redress. This protects the customer from becoming part of an internal negotiation and ensures a uniform and well-considered response.

3. Expert consultation

• Scenario: A ticket requires input from the legal department or compliance team.
• Action: The relevant expert is invited to a Side Conversation to provide a precise and approved answer that can be passed on to the customer without revealing internal considerations.

4. Ideas and bug reports for the product team

• Scenario: Several customers report the same usability error, or a customer suggests a new feature.
• Action: A Side Conversation is started with the product owner, where relevant tickets are linked, and the scope or potential is discussed. This creates a direct line from customer feedback to product development.

Best practices for clean and focused Side Conversations

• Use a descriptive subject: The Side Conversation is named clearly, e.g. "Question about invoicing" or "Input for the legal department".
• Invite the right people: Only necessary participants are invited to resolve the specific task.
• Mark as resolved: When a conclusion has been reached, the Side Conversation is marked as "resolved" to signal completion and maintain an overview.

The big picture: CCs vs. Followers – a direct comparison

To avoid mistakes and ensure the correct choice of tool, it is central to understand the differences:

Overall strategy: building a culture of collaboration

Tools alone are not sufficient; the effect is achieved through strategic use in daily workflows. The following principles support collaboration becoming a strength:

1. The principle of deliberate communication

The audience is always assessed. Before adding a CC or Follower, clarify: "Who needs this information, and why?" This reduces noise and ensures targeted communication.

2. The principle of clarity in ownership

Collaboration must not blur ownership. A ticket without a clear owner risks being delayed. The structure is:

• Assignee (responsible): One person owns the ticket from start to finish and is the customer's primary point of contact.
• Group (team): The team has overall responsibility and functions as backup.
• Followers (informed): People who contribute knowledge and attention without ownership.

3. The principle of continuous cleanup

Inactive Followers or outdated CCs create a cluttered workspace and unnecessary notifications. As a ticket approaches resolution, the list of Followers and CCs is reviewed, and irrelevant participants are removed.

4. The principle of shared learning and training

The differences and strategic use of the tools must be understood within the team. Examples from practice can be used in team meetings, and questions are encouraged when in doubt. A strong collaboration culture requires shared understanding and ongoing training.

Solving challenges: troubleshooting in everyday work

Even with clear guidelines, challenges can arise. The handling of common situations is described below:

Conclusion: mastering collaboration as a competitive advantage

CCs, Followers and Side Conversations are central elements of a professional, efficient and customer-centred support culture. When used correctly and strategically, tickets can be handled as collaborative processes where relevant expertise is involved, and answers are delivered quickly, precisely and consistently, even for complex enquiries.

Mastering the tools requires ongoing awareness, training and continuous improvement of processes. When the tools are integrated into daily operations, and teams are trained in best practices, the ability to solve complex problems and deliver a stable customer experience is strengthened.