The fact that it emphasizes on the people and not ticket numbers is the best. In software such as Zendesk or Freshdesk, it is all handled using ticket numbers. But in Gladly it is all customer-focused. The entire chat, email, SMS and calls history of a customer can be viewed in one location by my team. This simplifies the working process since the agents do not need to pose the same questions more than once. Another feature I greatly appreciated as an IT Manager was its ability to integrate with our Shopify store and internal systems. The design is contemporary and clean thus the agents will be comfortable with it throughout the day. Review collected by and hosted on G2.com.

It is rather expensive, particularly when it comes to small Indian companies. Besides, the dashboard may be a bit slow when we access heavy reports of the past 6-8 months and it takes a few seconds to load. Review collected by and hosted on G2.com.

What I really adore about Gladly is its customer-centric approach and it truly puts the person at the center of every interaction. Instead of focusing on tickets, it’s built around ongoing dialogues, with a complete history across all channels, phone, chat, and email. Because of this, our agents can pick up the conversation seamlessly even if the customer switches channels, like moving from a chat to a call. On top of that, its intelligent recommendations help agents find solutions faster, which noticeably improves both efficiency and the level of personalization. Review collected by and hosted on G2.com.

The only problem that I have with Gladly is that reporting and analytics customization can be rather hard at times. Although it offers good standard measures, sometimes one has to go a little further to get to very specific, granular data points than one may prefer. Review collected by and hosted on G2.com.

The most impressive feature is the one lifetime conversation one. Granted, I have never been witness to such a clean type of dealing with customers in my 10 years of operations. My team doesn't have to look for ticket #12345 or #67890. All that is not far away under the name of the person. When a customer calls after two days, and he has already chatted with the agent today, then the agent knows what was said in the chat. This wastes a lot of time and my agents are quite pleased since they do not receive shouts about not knowing the history. The UI is also a very modern and colorful one, unlike these old assorted enterprise softwares. Review collected by and hosted on G2.com.

To be frank, it is rather expensive on a pocket of a developing team. The reporting dashboard is also somewhat unfriendly when you desire very in-depth data. It can also take a lot of clicking to receive a simple daily report. Review collected by and hosted on G2.com.

I like the way Gladly allows conversations to flow in a clear way. It assists me in learning about customer history without having to switch between different messages. The feature set allows managing various communication channels centrally. Due to this, my work is easier as I can easily resume a conversation. It minimizes the amount of work required to collect context and allows me to concentrate more on assisting customers in the appropriate way. Review collected by and hosted on G2.com.

The one thing I dislike is that it may be overwhelming to deal with multiple conversations at a time. Having a high amount of features, it may be not easy to find something quickly. This has impacted my work since I occasionally end up taking more time to arrange my queue rather than responding. This delays me during rush times and makes it difficult to stay abreast of the incoming traffic. Review collected by and hosted on G2.com.

Gladly’s most powerful benefit is that it’s people-centric rather than ticket-centric. The other tools create a new ticket every time. Whenever a customer emails, it creates a ticket number. It is very confusing. But in Gladly, one customer gets one screen. So if they chat today, and call tomorrow, I can view it all in one place. No need to ask Sir, what was your old ticket number? It keeps the customer happy and my end quick. Review collected by and hosted on G2.com.

The search bar can sometimes be slow. When I search for previous conversations by name, it takes a while to load. One other note the reporting dashboard is a bit of an initial mind fuck. You ll require a tiny bit of training around how very much chats your group finished in one day. It’s not just a matter of pressing a button. Review collected by and hosted on G2.com.

I have been serving as Senior IT Manager during the last 10 years and do use numerous tools such as Zendesk and Salesforce. But Gladly works differently since they are not depending on the amount of tickets. In fact, this is the best thing my team would like. The problem present in my company was that we needed a tool wherein my support agents can view the entire history of the customers on a single page. Whether the customer mailed one on yesterday, or they chat or phone today, everything is on one track. In my case as an IT head the integration part was quite simple. We have it concatenated with our shopify, as well as with our warehouse management system. It got online not very quickly, perhaps a matter of few weeks. It has a very clean interface as opposed to the old softwares which appear so complex. My agents trained only 2 days and were using it. This spared me a lot of time and effort. Review collected by and hosted on G2.com.

The key issue that I think is the price. To be quite frank, gladly is very expensive. The per-user cost may be very expensive to a mid-sized company and they lack a flexible plan that are available should you be having a small group of people. On technical side, I am also not satisfied with the reporting section being somewhat limited. The filters are not very user friendly when I need to extract very deep data to present to my monthly management meetings. At times, I need to copy all the data to Excel and undertake the task by hand. In addition, the agent app is also alright, but in some cases it becomes slow due to a high amount of chats. They are also expected to offer additional API extensions as customizations at no excessive costs. Their assistance is sometimes slow in providing technical responses, amiable yet slow with complicated problems. Review collected by and hosted on G2.com.

In my case, the most interesting aspect of the software is that it eliminates the possibility of information falling through the cracks. I have access to the discussion with each of the customers and what needs to be addressed. The quantity of features justifies the ability to make various kinds of inquiries and keep their status effectively. It will allow me to minimize errors, ensure a happy customer base, and make my task during the day more structured. Review collected by and hosted on G2.com.

One of the negative aspects that I have observed is that Gladly may seem bulky when attempting to perform some of the tasks. There are those that involve more than one step and this makes work slow during peak hours. They may complicate the directness of simple processes, but otherwise, they have a lot of useful features. Review collected by and hosted on G2.com.

As a Cloud Engineer I have to see how our systems are talking to the CX platform. The "Customer Timeline" is very impressive. If a customer sends an email, then calls, then WhatsApp message it is all one single scrollable timeline. No need to merge tickets and look for old history. It saves so much time for our agents and on the backend side, the integration with the API is very clean. The "Customer AI" is also very smart - the bot actually knows what the customer wants rather than just giving generic bot replies. Review collected by and hosted on G2.com.

The reporting side, in fact, is a bit tricky. If you are the kind who wants to make some really custom reports, then it takes some time to learn. Sometimes the dashboard gets a little heavy if there are too many active conversations during the peak seasons of sale. Also have I wish that they had more "out of the box" integrations for some of the niche database tools which we use, though their API is good enough to build our own. Review collected by and hosted on G2.com.

My favorite feature of Gladly is that it keeps customer conversations together as opposed to being divided into tickets. I have been using it everyday and the frequency doing the same is a true indicator of how natural it is to my work process. It integrates with services such as Shopify and Slack, thus, I do not need to change tabs to see the order information and team reports. The feature count is also good as long as handling emails and chats. Review collected by and hosted on G2.com.

One of the things I do not like about about it is that certain characteristics feel restricted when dealing with more complicated processes. This implementation was also delayed due to the fact that we needed to adapt our processes to suit the system. Another issue is that not all the tools can be easily integrated with and this led to delays in customer data synchronization. Review collected by and hosted on G2.com.

Gladly is great since it puts consumers first instead of tickets. I can see all of a customers past conversations in one perspective that helps me to grasp their situation better and provide them with the right answers. I don't have to search in different sections for old messages which saves me a lot of time. The UI is easy to use clean and basic. It does not matter if someone is new they will learn how to utilize it quite quickly. I also like the fact that it allows you to use email live chat audio and social media all in one spot. This helps me to be organized and help me get more done Teamwork is another great thing about it. Its easy for me to ask my teammates to help & switch chats without getting any information lost in the process. The way the notifications and workflow are setup is also good which gets me to keep track of all my customers needs. Review collected by and hosted on G2.com.

Some things could be better When there is a lot of talks going on the system can slow down which can make it harder to get things done at busy periods. Also some of the more advanced capabilities are hard to understand at the very first and need training or experience and Another issue is that there are not many options for customizing things in some places. For instance it might be easier to put up reports of workflows. Small problems or delays in updated things can also make the things less seamless sometimes. Review collected by and hosted on G2.com.