ConnectWise PSA (formerly Manage) is a business management platform for companies that sell, service, and support technology. The platform is cloud-based and integrates automation, help desk and customer service, sales, marketing, project management, and business analytics. It is the hub of the ConnectWise suite.
$35
Per Tech Per Month
Salesforce Agentforce Service
Score 8.6 out of 10
N/A
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.5 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.
$45
per month per user
Pricing
ConnectWise PSA
Salesforce Agentforce Service
TeamSupport
Editions & Modules
Subscription
$35.00
Per Tech Per Month
Starter Suite
$25
per month
Pro Suite
$100
per month per user
Enterprise
$165
per month per user
Unlimited
$330
per month per user
Agentforce 1
$550
per month per user
Starter
$45
per month per user
Professional
$65
per month per user
Scale
$85
per month per user
Offerings
Pricing Offerings
ConnectWise PSA
Salesforce Agentforce Service
TeamSupport
Free Trial
No
Yes
Yes
Free/Freemium Version
No
Yes
No
Premium Consulting/Integration Services
No
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Optional
Additional Details
—
—
Pricing is based on annual billing
More Pricing Information
Community Pulse
ConnectWise PSA
Salesforce Agentforce Service
TeamSupport
Considered Multiple Products
ConnectWise PSA
No answer on this topic
Salesforce Agentforce Service
Verified User
C-Level Executive
Chose Salesforce Agentforce Service
This solution provided our organization a flexible platform. The other solutions were rigid or required complex integrations.
TeamSupport provides an easy to set up, easy to manage ticketing platform for our company. While SolarWinds and ConnectWise offer more bells and whistles, they also require a great deal of setup and configuration and more time managing. TeamSupport also comes in a very …
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.
BrightGauge lets us know when we have critical issues that need solving. A massive influx of tickets all at the same time triggers an investigation. Usually, it is tied to a server going down, which we can address. It would not be helpful for a small MSP or IT department with just a few daily tickets. The stats are better used to track a large amount of clients.
I think Service Cloud is best suited for medium to large operations that require both proactive and reactive service. It’s a great fit for post-sales support. However, I wouldn’t recommend it for very small companies because it can be quite costly, and many of the features may go unused. Salesforce also performs best when you have a capable team managing it, so it’s important to consider your organization’s size and readiness before starting. Once you do, I recommend exploring other parts of the Salesforce ecosystem—Service Cloud works even better when integrated with Sales Cloud, since it allows better visibility across teams.
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.
Tickets- Customers can email and a ticket is generated and falls under their profile for historical records. You can save documents and select if they are customer facing or only internal facing. The option as well to have communication in tickets whether its internal facing or customer facing is nice to have when you're trying to keep a record or important details for just internal means and the customer doesn't have to see all the jargon.
Procurement - It's great to have this integrate with Quosal Sell. Quotes being processed into opportunities and then into a sales order which connects to a ticket or project is pretty easy to use. It does have a learning curve but once you get the hang of it, it's straightforward. Everything is pretty connected, whether keeping track of products customers have purchased historically through us, to knowing what ticket is associated to an RMA.
Email to case is an interesting piece of it. The threading is very strong, sometimes too strong, but it does very well at handling the incoming emails.
The omnichannel routing, using skill-based routing is really effective.
Pathing. So making the workflow and helping the team understand what it is that they're trying to do, what they have to accomplish, those step-by-step pieces. That's really helpful.
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.
Annual or more than annualized data is desperately needed for MSPs to show trends, current limitation is previous 240 days for ConnectWise tickets
Alerts when datasets do not sync properly, I have to rely on my team to notice vs get an automated alert from BrightGauge
Small thing, but it would be nice to have more options on the report scheduler to enable a start date. If you wish to do it quarterly, you have to start the schedule exactly 3 months from the next run.
We had a principle initially to try and use Omni as much as we can from the user experience perspective, but have found that fairly restrictive. It was very difficult to actually get the right customer experience and customer engagement going. So we're actually on a journey at the moment to replace all of our Omni with Lightning web components that gives us that flexibility. That's probably one area where we've had some challenges in terms of how we've used the product out of the box.
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.
ConnectWise has uniquely positioned themselves with the Modern Office Suite to have direct integration with a nearly full suite of tools for MSPs. Although each tool may not necessarily be the absolute best tool on the market, the efficiencies leveraged through direct integration make the entire suite an obvious choice for most companies.
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 have been using ConnectWise since 2004 and I am impressed with the progress they have made. However, there are still bugs that don't work quite like they should. If I were to run reports and get consistent answers along with a couple other annoyances, then I would score CW as a 10
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.
We use the cloud version of ConnectWise and in the last 5 years it has never been down for us during business hours. I can only recall 1 time when it was not available during off hours when we wanted to use it.
Working on an application that caters to customer needs requires a platform that acts as a mediator between the actual person and the client. This mediator handles the customer and resolves many of their doubts, helps them map through the entire process, and automates the processes. Such a platform is Salesforce Service Cloud. For queries that cannot be serviced by the platform, it creates a separate ServiceNow ticket for us, and it is assigned.
Some tab for certain areas load speeds could be better. Dashboards can load slowly when they reference multiple reports. Some reports can load slowly based on the tables and views they are accessing. At times the SQL queries being performed in the background can actually timeout and a tab or screen will fail to load.
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
The front line support techs are wildly inconsistent when it comes to the level of support. Sometimes you get someone who just wants to throw links to University documentation at you, sometimes you get someone who truly tries to understand your issue and confers with peers and managers to find an answer, and sometimes you get someone who just wants to create a ticket and escalate immediately. If you ask three different techs the same question you will probably get three different answers, one of them being, "That's not possible."
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.
We are a telecoms company. Whilst CW were very happy to sell us their product and tell us how good it is for telecoms. All the training material is geared towards IT MSP's. The on-line training material was virtually useless. We found the implementation a bit of a joke. They tried telling us 12 hours of implementation time would be sufficient to launch the product. We erred on the side of caution and paid for 24 hours. This was quickly eaten away and we were nowhere near ready to go-live. I find the on-line chat facility is of much more use for us.
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.
Rather than letting them sell you a block of time for implementation, create a list of things that must be completed do declare the implementation complete. The implementer will have the discretion on what they set up and in what order. They will be trying to end their services in as little time as possible and may not get things set up right. You are best advised to hire a third-party wizard that has done many of these setups. Record the audio and video of all of your implementation sessions.
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.
Everyone but dynamics had holes in it. Dynamics is good, but it requires more development time. I spoke with some people that have CW and liked it. But when I inquired after our frustrations, I discovered they had a full time scheduling & logistics CW manager and the field people were using it purely like any other more simplistic ticket system. They said it would be impossible otherwise. The one big difference is the transparency of the sales effort. The other sales people were honest on the limitations or potential challenges and worked with us. They also worked with our agenda. At CW they don't have that option. The consulting time is eaten through a pre-formatted agenda which they communicate too you, not with you.
We selected this product because we already had some competencies in Salesforce. We own a Salesforce partner with expertise in this area, and on top of that, Salesforce purchased it — it was originally called Velocity. When Salesforce decided to acquire it, that finalized the decision for us.
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.
ConnectWise seems to have a good understanding of the IT service industry. During the required onboarding training, they even preach configuring only features that you need right now, as you can always scale up later. The feature set for the most part takes into considerations all aspects of an IT business, whether small or enterprise, or growing from one to the next.
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
We have cut our service team in half over the past 5 years due to the efficiency of the tool
The amount of direct inquiries to our technical team is less than 10% compared to the number support tickets that get entered in the system for them to work in a more organized manner
Responses are 100% more timely because tickets can be responded to by any individual in the queue or on the team, as opposed to direct emails to just one person
