Setting up Freshdesk was straightforward, and the tool is flexible. We initially opted for a basic license with limited reporting but considered upgrading. However, the higher subscription cost made us stick with our current level. While the tool is easy to deploy, upgrading to the next subscription level could provide more flexibility and additional features.

The solution is moderate to deploy. It's not complex, however, it isn't easy. It's average. 

The initial setup is straightforward. I would rate the setup an eight out of ten. We deployed it on the cloud and on SaaS software. The deployment process took almost one day.

During the deployment, we had to create our company ID, categories and users, and assign auto resigning and CAN messages. We also included FAQs which are another essential feature.

The initial setup of Freshdesk is not straightforward because there is a lot of preparation. However, this is something that would take time in any solution because you need to build your own look and feel.

I rate the initial setup of Freshdesk a five out of ten.

When you get it, it's quite easy get up to speed. In Europe, you have to deal with strict GDPR-rules, and only when you take the highest price model, you will get a server in Germany. Apart from that, it's quite easy to get up and running.

It took me a bit longer than two weeks to set everything up, because most of the things we wanted to have, we prepared in advance. I would say, to really get your bearing and to really know what you are doing, it takes about three to four weeks. Even then, I've been working with it for nearly three years now and I still learn. I'm still learning more every day.

There is not really any maintenance. It's very stable and only requires maintenance when you have to change something due to any request or requirements from your own company. No technical maintenance is needed.

The initial setup is straightforward. Implementing Freshdesk is super easy, and I did it in two days. You don't have to break your head with the configurations because it's very simple. In two days, you can start using it. The production version can be set up in a week, and the whole organization can start using it.

Once you run a test, you'll understand what features are available and what are not. You will also better understand what you can develop. In contrast, if you want to install ServiceNow, you will need a consulting company to do that, and they charge thousands of dollars. With this one, you don't need them or your in-house developers. You can just go ahead and create it in about a week and deploy it to production.

It's a one-time activity, and once you've done it, that's it. You don't have to do any maintenance.

It was very easy to set up. 

Freshdesk was set up by our tech team. We needed the tech team to integrate it with our platform since we could not do it ourselves, but I would say that the setup was user-friendly and that the solution does not require much maintenance.

Since the solution's initial setup was straightforward, I rate it an eight out of ten. It can be considered complex only when the workflow is complex. Freshdesk's deployment is done on the cloud.

The solution's initial setup phase takes around three to four days, while the configuration process may take some time, maybe around three to four weeks.

I'm not responsible for the setup. That said, it's my understanding that we did have a couple of issues when it comes to workflow. For example, certain tickets should come to a certain department, and we have issues with that. 

The initial setup is not complex. The user manual and initial demo given by the sales team of Freshdesk is good. Our non-technical team members were able to understand how it works within one to three weeks.

The initial setup took around two to three weeks. What took the most time was writing the rules to manage the ticketing system. 

They had a VP set it up, at which point I was hired to come in and fix it. They just didn't know what the consequences were of, for example, letting every single manager build the enterprise workflow that applied to everybody. So, it was constantly breaking. It just needed going in and just saying, "Hey, you don't need to go do that anymore. We can simplify this." That had to do with the wrong use case.

It is a customer support tool. If you try to do enterprise support or logistics in it, there could be issues. All of my use cases have been B2B, and I've had it work really well. It did work really well at a smaller company with a smaller team where our account managers used it. That worked really well, but recently, I have been just a little bit removed from it. I'm now working on a deployment of it. So, we'll see how that goes in a couple of weeks or months.

I didn't do it. It was someone from my team. He did it in three or four days in the midst of everything else he was doing. It was simple. You just add in our users. He was able to import the names of everybody from the active directory, so we got all the employees there.

We had to sit down and have a meeting to decide the lists, categories, and groupings, and then he just did it. A couple of days later, I started to use it in the pilot form, and we cut over to it fast.

The initial setup was relatively easy.

As a cloud-based solution, the initial setup is very easy and very straightforward. It's not overly complex or difficult. 

The initial setup was fairly simple. We had about a month of trial and then it was fairly simple when we launched. We had an onboarding person that gave us overall training for it, and then they have the Freshdesk Academy, where they have training videos on their platform that I could use. It would just direct my team to see it as well, so it's fairly simple. It didn't take too long.

There were five people involved and it took about a month and a half.

It's very straightforward. The initial implementation didn't take long, but I wasn't there at the time. When I became an admin, somebody else had already implemented it, so I'm unaware of the details. However, we did more implementations after that, but it was plug-and-play because we already had everything in place. There were no hassles. There's no maintenance on our side, either, because that's taken care of by Freshdesk.

The initial setup was easy for the average user. However, we did have instances where new features took a couple of days to implement properly.

The initial set-up was not easy, but it was not difficult either. It is like that with any new software that you use, you just need to get used to it. Thanks to great support from Freshdesk, every question we have had has been answered promptly.

Everything was simple except importing the help articles, which was awful. Aside from that, customizing the solutions centre stylesheets/page layout was very, very time consuming, but that's more unforgivable considering the heavy customization we were doing. We needed to use quite a few hacks and reach out to their support team for help with figuring out how they handle pagination, but again, nothing I wasn't expecting. the support team was great.

Everything about the setup was straightforward. It's not complex at all.

The initial setup wasn't too complex. It was easily understandable and quite simple.

The initial setup was not that straightforward.

It is simple and easy to use. All you need is the MobiHelp SDK, the credentials that they will give to you, and some codes.

It was complex to set up the parameters.