Simplified Threading in Zendesk – Available ApS

In modern customer service, efficiency and clarity are crucial. Agents handle a constant flow of enquiries, and each interaction contains valuable information. As a ticket's history grows, however, it can quickly become an unmanageable list of events such as emails, internal notes, status changes, CC notifications and more. This can lead to errors, longer response times and a frustrating experience for both agents and customers. Simplified Threading in Zendesk changes the way ticket histories are visualised and used. This article goes through what Simplified Threading is, how the feature works, and how it can be used to create a more streamlined and user-friendly working environment.

What is Simplified Threading?

Simplified Threading is a visual feature in Zendesk Agent Workspace that redesigns the presentation of the ticket history. Instead of a traditional chronological list, where each action is shown as a separate entry, Simplified Threading groups all customer-facing comments together. Internal actions such as internal notes, status changes and field updates are shown separately and clearly distinguished from the actual conversation with the customer.

In a long email correspondence between a customer and several agents, the classic view will typically be interrupted by internal notes, assignment notifications and system messages about field changes. The result can be a fragmented thread, where you have to scroll back and forth to get an overview.

With Simplified Threading, all public comments (the customer's enquiry, the agent's reply, the customer's follow-up and so on) are gathered into one coherent and easy-to-read thread. Internal discussions and system actions are still available, but do not disrupt the reading of the primary customer dialogue. The customer dialogue is presented together, while internal activities are kept separate but still within reach.

Why is Simplified Threading a game-changer?

Implementing Simplified Threading is more than a visual change. It is an improvement that can affect support processes broadly. The main benefits are described below.

Reduced cognitive load

When an agent encounters a long and cluttered ticket history, it takes mental effort to filter out the noise and identify the flow of the conversation. That load can lead to fatigue, increase the risk of errors and delay response times.

Simplified Threading reduces the noise by presenting the public conversation as a coherent thread. This makes it easier to focus on understanding the customer's problem and formulating a relevant reply.

Improved readability and contextual understanding

When handing over a ticket or reviewing a case, quick contextual understanding is crucial. Simplified Threading can shorten this process significantly. Instead of reading many separate entries to understand the dialogue, the full conversation can be skimmed quickly. The clear separation between customer dialogue and internal actions makes it possible to first get an overview of what has been communicated to the customer, and then review the internal notes for background and considerations.

Increased efficiency and faster response times

When less time is spent navigating the history, time is freed up to solve the customer's problem. Less scrolling and quicker contextual understanding can contribute to a faster First Reply Time and a shorter handling time. Small efficiency gains per ticket can, over time, add up to significant improvements in productivity.

Better collaboration without disturbing the customer

Simplified Threading supports internal collaboration by making it possible to add internal notes, discuss solutions and consult colleagues without making the public conversation unmanageable. This can promote documentation and knowledge sharing, which can contribute to higher-quality solutions.

Improved customer experience (CX)

Customers do not see Simplified Threading directly, but they can experience the effect. When agents have a better overview and can collaborate more effectively, replies can become more accurate and relevant. It becomes easier to see what has previously been promised or communicated, which can reduce the risk of conflicting information. Faster and more accurate service is central to a good customer experience.

How Simplified Threading works in practice

To understand the value of Simplified Threading, it is helpful to know how activities in a ticket are divided.

The visual separation

When Simplified Threading is enabled, a clear visual separation is shown in the ticket history in Agent Workspace:

The customer's conversation thread: All public comments are grouped at the top and presented as a coherent conversation, as in an email client. A blue line or other visual indicator ties the comments together.
Internal and system actions: Below the conversation thread, other activities are shown in chronological order, including internal notes, field changes, assignments, CC notifications and more. These are marked with a timestamp and the sender.

Public comments are grouped, but not hidden. There is still an easily accessible option to view the full, detailed history when needed.

What gets grouped in the conversation thread?

Everything that the customer can see is grouped. This includes:

The customer's original enquiry: Regardless of channel (email, web form, chat converted to a ticket or another public channel).
Agents' public replies: Comments marked as Public and sent to the customer.
The customer's follow-up replies: Replies sent back on the existing email thread.
CC'd users' comments: If an external party is CC'd and replies "all", the comment is included in the public conversation thread.

These elements make up the overall customer dialogue, which is presented as a single unit.

What is shown separately?

Everything internal or system-generated is shown outside the conversation thread. This ensures that the direct communication with the customer is in focus in the grouped view. Separate elements include:

Internal notes: Visible to agents and administrators.
Status changes: E.g. from "Open" to "Pending" or "Solved".
Assignments: Change of agent or group.
Changes to custom fields: E.g. "Priority", "Type" or other fields.
System messages: Automatic messages from Zendesk, e.g. virus scanning of attachments.
Side conversations: Creation and replies are shown separately.
Timestamps and edits: Information about creation and editing.

The division makes it possible to switch between an overview of customer communication and a detailed insight into internal activities without losing the context.

Enabling and configuring Simplified Threading

Enabling Simplified Threading is a simple process for an administrator. The setting is account-wide and affects all agents who use Agent Workspace.

Step-by-step guide to enabling it

Log in as an administrator: Administrator rights are required.
Navigate to the Admin Center: Click the gear icon (⚙️) in the left sidebar and select Admin Center.
Find the Workspaces settings: Find the Workspaces section in the left-hand menu and select it.
Select Agent Workspace: Click Agent Workspace in the submenu.
Enable the feature: Find the Simplified Threading setting (typically a toggle) and switch it on.
Confirm the change: The change takes effect immediately for all agents. A restart or re-login is not necessary.

Once the feature is enabled, ticket histories are automatically shown with the new grouped structure in Agent Workspace.

Important considerations before enabling

Before enabling it across the organisation, the following can be considered:

Communication to agents: Inform them of the change, its purpose (reduced noise, better overview) and the new view. A short workshop or an email with screenshots can support adoption.
Training: A short training session can be relevant, including how the full history is expanded and how internal notes are used in the format.
No going back (right away): It can take time before the change is applied to all existing tickets. The setting is account-wide, so the old and new views cannot run in parallel for different agent groups.

Practical use cases: When does Simplified Threading shine?

Below are scenarios where Simplified Threading typically makes a clear difference.

Use case 1: The long, complex technical case

A customer reports a critical bug, and several agents as well as a developer become involved.

Without Simplified Threading:
- Customer: "We have a bug in the billing."
- Agent A (internal note): "Okay, I'm looking into it. Have seen something similar before. Maybe a database error?"
- System: Ticket assigned to Agent B.
- Agent B (internal note): "Agent A, can you send me the log files you looked at?"
- Agent A (public comment): "Dear customer, thank you for your enquiry. We are looking into the matter and will get back to you."
- Customer: "It's urgent, we have a financial close coming up."
- Agent B (internal note): "Developer C, can you look at this? Ticket #12345."
- Developer C (internal note): "It looks like an error in the API call. I'll make a fix in the next release."
- Agent B (public comment): "Dear customer, we have identified the problem. A fix is on the way..."
The history becomes fragmented and requires sorting to follow the dialogue.
With Simplified Threading:
- Conversation thread (shown first):
  - Customer: "We have a bug in the billing."
  - Agent A: "Dear customer, thank you for your enquiry. We are looking into the matter and will get back to you."
  - Customer: "It's urgent, we have a financial close coming up."
  - Agent B: "Dear customer, we have identified the problem. A fix is on the way..."
- Internal and system actions (shown below):
  - Agent A (internal note): "Okay, I'm looking into it. Have seen something similar before. Maybe a database error?"
  - System: Ticket assigned to Agent B.
  - Agent B (internal note): "Agent A, can you send me the log files you looked at?"
  - Agent B (internal note): "Developer C, can you look at this? Ticket #12345."
  - Developer C (internal note): "It looks like an error in the API call. I'll make a fix in the next release."
The public communication appears as a single unit, while the internal investigation is organised separately.

Use case 2: Onboarding a new agent

A new agent, Maria, takes over an existing ticket as part of her training.

Without Simplified Threading: It requires reading through many entries to understand the course of events, and important customer comments can be overlooked among the internal notes.
With Simplified Threading: The full conversation thread can be read quickly for an overview, after which the internal notes can be reviewed for background. The training can thus become quicker and more effective.

Use case 3: Managerial review and quality control

A support manager reviews a closed ticket to assess service quality.

Without Simplified Threading: Public replies have to be identified manually in a mixed history, which is time-consuming.
With Simplified Threading: Focus can be placed directly on the conversation thread to assess external communication, and the internal notes can then be reviewed to assess the process and compliance.

Best practices: Make the most of Simplified Threading

Enabling it is the first step. To get the greatest benefit, workflows and habits can be adapted as described below.

1. Write clear and self-contained public comments

When public comments are presented as a coherent thread, it becomes more important that each comment is well structured and can stand on its own. References to internal notes in public replies (e.g. "As I wrote in my internal note...") should be avoided, as the customer cannot see them, and the separation is clearer in the view. Each public comment should contain the necessary information for the customer.

2. Use internal notes strategically

Internal notes become a central tool for internal activities. They can be used for:

Documenting research: "I have checked the customer's account and see that they are on the 'Enterprise' plan."
Brainstorming: "Possible solutions: 1. Reset the password. 2. Check the firewall settings. 3. Escalate to 2nd level."
Communicating with colleagues: "@John, can you confirm that this feature is on our roadmap?"
Personal reminders: "Remember to follow up on this ticket tomorrow at 10am."

The ability to use internal notes without disrupting the public conversation is a key strength of the feature.

3. Train agents to expand and explore

Although the grouped view is the default, it is important that agents know how to access the full history. Zendesk typically offers a link such as "Show X comments" or similar. Agents should be trained to expand the thread when in doubt, to avoid overlooking critical details. The purpose is to prioritise information, not to hide it.

4. Combine with macros and side conversations

Simplified Threading works together with other Zendesk features:

Macros: Macros can be used to insert standardised internal notes, e.g. when escalating: "Escalated to the technical team. Expected response time: 4 hours."
Side conversations: When external expertise outside the customer dialogue is needed, side conversations can be used. The side conversation is shown as a separate entry in the internal part of the history, which keeps the conversation thread clean.

5. Establish clear guidelines for the use of CC

When external parties are CC'd on a ticket, their replies can create noise in the public conversation. Clear guidelines on when CC is relevant and how replies are handled may be necessary. A side conversation can be considered if a dialogue with a third party is not relevant to the customer.

Considerations and potential challenges

Although the benefits are many, challenges can arise that should be addressed.

Risk of overlooking details

A potential downside is that focus can become too one-sided on the grouped conversation thread, so that internal notes and system actions are not reviewed. Critical information can therefore be overlooked if the history is not expanded or reviewed.

Solution: Training and habit formation are key. It should be built into practice to review the entire ticket history, not just the visible conversation thread, before replying or taking action.

Getting used to a new workflow

For agents who have worked with the classic view for a long time, the transition may require some getting used to. The visual change can feel unfamiliar at first.

Solution: Communication and training before launch are crucial. The benefits should be made clear, and time should be given to get used to the layout, if possible, before a broad rollout.

Not relevant in all scenarios

For very simple tickets with one enquiry and one reply, the difference may be limited compared with the classic view. The effect is typically greatest for complex and long cases.

Solution: This is primarily an observation. A standardised view across tickets can outweigh the limited gain in the simplest cases, as consistency in the user experience is important.

Troubleshooting: Common questions and solutions

Below are typical questions and their solutions.

Question: Simplified Threading is enabled, but does not appear in tickets. Why?

Solution: Check that Agent Workspace is being used, as the feature does not apply to the classic Zendesk interface. Re-logging in may help, as the browser cache can delay the display of changes. If the problem persists, the setting in the Admin Center should be double-checked.

Question: An internal note was grouped together with the customer's comment. Is that an error?

Solution: This should not happen, as the feature distinguishes between public comments and internal notes. Check whether the note was created as Public by mistake. If the note is correctly marked as Internal and the problem persists, Zendesk Support should be contacted.

Question: How can the author of internal notes be seen when they are separated?

Solution: Each internal note and system action still shows the author's name and avatar as well as a precise timestamp. The information has not been removed, only organised differently.

Question: Can what gets grouped be customised?

Solution: No. The grouping logic is fixed: everything public is grouped, and everything internal or system is shown separately to ensure consistency and predictability.

Question: How are integrations and apps affected?

Solution: Most modern Zendesk apps are built for Agent Workspace and therefore typically work with Simplified Threading. Older apps that manipulate the display of the ticket history could potentially be affected. Critical apps should be tested after enabling to ensure they function as expected.

Conclusion: Create overview and efficiency with Simplified Threading

Simplified Threading is an improvement to the way ticket histories are used. By separating customer dialogue from internal and system-generated activities, it becomes easier to prioritise and organise information.

For agents, this can mean lower cognitive load, faster contextual understanding and a more focused working day. For the organisation, it can contribute to increased efficiency, higher quality in case handling and an improved customer experience. Implementation requires a deliberate decision as well as communication and training, but can result in a more streamlined and professional support function, where the customer dialogue stands out clearly and internal activities remain accessible without dominating the history.