How to optimise your macros usage in Zendesk

Hi all! 👋

I am very happy to proceed with my series of Zendesk optimization posts. You can find previous ones about general Zendesk setup, ultimate optimization checklist, ideal KPI system, and excellent ticket categorization. This very post is based on those posts' ideas – so feel free to read them for having better context.

Today I would like to share some best practices for organizing and using macros in Zendesk. After many Zendesk optimizations projects, I found that macros underutilization is the main productivity killer in Zendesk. Actually, I see the same issues with macros usage across very different Zendesk accounts all the time. But in fact, with pretty minimal efforts, you can fix these issues and improve your Zendesk productivity significantly – and other KPIs as a result since the speed and quality of the customer service is a key competitive advantage today.

Top 10 issues with macros in Zendesk

The following are issues with macros organization and usage in Zendesk and how they impact the agents' productivity or CSAT of your customers:

1. Macros not used at all. All is clear – agents spend much time for simple typing or copy-pasting from somewhere outside of Zendesk. Just start using macros.

2. Macros not actively used. Macros are up to date but (not all) agents use (not all) macros. Some agents are underperforming as a result.

3. Limited macros taxonomy. Your macros cover only some limited set of topics while other cases are not covered. You should organize the macros creation workflow to manage this.

4. Limited macros standardization. Sometimes managers allow agents to create personal macros and this might end with over-diversified macros taxonomy without any common brand communication style.

5. Outdated content in macros. Some of your macros have old content that is being edited all the time when applied or sent as is (with negative consequences as a result).

6. Missing actions in macros. Sometimes macros are used only to add the comment to the ticket. The rest of the actions are being made manually each time (like fields values, setting status, etc).

7. Macros not grouped. Without grouping macros, you have a long list of macros with hard navigation and a difficult search process.

8. Macros titles are too short (unclear). Without enough details, agents might need to preview or apply and undo macros changes manually to see in detail what the macro is about.

9. Creating individual language-specific macros. When you create many macros for the same reply in different languages you end up with too many macros. If available on your plan, use Dynamic content instead to have fewer macros and manage them easier.

10. Adding signatures to macros texts. Avoid doing this and instead, use the standard signature feature in agent profiles or Brands settings to manage them easily from one place.

How to organise macros in Zendesk

Below I would like to highlight the main macros organizations principles that also address the issues outlined above.

• Organise the macros creation process. Depending on the team size, macros creation and regular updates might be a duty of one or many persons. The main thing here is to establish an ongoing process and organize workflows when agents can request creating/updating macros right inside related tickets. They can refer to the replies-candidates and use special macros (!) to leave a structured internal note with relevant details. The simplified workflow looks like follows: (1) Agent requests new macro in the ticket > (2) Manager notified via trigger about the request > (3) Manager creates a macro and leaves a note about this > (4) Trigger notifies all agents about new macro with a source ticket link to learn the context.

• Add all standard and custom actions. Macros serve great by setting many system and custom fields values, tags, etc in one shot. It makes sense to replicate all relevant actions even if some of them are set by business rules in Zendesk. Why? Because you never know when you could have a case when you need to do this manually and having all actions in the macro saves your time in any future case. The same applies to the plain text version of the comment: add it by default to avoid unnecessary edits for channels that do not support Rich content formatting. This is how the actions list might look like with all actions added.

• Group macros into categories. Once you have a good number of macros it gets difficult to navigate and search them from a long list. But macros can be easily organized into multi-level groups like dropdown fields values. By adding double colons (::) you are separating different levels (this might look like this: Delivery::Track status::What happens if the order is lost during shipping). I usually suggest using the same categorization taxonomy that is used for ticket fields and syncing them completely to have a full synergy between ticket properties and macros. Check my post about excellent ticket categorization for a reference.

• Formulate answer-style titles. Macros are about answers you provide to questions. That's why the titles of the macros should clearly indicate what the macro is replying to the particular request (but stay compact at the same time!) and not what is being asked (because you can use very different replies to the same question). Very often you have similar macros varying by some minor part – be sure to point this in the title. I usually suggest using "+" to separate the main different parts of the macro and () for minor specifics. The macro title Delivery::Track status::Order shipped + Tracking link (International) tells us that we confirm order delivery status (shipped) and sending tracking link for an international order. Other versions might be for domestic or country-specific shipping.

• Track & review macros usage trends. Last but not least, any activity requires measuring its success. To keep macros usage high and measure their performance you need to have a tool. This point is explained in the last section of the post.

How to measure macros usage in Zendesk

The most intriguing question is: What is a good level of macros usage for my team? I know companies that have many hundreds of macros and use them very actively – like in above 95% of their replies (technically in all of their replied tickets). And I saw the brands with thousands of tickets monthly not using a single macro. With proper setup, you can create many macros and still use them very efficiently. The golden rule here is that the more macros you use the fewer support agents you need (= have fewer spendings).

First of all, it makes more sense to measure macros usage against replies and not tickets since macros usually are used in individual replies (public pr private comments). Also, the ticket might have more than one reply, thus the One-Touch Rate of the standard CS team might be between 60%-80%. The more replies on average does your typical ticket have, the more important is to measure macros usage against the replies.

From my perspective there are next levels of macros usage:

• Very high – > 80% of replies

• High – 60-80% of replies

• Medium – 40-60% of replies

• Low – 20-40% of replies

• Very low – < 20% of replies

To measure your macros usage trends and patterns you can use different tools depending on your Zendesk plan and budget.

• Using stats on Macros page. If you have Zendesk Professional plan or above you can check usage stats for up to the last 30 days. Go to Admin > Manage > Macros and select a period in the sorting menu. With a regular monthly checkup, you can save your stats into a sheet and have these general usage numbers tracked. Clearly, that you don't have any additional context (except groups using macros) to analyze usage.

• Using Explore reports. There is a great Zendesk recipe explaining how to measure macros usage with tags. This approach is limited by counting all non-unique usage events per ticket level (which means you will not see all events of the same macro usage if it is used a few times in a ticket). But you can use any other Explore user or ticket attributes (like brands, forms, fields, etc) to dig into your macros usage trends. And this is great!

• Using Zendesk apps. There are just a few apps on Zendesk Marketplace that do allow you to report on macros usage in detail: Miuros Insights and Macros Reporting by Pythia. These apps provide you a deep look into macros usage and performance across many attributes and their relation to agents' productivity and customer satisfaction. Highly recommended for reporting obsessed ZD owners!

I hope this post was interesting reading for you. Let me know in the comments what other macros optimizations techniques do you use and like.

Stay safe and productive! And happy support! ✌️

Andrei Kamarouski
Zendesk Expert, Pythia Co-Founder

Placeholder blocking reply without field filled out

Hey everyone! Is there a way to create a custom placeholder that won’t let the agents send the reply unless it’s filled out by them manually?

- Automations Specialist

Lance Conzett, Customer Experience Lead at Found: The way we've done this in the past is with conditional fields and macros. The macro with the placeholder enables a checkbox that makes the placeholder field appear, which is required to solve the ticket.

Automations Specialist: ah so it’s only possible with the custom field, right? Not the actual text in the body of the reply.

Lance Conzett: Right. Your placeholder would be something like {{ticket.ticket_field_1234}}, with 1234 being the custom field ID you want to pull the value from. One pro-tip on that, you’ll want to surround that placeholder in the macro with {% raw %} and {% endraw %}. Otherwise it’ll come out as blank since the placeholder looks for the value when inserting it into the comment box after you pick a macro.

Automations Specialist: I see, I’ll definitely use this in somewhere. I was looking for a way to include a mandatory fill out part of text for agents, as there is nowhere to pull it from. Basically it’s the end of the subscription, and it’s not in zendesk so agents will need to fill it out themselves. It’s different (obviously) for every user and agents often forget to add it to the template which results in sending out very awkward messages containing {pls add end of subscription here}

Josh Keller, Sr. TechOps Manager, Customer Ops @ Udemy: We had a similar problem. I added a process in a custom ticket sidebar app that listens for ticket submission, checks the description text for various strings, and prevents submission if it contains them. Looking through the Zendesk Apps Marketplace, I found this one which can do this (prevent submission if { or } are in the description), but I tested it out and found that you also must use the submission preview feature for this to work. You could set the delay to 1 second so that it’s quick, but it’d be a tad odd. Setting it to 0 or 0.1 seconds doesn’t work. Or maybe the preview feature is nice and an added bonus.

This article was created with the support of Pythia AI, the provider of affordable productivity apps for Zendesk leading youк business to the true CX Success.

Migrating help center docs from Intercom into Zendesk

Can anyone share the best method (in your opinion) for migrating help center docs from Intercom into Zendesk. I’ve seen a ton of add ons, consulting groups, and walkthroughs online and I am struggling picking the best option for our needs

- Content Manager

Josh Keller, Sr. TechOps Manager, Customer Ops @ Udemy: I’d pull from one API and send to the other.

Dave Dyson, Sr. Customer Service Evangelist at Zendesk: Here are some guidelines on doing that via the API: https://support.zendesk.com/hc/en-us/articles/4408828053146-Migrating-existing-content-to-your-help-center

Fwiw, there's a (paid, 3rd-party) Help Center Import app that can import from CSV (but you'd have to get your Intercom help center into the CSV first): https://www.zendesk.com/apps/support/285803/help-center-import/?_ga=2.258445896.375416329.1638335349-1139015716.1638335349

There are also third-party services that can migrate your help center content, e.g. https://help-desk-migration.com/intercom-to-zendesk-migration/

import2 might be able to do it as well, I'm not positive though: https://www.import2.com/

Content Manager: Thanks for the resources Dave! I can’t decide if I want to pay a team to do, have my eng team do it w the api, or try my hand using an add-on/csv as described. I’m sure there are pros/cons for each avenue and just gotta figure out which one we need…

Simple team average for replies-to-resolution

Any quick hacks for finding out a simple team average for replies-to-resolution? Started with this, not super interested in breaking it down by agent, so have just removed the row aspect https://support.zendesk.com/hc/en-us/articles/4408846763802-Explore-recipe-Average-replies-per-ticket-for-each-agent-per-day I suspect it's also rounding when I'd prefer it didn't

- Explore Learner

Community Member A: This should help with the decimal places: https://support.zendesk.com/hc/en-us/articles/4408838914842-Changing-the-format-of-results

About the Editor

Andrei Kamarouski is a Zendesk Expert and Pythia AI CEO. He loves to help people in the Support Driven Community and across the Web with any kind of Zendesk challenges and projects. Find him here LinkedIn.