Admin Pro Tip: Onboarding New Agents - Quickly and Effectively

Onboarding a new agent in Zendesk is one of the most critical administrative tasks. A good onboarding process is not merely an advantage; it is the foundation for high customer satisfaction, agent retention and a well-functioning support organisation. An inadequate process can lead to insecure agents, inconsistent responses, customer frustration and a steady stream of simple questions to more experienced colleagues.
Over time, the onboarding process can be refined through experience with both "learning under pressure" and longer, theoretical programmes. The conclusion is typically that a structured, practical and gradual approach gives the best results. The article describes experiences, learning points and concrete strategies that can make new agents productive and self-sufficient quickly.

The first 72 hours: A structured start

The first three days are crucial. The goal is not to turn the new agent into a Zendesk expert, but to build a solid foundation of confidence and basic understanding. Being overwhelmed is a significant risk factor. The first 72 hours can usefully be divided into three focused phases.

Day 1: The foundation - "What is this place?"

Day 1 is solely about navigation and terminology. Advanced features and complex workflows are kept out.

Goal for the day: The agent can log in, identify the most important parts of the agent interface and understand what a ticket is in its simplest form.

Agenda for day 1:

• The Zendesk universe (30 minutes): Start with the overview: What is Zendesk, and why is it used? Show a simple flow diagram of how a ticket arrives (via email, form, chat), is handled by an agent and is closed. This creates context.
• Tour of the agent interface (60 minutes): Systematically go through the primary elements:
  • Ticket Editor: What are Subject, Comment, Requester, Assignee, Group, Status, Type, Priority? Explain each field with simple examples (e.g. "This is the customer's name", "This is who is working on the case", "This is whether the case is open or closed").
  • The side panel: Briefly introduce what Apps are (e.g. Jira, Salesforce), but note that more will be covered later. The focus is to show where the information is found.
  • The top bar: What are Views, Macros, Guides, Explore? Explain that these are central tools that are introduced step by step.
• The first ticket (90 minutes): Create a "training ticket" and go through the process together:
  1. Read and understand the customer's enquiry.
  2. Add an internal note (Note) to document considerations.
  3. Write a public comment (Comment) to the customer.
  4. Set status to Pending (waiting for the customer) or Solved (if the case can be resolved immediately).
  5. Assign (Assign) the ticket to the agent themselves.

The day can be concluded with time in a sandbox environment with 5-10 simple, fictitious tickets. The goal is not perfect solutions, but confidence in navigation and basic actions.

Day 2: The toolbox - "How is the work done efficiently?"

Once the agent understands what a ticket is, tools that increase efficiency are introduced. The focus is to automate and standardise repetitive tasks.

Goal for the day: The agent understands and can use Views and Macros to handle a standard ticket flow.

Agenda for day 2:

• Views - Personal dashboard (60 minutes):
  • Explain the concept: A view is a saved search that shows the tickets to be worked on; a to-do list.
  • Introduce three critical views for beginners (elaborated in the next section): My Open Tickets, New Unassigned Tickets and Awaiting My Response.
  • Show how a view is updated via "Update", and what the columns mean.
• Macros - A shortcut to consistency (90 minutes):
  • Explain the purpose: Macros ensure uniform, correct responses and reduce repeated typing, so the focus can be on problem-solving.
  • Introduce 3-5 essential macros:
    1. A welcome macro.
    2. A macro for the most common question (e.g. "Password reset").
    3. A macro for escalation to 2nd level support.
    4. A macro for requesting more information.
  • Go through how a macro is used, and especially: how it is customised before sending. A macro is a template, not a finished solution.
• Practical exercise (90 minutes): Give a new batch of training tickets where views and macros must be used. The task could be: Take a ticket from "New", assign it to the agent themselves, find the relevant macro, customise it, and send the response.

Day 3: First hands-on work - "I can do it myself!"

Day 3 bridges training to operations. SLAs, internal notes and collaboration are introduced, and the agent handles the first real (but low-priority) tickets under close supervision.

Goal for the day: The agent can handle a simple, low-priority ticket from start to finish with minimal guidance.

Agenda for day 3:

• SLA and follow-up (45 minutes): Explain what a Service Level Agreement (SLA) is, and why it is important. Show how the SLA clock appears in views, and what the colours mean. Introduce Pending as the primary tool to "pause the clock" while awaiting a response from the customer.
• Communication and collaboration (45 minutes):
  • Internal notes vs. public comments: A simple rule can be applied: Anything that should not be visible to the customer is written as an internal note. Internal notes are used for questions to colleagues, documentation of research and important details.
  • CCs and Followers: Explain how other agents or external parties are involved in a case.
• First real tickets (the rest of the day):
  • Create a specific view for new agents, e.g. New Agent - Training Queue, with simple, low-risk tickets (e.g. invoice questions, general "how-to" questions).
  • The agent takes one ticket at a time. A senior agent is available alongside (or via screen share) for questions.
  • For each ticket, review the content before sending: "What is the plan? Which macro is used? Have internal notes been checked? Is the response clear and friendly?"
  • The first resolved ticket is marked as an important milestone that supports self-confidence.

The most important views for a beginner

A new agent does not need 50 different views. 3-5 views can cover the majority of the daily work. Too many views can create "analysis paralysis" and confusion. A sensible approach is to start simple and expand later.

The views below can be created and added directly to the agent's home page.

1. My Open Tickets

The most important view and the agent's personal to-do list. Contains all tickets that the agent is actively working on.

Purpose: To give a clear overview of what needs to be done now.

Configuration:

Status: Less than - Open
Assignee: Current user

Pro Tip: Often add columns such as Requester, Subject, Created, Updated and SLA. Sort by SLA (descending) so that tickets close to expiry are at the top. This supports a good habit from day one.

2. New Unassigned Tickets

The place where new, unhandled tickets land. This is where new work is found.

Purpose: To provide a place to pick up new cases and support understanding of a shared inbox.

Configuration:

Status: New
Group: [Name of the agent's group, e.g. Customer Service]
Assignee: - (None)

Pro Tip: In the beginning, filtering on a specific channel or type can reduce being overwhelmed, e.g. Via: Email and Type: Question. This ensures that the simplest enquiries are handled first.

3. Awaiting My Response

A central view for avoiding tickets "dying". When an agent has replied to the customer and set the ticket to Pending, it lands here. If the customer replies, the ticket is automatically moved back to My Open Tickets.

Purpose: To act as a reminder to follow up on cases where a response from the customer is awaited.

Configuration:

Status: Pending
Assignee: Current user

Pro Tip: A macro such as "Follow-up: No Response" can be used after a certain number of days (e.g. 3 days) to send a friendly reminder. This view is the place where tickets for that macro are typically found.

4. Solved today

This view is not for active work, but for motivation and quality assurance.

Purpose: To give a sense of progress and an easy place to find the day's work for any review.

Configuration:

Status: Solved
Assignee: Current user
Solved: - Today

Pro Tip: Watching the list grow during the day can be motivating. The view is also an obvious starting point for daily "ticket review" with a mentor or team leader.

Macros: The new agent's superpower

Without macros, a new agent can end up in a cycle where every response has to be formulated from scratch. Macros act as a "superpower" that enables consistent, fast and correct responses, even before all knowledge is fully embedded.

When building macros for onboarding, it can help to think in categories.

Category 1: Welcome and acknowledgement macros

These macros are typically the first ones a new agent learns. They set expectations and confirm that the enquiry has been received.

Example: "Acknowledgement: We have received your enquiry"

Subject: Re: {{ticket.title}}
Comment:

Hi {{ticket.requester.first_name}},

Thank you for your enquiry. We have received your message and one of our agents will look at it as quickly as possible.

We aim to respond within [number] hours.

Kind regards,
{{current_user.name}}
[Company name]

Why it is essential: It is professional, sets an expectation for response time and is easy to apply to new tickets.

Category 2: Common response macros (FAQ macros)

The backbone of efficiency. For questions that occur several times a week, there should be a macro.

Example: "FAQ: Password reset"

Subject: Re: {{ticket.title}}
Comment:

Hi {{ticket.requester.first_name}},

You can easily reset your password by following these steps:

1.  Go to our login page: [link to login page]
2.  Click on "Forgot password?".
3.  Enter the email address you used to create your account.
4.  You will receive an email with a link to create a new password.

If you experience problems, please reply to this email and feel free to attach a screenshot of any error messages.

Kind regards,
{{current_user.name}}

Why it is essential: It provides a complete and correct answer to the majority of password enquiries and teaches the correct procedure from the start.

Category 3: Escalation and handover macros

Escalation macros provide a structured and safe way to pass cases on when a new agent is stuck.

Example: "Escalation: To Technical Department"

Actions:
- Assignee: [Name of Technical Department/Group]
- Group: Technical Department
- Type: Incident
- Priority: High
- Add internal note: Hi team, this enquiry concerns a technical issue that I cannot resolve at 1st level. The customer has described the following: [Insert the customer's problem here]. I have already tried to [insert what you have tried]. Kind regards, {{current_user.name}}.
- Set status: Open

Why it is essential: It ensures that necessary information accompanies the ticket, that it is sent to the right recipients, and that priority is set correctly. This reduces uncertainty for new agents.

Category 4: Closing macros

Correctly closing a ticket is an important part of the customer experience.

Example: "Closing: Resolved - Awaiting confirmation"

Actions:
- Set status: Pending
- Comment:

Hi {{ticket.requester.first_name}},

We have now carried out [describe what you have done].

Please do let us know whether this resolves your problem. If we do not hear from you within [number] days, we will automatically close this case.

Kind regards,
{{current_user.name}}

Why it is essential: It confirms the action to the customer and proactively attempts to reduce the risk of reopening later.

Measure success: How to test onboarding

An onboarding process is not static. It should be measured and improved on an ongoing basis. The assumption that the process works because there are no complaints can lead to stagnation. A combination of quantitative data and qualitative feedback can be used to assess effectiveness.

Quantitative measurements

Track specific key figures for new agents (typically the first 30-90 days) and compare with the team average.

• First Contact Resolution (FCR): What proportion of tickets are resolved on the first attempt? Low FCR may indicate a lack of knowledge or inadequate tools (macros).
• Time to First Response: How quickly is a new ticket responded to? A high value may indicate uncertainty or too much research time.
• Ticket Reopen Rate: How often are resolved tickets reopened? A high rate is a clear red flag and may indicate inadequate or unclear solutions.
• CSAT/NPS Scores: The customers' assessment of the interaction with the new agent; a direct quality indicator.
• Macro usage: How often are macros used? Low usage may mean a lack of familiarity or low relevance. High usage is a positive sign.

A simple dashboard can be set up in Zendesk Explore that tracks these metrics for a "New Agent" segment, so the need for extra support can be quickly identified.

Qualitative measurements

Numbers do not cover the whole picture; the human factor is crucial.

• Weekly ticket review: A senior agent or team leader reviews 5-10 randomly selected tickets weekly. The focus is constructive feedback rather than fault-finding:
  • "The response was clear and friendly. Next time, the macro 'FAQ: Password reset' could be considered, as it contains a link that makes it easier for the customer."
  • "The question in the internal note was relevant. This is how that type of problem is typically investigated…"
• Shadowing: In the first few days, the new agent observes an experienced agent. After a week or two, this is reversed so that the experienced agent observes the new agent working on real tickets. This provides insight into thought processes and challenges.
• Structured feedback: After the first week, and again after the first month, a short, structured meeting is held with direct questions:
  • "What feels most overwhelming?"
  • "Which macro is missing?"
  • "Is there anything in the process that seems unnecessarily complicated?"
  • "How can better support be provided?"

The combination of these methods provides an overall picture of the onboarding programme's effect in practice.

Common onboarding mistakes and learning points

Classic mistakes in onboarding can be costly, but valuable sources of learning. Below are typical pitfalls and ways to avoid them.

Mistake 1: The "Firehose" method

The mistake: Everything is presented at once: tickets, macros, automations, triggers, views, apps, SLAs, reporting, Guides and so on. The result is often overload and helplessness.

Learning point: It is not realistic to absorb so much information at once. It can create stress and inhibit learning.

The solution: The 72-hour model has been developed as a countermeasure: One concept at a time and plenty of practical exercise between each topic.

Mistake 2: Ignoring the "why"

The mistake: The focus is only on "how" (click here, write this, select that dropdown), without explaining why processes and macros are designed as they are.

Learning point: Without context, knowledge becomes commands, and it becomes difficult to handle deviations from the standard.

The solution: Start with the rationale: "The macro is used to ensure GDPR compliance" or "The status is set to 'Pending' to pause the SLA clock, so that waiting time for the customer does not count negatively." When the rationale is understood, the procedure is retained better.

Mistake 3: Lack of structure and documentation

The mistake: Onboarding happens ad hoc. Different senior agents teach different (and sometimes conflicting) methods, and there is no central place to find information.

Learning point: Inconsistency creates confusion and bad habits. New agents spend unnecessary time searching for answers or get different answers from different people.

The solution: A simple onboarding site in Zendesk Guide can act as a reference point and contain:

• A weekly plan with links to relevant articles.
• Videos showing how specific tasks are performed.
• A "glossary" of Zendesk terminology.
• A list of essential macros with a description of usage.
• An FAQ for new agents.

This acts as a "single source of truth" throughout the onboarding programme.

Mistake 4: Forgetting the human factor

The mistake: The focus is solely on the system and not on the team. The new agent is introduced to Zendesk, but not to colleagues, culture or unofficial rules of the game.

Learning point: Technical skill is not sufficient if the agent does not feel part of the team. It can affect performance and increase the risk of an early departure.

The solution: Onboarding starts before Zendesk. A "buddy" scheme can ensure that an experienced agent (not necessarily a manager) is dedicated to answering "simple" questions, showing practical matters and introducing the new agent to the team. The new agent is involved in social activities from day one.

Red flags: Signs of an overwhelmed agent

Early warning signals should be identified quickly. An overwhelmed agent is not only less effective, but may be heading towards burnout or resignation. The following red flags are relevant to monitor:

• Tickets sit for a long time in My Open Tickets: If a simple ticket sits for several hours without an update, it can indicate uncertainty, forgetfulness or a lack of knowledge about the solution.
• Extreme use of internal notes for simple questions: Internal questions are relevant, but if every other note is a question that should be covered by basic training or a macro, the foundation is missing.
• High Ticket Reopen Rate: A clear quantitative red flag that indicates inadequate quality.
• Avoidance behaviour: Consistently choosing the easiest tickets from New Unassigned Tickets and leaving more complex cases, or avoiding new tickets by focusing only on existing ones.
• Repeated questions: Repeated questions about the same basic concept can indicate that the information was presented too quickly or unclearly.
• Stress and uncertainty in meetings: Lack of contribution, visible confusion during process discussions or direct expressions of being "behind".

When a red flag is observed, action can be taken quickly with, for example, an extra one-on-one session, a review of specific tickets or a temporary reduction in active tickets to rebuild confidence.

Green flags: Signs of an independent agent

It is just as important to identify and support positive signs. Green flags indicate that the onboarding process is working, and that the agent is developing into a stable resource.

• Proactivity in New Unassigned Tickets: The agent takes the initiative to pick up new cases and contributes to keeping the queue down.
• Suggestions for improvements: Statements such as "This question comes up often; should there be a macro?" show critical and proactive process understanding.
• Rising FCR and falling Reopen Rate: Key figures move in the right direction and approach the team average.
• Constructive use of internal notes: Internal notes are also used to document research, share solutions and provide information about trends in enquiries.
• Helping other new agents: When a relatively new agent helps an even newer agent, it indicates that knowledge and processes have been internalised.
• Positive CSAT comments: Customers mention the agent by name in positive feedback, e.g. "Thank you for the quick and friendly help from [Agent Name]!"

Recognising green flags is central, as it reinforces desired behaviour and supports continued development.

A successful onboarding process is dynamic and requires ongoing attention, adjustment and empathy. The investment can deliver great value in the form of confident, competent and effective agents who can not only use Zendesk, but also understand the rationale behind the workflows. This supports the team, the customers and the administrative function alike.