Zendesk Suite

What do you like best about the product?

Zendesk is very strong when it comes to organizing support operations, building triggers, managing views, and handling different support channels in one place. It gives us a lot of flexibility to route tickets, separate agent work from automation, and adapt workflows as our operation changes. It is especially useful when you need to manage email, chat, WhatsApp, and bot-assisted support in a structured way.

What do you dislike about the product?

The main downside is that some configurations are much more complex than they should be, especially in reporting and analytics. Metrics can be difficult to set up correctly when bots, automations, and human agents all interact in the same ticket. Explore is powerful, but it is not always intuitive, and small changes in formulas, channel naming, or field setup can break a report. Some admin tasks also feel too manual and time-consuming for teams that need to move fast. More API management options, mostly for AI management will help a lot

What problems is the product solving and how is that benefiting you?

Zendesk helps us centralize customer support across email, chat, WhatsApp, and automated bot flows, which makes it much easier to manage volume and keep the team organized. It solves a big operational problem for us by letting us route conversations correctly, separate what the bot can handle from what agents should handle, and build views and triggers around real support workflows. The benefit is better visibility, faster response handling, and more control over how customer conversations are managed and measured.

What do you like best about the product?

I love how it keeps every conversation from email to chat in one neat timeline so the support teams never lose context.

What do you dislike about the product?

I dislike how complex its pricing and setup can get, as features you actually need often require expensive tier upgrades or tedious configuration

What problems is the product solving and how is that benefiting you?

It stops customer messages from slipping through the cracks by pooling everything into one shared workspace which saves our team tons of time and frustration.

What do you like best about the product?

Some of the benefits of Zendesk for Customer Service include a user-friendly ticket management process and various support channels that allow the user to interact with customers through just one portal. Due to the automated system, which ensures ease of monitoring the reports, and the self-service feature, which increases customer satisfaction, the process becomes more convenient.

What do you dislike about the product?

nothing to add this time from my side everything seems fine

What problems is the product solving and how is that benefiting you?

Zendesk for Customer Support tackles issues such as handling large amounts of queries, tracking customer problems, and ensuring consistent communication through different channels. The software helps me by increasing response time efficiency and creating better customer experiences.

What do you like best about the product?

What I like best about Zendesk is how it brings everything together in one place. It makes it easy to track conversations, manage tickets efficiently, and keep responses consistent, which helps my teams stay organised and deliver a better customer experience.

What do you dislike about the product?

Nothing, once you know how to set it up and get it right for your teams its great

What problems is the product solving and how is that benefiting you?

All customer communication coming through 1 channel

What do you like best about the product?

I have been using Zendesk for around 6 years and I really like the user interface since everything is easy and quick to use. It is also very customisable, over the years we have easily tuned it to support our business. Any times I need to perform any sort of administration, it is fairly easy and intuitive. If I need product support, Zendesk are very helpful, responsive and descriptive.

What do you dislike about the product?

Without plugins, it can be difficult to choose the from email addresses which support tickets are sent to customers. Most business just have one so it is not a big deal.

What problems is the product solving and how is that benefiting you?

Zendesk for Customer Service allows us to offer help desk services for our customers and has a large amount of features to make it easy and quick. Zendesk also supports taking and making phone calls which effectively replaces a lot of systems and keeps all data in a unified, rich view.

What do you like best about the product?

Zendesk streamlines our customer communication for billable/non-billable projects and provides visibility across my team. I like that any team member can jump in on a project if needed to support a teammate, and all correspondence and internal notes are visible.

What do you dislike about the product?

It would be helpful if we could have it sync with our Salesforce to track billable/non-billable time, but I understand that's a very niche and nuanced use case!

What problems is the product solving and how is that benefiting you?

It helps my team work more efficiently and have visibility for collaboration and/or coverage.

What do you like best about the product?

Overall I've had a pretty good experience with Zendesk but there are definitely some quirks you need to know about if you're doing anything beyond basic ticket management. The automation is powerful once you get the hang of it - triggers, automations, and macros let you build out pretty complex routing logic and workflows. The API is solid and well-documented which has been a lifesaver when I need to pull custom reports or do bulk operations that the UI doesn't support well.
The integration ecosystem is good too. We connect with Jira, Slack, Office 365, and a bunch of other tools and it mostly just works. For managing a multi-team support operation with different queues and routing needs, it handles the complexity well once you get everything configured right.
That said, there are some frustrating gaps. Omnichannel routing can override your trigger-based group assignments in ways that aren't obvious, so you end up having to build defensive conditions everywhere to catch edge cases. Tag-based logic doesn't work the way you'd expect either - if one trigger adds a tag, other triggers firing in that same pass can't see it yet, so you have to work around that with update_type conditions and other tricks. The search API caps at 1,000 results which means chunking large date ranges for reporting, and macro restrictions only let you include groups not exclude them, so hiding irrelevant macros from certain teams is unnecessarily painful.
HTML email templates are also kind of a pain because any whitespace between tags renders as line breaks, so you have to minify everything to a single line which makes them impossible to read and maintain. And custom fields aren't always populated at ticket creation time, so triggers using Create conditions can randomly fail depending on when the field gets set.
It's a solid platform if you have someone technical managing it who can learn all the undocumented behaviors and quirks. Just don't expect it to be plug-and-play for complex workflows. You'll spend time testing and building workarounds, but once you know what to watch out for it does the job well.

What do you dislike about the product?

The biggest frustration is how many undocumented behaviors you have to learn the hard way. Omnichannel routing can override trigger-based group assignments in the same update event, but there's no warning about this anywhere - you just discover it when tickets aren't routing where you expect and have to dig through audit logs to figure out what happened. Same thing with tag timing - if one trigger adds a tag, other triggers firing in that same pass can't see it yet, so guard tag logic that should work just doesn't. You end up building workarounds for things that seem like they should work based on how the UI presents them.
The search API 1,000-result limit is a pain for any kind of large-scale reporting. If you want to pull ticket data for a high-volume group or date range, you have to chunk it into smaller searches and stitch everything back together. It adds a lot of complexity to what should be straightforward data pulls.
Macro visibility restrictions are unnecessarily limiting too. You can only include groups in macro visibility, not exclude them, so when we wanted to hide non-CES macros from our CES groups we had to go through and manually add every other group to hundreds of macros. There's no reason exclusion logic shouldn't be an option.
HTML email templates are also weirdly fragile. Any whitespace between HTML tags renders as line breaks in the actual email, so you have to minify everything to a single unreadable line before you can use it. Makes templates nearly impossible to maintain or update without breaking something.
The documentation gaps are probably the underlying issue with all of this. A lot of the advanced functionality just isn't well explained, so you're left testing and troubleshooting to figure out how things actually work versus how you'd assume they work. It's fine once you know the quirks, but the learning curve is steeper than it needs to be.

What problems is the product solving and how is that benefiting you?

The biggest thing Zendesk solves for us is routing and organizing tickets across multiple specialized teams. We have four main SME groups handling different parts of our product (association management, financials, homeowner portal, integrations) plus a client enablement team, and Zendesk lets us automatically route incoming tickets to the right group based on the issue type, product area, and client status. Without that automation we'd be manually triaging every ticket which would be a nightmare at our volume.

What do you like best about the product?

After using Zendesk for some time, I'd say it's one of the more user-friendly support platforms out there. The interface is clean and well-organized, making it easy to get up and running without a steep learning curve. Whether you're managing tickets, setting up automation, or creating macros, most tasks feel intuitive from the start.
The ticketing system in particular stands out — it's straightforward to navigate, and the ability to quickly triage, assign, and track issues keeps the team aligned without a lot of friction. New team members were able to get comfortable with the platform fairly quickly, which is a big plus.

What do you dislike about the product?

A few areas could still be improved. Reporting configuration is not very intuitive, as some of the more advanced configuration settings can feel buried. It can be difficult to find the data you need and update the report to incorporate filters across different objects.

What problems is the product solving and how is that benefiting you?

Zendesk has streamlined how our customer support team manages incoming requests from ChurnZero users. We can respond quickly, reduce resolution times, and ensure no customer concern falls through the cracks. This has directly helped us drive retention and reduce churn, which is at the heart of everything we do.

What do you like best about the product?

Omnichannel CRM capabilities are a must when dealing with customers. Having all interactions with a customer in one place—whether it’s voice, live chat, WhatsApp, or any other channel—is fantastic.

What do you dislike about the product?

The cost is high and some features and reporting are not available on lower packages meaning you are held hostage for the higher packages. Having a CRM in which you limit the ability to see what agents are doing is not functional and is prohibitive in its nature and as such I cannot recommend Zendesk

What problems is the product solving and how is that benefiting you?

The transparency of contact is making it easier for us to support customers and identify issues that have affected their service. It also helps us spot patterns where the same criteria matches, so we can try to pre-empt any future contact from that customer or from others with similar issues.

What do you like best about the product?

What I rely on most is having everything land in one place. Emails, chat, social messages, and phone calls all become tickets in the same queue, so I’m not bouncing between five different inboxes trying to piece together what a customer already told someone else. The full conversation history is right there on the ticket.

Macros have probably saved me the most time day to day. For the questions we get again and again, I can drop in a canned response and tweak it as needed. That keeps replies consistent across the team and means I’m not retyping the same thing twenty times.

Routing and triggers are another big upside. Tickets get assigned and tagged automatically based on the rules we set up, so the right person gets the right issue without anyone manually sorting everything. Setting up SLAs and getting alerts when something’s about to breach has also helped us stop letting tickets slip through the cracks.

A few other things are worth calling out. The reporting actually tells you something useful; response times, ticket volume, and where the backlogs are building. The knowledge base/help center is handy too, because you can deflect a chunk of the repetitive stuff by pointing customers to articles, and you can build it out of answers you’re already writing. It scales well as well; whether you’ve got a couple of agents or a whole department, it doesn’t really change how you work.

Onboarding new agents has been smoother than I expected. The interface is intuitive enough that people pick it up quickly without a ton of training.

It connects with just about everything we use: Slack, Salesforce, Shopify, and Jira. The marketplace has hundreds of apps, so setup is usually just a few clicks, and the API is solid when we need something custom. The Slack integration is especially handy for responding to tickets without leaving the channel.

What do you dislike about the product?

The biggest downside is the cost. It gets expensive quickly: the per-agent pricing adds up as the team grows, and a lot of features you’d expect to be standard are locked behind higher tiers. It can feel like you’re being nickel-and-dimed, where solving one problem means upgrading to the next plan.

Setup and configuration can also be a lot to take on. Getting triggers, automations, and routing rules properly dialed in takes real time and some trial and error, and it isn’t always intuitive when something doesn’t fire the way you expected. For a small team without someone dedicated to admin work, it can start to feel like overkill.

Performance can be another issue. When you have a lot of tickets or several apps running, the interface can get sluggish, and there are stretches where loading tickets takes longer than it should.

Reporting is solid at a basic level, but it gets frustrating when you need something more custom. Building the specific report you have in mind often means wrestling with the tools, or bumping up to a tier that includes better analytics.

A few smaller annoyances: support from Zendesk itself can be slow, which is ironic for a customer service tool. Some marketplace integrations are third-party and inconsistent in quality. And because there are so many features and settings, there’s a real learning curve—new admins in particular can get lost in the configuration.

What problems is the product solving and how is that benefiting you?

The main one is that our support used to be scattered everywhere emails, chat, social, phone calls all living in different places. Things slipped through the cracks constantly because no one had a full picture of what a customer had already asked or who was handling it. Pulling everything into one queue fixed that. Now there's a single history on every ticket, so nothing gets dropped and customers aren't repeating themselves.

It's also solved a workload problem. We were drowning in repetitive questions; the same handful of issues over and over. Between macros, automated routing, and the help center deflecting the simple stuff, the team handles a lot more volume without us having to keep adding headcount. Agents spend their time on the issues that actually need a person instead of retyping the same answer twenty times.

Accountability was another big one. Before, it was hard to know if tickets were being answered on time or just sitting there. SLAs and alerts mean things don't quietly slip past their deadline, and the reporting finally gives us visibility into response times, ticket volume, and where the backlogs are building; so we can actually staff and prioritize based on real numbers instead of guessing.

And it's let us scale without reinventing our process every time the team grows. Whether it's a couple of agents or the whole department, the workflow stays basically the same.