Scalability is normal. Not very high. At that time, there were around 1100 end users using this solution. 

The scalability was good. We had a lot of tickets and never had an issue.

We had 20 to 25 people using the solution. We had departments like customer support and operations on it. 

Three people are using Zendesk Support in my organization.

My experience with Salesforce Essentials has been positive in terms of scalability and I’ve witnessed organizations scale rapidly.

It is a scalable solution. But for me, there is maybe some Slack thing, really for me. Slack becomes more than the same time. But all those decks, once you open Zendesk to attend to the customer’s request on the phone and all, and hence I would rate the scalability of Zendesk Support a nine out of ten.

Around 400 users who are using Zendesk Support in our organization. With Zendesk Support, you can also create the same Macro on Zendesk. The time you use to type in the calculator will take you more time. So it is better just to create a Macro instead of you wasting like five minutes typing.

Once you have already created the Macro, you can just send whatever response you want to decline if you are sure you know what the feedback really is. So I can resolve a customer request immediately.

This solution is pretty easy to scale. You can put a lot of data in there—it doesn't seem to affect it at all. However, in terms of Multibrand, you have to make the updates manually. There is no feature to push to update to all the health centers. 

We are a six-people team, and we all work with Zendesk Guide. As far as usage, we have over 1,000 customers who are accessing Zendesk Guide, and we have more than 12 health centers that we have deployed. 

We have approximately 150 customers using this solution.

I rate the scalability of Zendesk Support a ten out of ten.

There are about six people involved with Zendesk Guide in my organization. We have plans to increase our usage. 

The scalability capability seems pretty straightforward. I can't speak to how the support team is using it, to be honest. I can't speak to if they actually have attempted to scale it in any meaningful way just yet.

Our support and customer success teams are the main users of the product. We have about 15 people in total on the solution at any given time.

We didn't really talk about scalability previously. That wasn't even something that was considered as there were so many things that ServiceNow does that Zendesk doesn't from an IT infrastructure perspective. We're looking at those features for the future in terms of our roadmap, security, asset management, and so forth.

Currently, we have about 24 people on the solution. They are admins or developers, for the most part.

At this point, we don't intend to increase usage.

The scalability isn't an issue for us right now.

In terms of scalability, that wasn't even something that we were considering, just that there were so many things that ServiceNow does that Zendesk doesn't from an IT infrastructure perspective. And we were looking at those features for future-state from the roadmap, security, asset management, and so forth.

We only have about 24 people interfacing with Zendesk. They are admin or developers. Then there's a few BA who are mostly either engineer support for the help desk IT or they  belong to one of those internal groups that we support, Salesforce developers, SharePoint developers, or Tableau developers and architects. These are the people who need to resolve the tickets when there's an issue.

It's been able to scale for our needs.

If you wanted to scale from ten agents to 1,000 agents, then it's tricky to do it by yourself.

That's the moment when you should go for an implementation partner or something. I tried to do it by myself. I tried scaling from three or five people to 30 people. And the biggest problem is when you have a structure, and you change the structure. I found that when I was doing extracts, I had a lot of data on the previous structure and I didn't have data on the current structure and I had to do a lot of manipulation in Excel. Basically, you are losing a lot of data in analytics at the moment you decide to change the structure of your team.

In my previous company, 30 to 40 people used this product. 

I only receive a certain amount of tickets throughout my working day.

We haven't needed to scale as our helpdesk is quite small.

We never suffered any stability or any difficulty increasing our operation. Some parts of the month we have more flows of transactions and more cost. We can run with no problem, we do not have any delay operating. 

Currently, we are upgrading and going to be having more users inside our company. We are hiring more people and we are very satisfied.

We have 16 users currently and by the end of the months, we will have 23.

It is easily scalable for departments, however, if different departments need to use it, then each may need their own customizations. If there are many departments with specific customizations, scaling the central management of Zendesk becomes more difficult.

There have been no issues scaling it for our needs.

To date we have had no issues with scalability.

No issues encountered, and many different teams are utilizing Zendesk here at the company.

We have had no problems scaling it for our needs.

I'm not too sure what you mean in terms of scalability, but I did encounter issues with trying to back up the data (ie. tickets sent, frequent ticket senders, etc.) to a different platform (which was necessary at the organization I was with at the time).

We have had no issues with scaling it for our customers needs.

It has been able to scale well for our needs.

We had no issues with scaling it for our needs.

It's been able to scale for our needs.

We gradually include new users to Zendesk without any issues.

It's scalable/

No problems scaling.

We have had no issues with scaling it for our needs.

No issues encountered.

We have had no issues scaling it for our needs.

There have been no issues scaling it for our needs.

No issues encountered.

At the very beginning, we had some scalability issues.

We've had no issues scaling it for our needs.

We have had no issues with scaling it for our needs.

I have not seen any issues.

None at all.

There have been no issues scaling it.

We had no issues scaling it for our needs.

At the very beginning, we had some scalability issues.

We have had service clients, creating great support and managing relations, tracking jobs via ticketing system as well. In other words, it's scaled for the things we need it to do.

There have been no issues scaling it for our needs.

As our organization grew, it couldn't scale to our needs. That's why we switched to Salesforce.

No issues encountered.

I never dealt with Zendesk customer service, but I have heard great things about it.