Service Cloud is a customer service platform that helps businesses manage and resolve customer inquiries and issues. It provides tools for case management, knowledge base, omni-channel support, automation, and analytics, enabling companies to deliver exceptional customer service experiences.
$25
per month
TeamSupport
Score 8.1 out of 10
Mid-Size Companies (51-1,000 employees)
TeamSupport is customer support software built for B2B software and technology companies. The solution offers ticket management, a customer and contact database, reporting and analytics, multi-channel support, built-in collaboration tools, and many native integrations.
$25
per month
Pricing
Salesforce Service Cloud
TeamSupport
Editions & Modules
Starter Suite
$25
per month
Professional
$80
per month
Enterprise
$165
per month per user
Unlimited
$165
per month per user
Unlimited+
$165
per month per user
Support Desk
$40
Per User per Month
Enterprise
$55
Per User per Month
Offerings
Pricing Offerings
Salesforce Service Cloud
TeamSupport
Free Trial
Yes
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
$2,000 per installation
Additional Details
—
Pricing is based on annual billing
More Pricing Information
Community Pulse
Salesforce Service Cloud
TeamSupport
Considered Both Products
Salesforce Service Cloud
No answer on this topic
TeamSupport
Verified User
Manager
Chose TeamSupport
I belive that ticket tracking service of Salesforce was another name when we evaluated it but TeamSupport provides a robust solution that works with SaaS providers at a fraction of the cost.
It is a helpful tool, but it can be a bit cumbersome to manage. It is also a bit expensive, but we already use CRM for Salesforce and it is convenient to be able to immediately tag contacts and accounts when the tickets come into the system and tie them directly to the account. I do know an integration with Jira is possible (we use Jira internally for our engineering team to escalate issues) but it is not configured right now so managing the connection between support tickets and Jira tickets is manual and hard to keep up with
TeamSupport is a great ticketing/help desk platform for small companies. It gets the job done and allows for multiple teams to manage workloads. It is not best for bigger organizations as there are lots of lacking features (mobile app, integrations, robust Jira/Confluence like system). The support for TeamSupport is great too. They usually get in touch with customers quickly when the system is down and they resolve issues quickly as well.
There were other customer support software companies that I looked into at first, however TeamSupport provided exceptional customer service themselves. I paid close attention to how they handled me as a customer to see if they were a company that would understand my desire to give exceptional customer service to my clients and if they had the tools to make the experience easy. Every interaction with them was very positive.
Since we needed TeamSupport's software embedded into our software application to give our users easy access to the support tools, the staff at TeamSupport needed to answer many questions and work with our developers to make this possible. They were always willing to take the extra step to ensure a smooth set up.
As we continue with TeamSupport, I am especially impressed with the sincerity of the CEO, Robert C. Johnson, and his commitment to us so that together we can deliver exceptional customer support.
We would like to see a structure to the ticket numbering system. In a previous system we had a numbering system like this mmddyy-xxxxxx This was very easy to see when a ticket was created based on just it's number. Currently with TeamSupport they assign a random number to tickets that is not very informative without a created date field.
Reports are nice but lack some rollup capabilities that are needed. Any given report can only work against two data tables at max. This is a limitation that we had to create custom contact fields to get around. They store phone, address and base contact info in separate tables. This makes it impossible with a standard system to create a report of all tickets along with the ticket and contact information in one report. The previous system we were on, allowed you to tie as many related data tables together that was needed to create one high level report.
Need Ability to notify external users of ticket activity in regions. So what I mean is we have FAE's in the field that want to know what their customers are asking for their region. They don't want or need a TeamSupport account but want simple e-mails of activity. This has been a lost feature for us going to a new system. I have to create a manual report each week and forward to the people that want this kind of information.
Ticket Automation rules will only run against a ticket one time. I understand why they did this to prevent uncontrolled loops but it would be nice to be able to set a limit that was greater than one. This limitation often causes us to have to write multiple rules to handle certain ticket cases.
Professional edition works best for a small company with lower call volumes and is very useful but as you grow exponetially I think it has limited ability to do all the things we want to - SLA management, defect, release management to name a few. Reports and dashboards being available in real time.
We are very likely to renew. We have been using TeamSupport for years and have tested a few other ticketing software solutions. We utilize several project management solutions to date and are always looking for better more efficient ways. Team Support is great at working with us and allows us to report issues well.
I had Salesforce experience prior to using Service Cloud which made it a little easier to learn and navigate, but overall my team (some who had no Salesforce experience) caught on very quickly and found Service Cloud to be easy to use.
I think some things could be a little more user-friendly: specifically the dashboard. Although it's fantastic and makes life so much nicer, I'd like to have more control on it's customization. I'd like to be able to default what's collapsed and what's expanded...instead of everything expanding by default each time I load it. But the portal offers great tools and guides on workarounds.
Salesforce's Trust Center clearly communicates occasional issues to anyone who subscribes, down to an organization's cloud instance. Bundled sandboxes ease updates, and seasonal upgrades are seamless, scheduled well in advance with plenty of information about what's coming. Support agents have noticed intermittent Omni-Channel disconnects due to internet connections, and these are clearly notified.
The Salesforce Service Cloud generally has very good performance, however the overall new Lightning user experience can bring that down. For example, if you have too many tabs open, then it can take a while for the Lightning UI to load. This UI is probably not well equipped to handle loading of all of that information at once, but Users tend to leave their tabs open all day long. It can also be fickle depending on which browser you use, what extensions you have installed, and whether you've cleared your cache. This can be the downfall with any software as a service though, not just Salesforce
Salesforce offers support, although it generally gets routed to overseas support teams first, and once they are unable to help, it gets escalated up the chain to higher tiers. Frequently, the answer back from support is that there is no native solution, and we either have to turn to the AppExchange for some solution provided by another developer, or custom build our own solution.
TeamSupport's ease of use and the way it benefited our company overall. From cost improvements, ROI, and overall management of team members it gets high marks. We are better able to support our customer base by providing improved support in a more timely fashion. The End User view of IT Support overall has improved just through using this platform in our company.
Our in-person training was provided by our implementation partner and it was quite good. This was in part because we were already working with them and so it naturally leant itself to a good training relationship. And because they were building our customizations and configuring things, they could then provide training on those things naturally.
Trailheads are great but it was often unclear what actually applied to our organization. This made it difficult to get a whole lot out of it. Part of it is that because the basic Salesforce features didn't quite work for us, we had to add customizations, which then nullified a lot of the training.
I would go through an implementation very differently knowing what I know now. It was difficult coming from systems we liked in post-sales service and having to adapt to the clunky and underwhelming feature set in Salesforce. I would trim back our expectations
Data import was the most difficult hurdle for us to get over. The mass import was handled through an Excel spreadsheet. TeamSupport doesn't use Microsoft Office products for the most part so they were relying on Google Docs which has limitations over Excel. Special characters and html in import cells can be a issue with importing. When creating a data export from your current system, special care needs to be taken so that the data is able to be processed into TeamSupport without issues.
Salesforce service cloud is more configurable than Zendesk and Freshdesk. It has its own inbuilt AI chatbot also which further improves service agent efficiency. Salesforce is more integration agnostic and has pre-built connectors with multiple 3rd party systems. However, in terms of pricing it is priced at a premium compared to the other solutions
TeamSupport is a much more modern, intuitive and user-friendly version of NetSuite with many additional bells and whistles. NetSuite has a business only facade with a rather clunky interface and system. TeamSupport compares favorably and meets business needs while being a much more advanced and modern solution.
TS keeps adding new features without making sure the program is reliable as-is. The program is frequently offline which makes for significant frustration on my part
Because this is a cloud service, the security, implementation framework and feature list is very mature and you don't have to develop these during implementation.
The larger the implementation programme the better the licensing arrangements
Free developer toolkit for proof of concepts or showcasing features