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
Wrike
Score 8.6 out of 10
Mid-Size Companies (51-1,000 employees)
Wrike is a project management and collaboration software. This solution connects tasks, discussions, and emails to the user’s project plan. Wrike is optimized for agile workflows and aims to help resolve data silos, poor visibility into work status, and missed deadlines and project failures.
$240
per year 2 users (minimum)
Pricing
TeamSupport
Wrike
Editions & Modules
Starter
$45
per month per user
Professional
$65
per month per user
Scale
$85
per month per user
Wrike Free
$0
per month per user
Wrike Team
$10
per month (billed annually) per user (2-15 users)
Wrike Business
$25
per month (billed annually) per user (5-200 users)
Apex
Request a quote
per month per user
Pinnacle
Request a quote
per month per user
Offerings
Pricing Offerings
TeamSupport
Wrike
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
Optional
No setup fee
Additional Details
Pricing is based on annual billing
Every premium plan begins with a 14-day trial period.
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.
I believe it's well suited if you have multiple jobs/projects that you need to keep organized. We work with multiple job types from print/creative to web, copy and digital ads so it helps us stay organized. I don't think it would be suitable for a company that doesn't have a lot of jobs to manage. We average over 1,200 requests a year.
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.
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 wish that Wrike had more drag and drop functionality that would be connected to assignee and also I wish that the finish date of a task would update to the date where you checked completed. It does not do that. Also finishing a task doesn't move the start date of the next task it "protects your time in that way", but our management team wants us to quickly see what we have down the pipeline rather than having to scroll down the list of upcoming tasks.
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.
It does take some time and work to really understand and use it properly, but I think the accessibility to help and documentation make that completely feasible. Once you know how to use it, I find it to be very user-friendly, and have very few complaints.
Over two years of (almost) daily usage without outages. Don't remember any errors. I give it 9 only because some Wrike plugins (for online document edit) are based on NPAPI architecture. These types of plugins are being phased out in new browsers, and NPAPI plugins are disabled by default in recent versions of Chrome so you have to do some browser adjustments when you switch browsers or move to another computer.
Wrike tasks loads fine, but I hate clicking files and wait for a bit of time since it is powerpoint or word, Wrike assumes I want to open those on Wrike. My suggestion is to link it to office 365 so we do not need Wrike based decoder for PPTX and DOCX
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.
During my learning phase with Wrike, I initially struggled with setting up automation rules and request forms. However, Wrike support was always my go-to, resolving issues within seconds or minutes. Their assistance made the learning process much easier. My best experience was receiving step-by-step screenshots to follow, with the support team on standby until I was completely satisfied.
I love the Wrike training options. Wrike Discover has tons of courses, learning plans, certifications, etc. This is an area where Wrike definitely shines! I wish these resources were more in your face for new people, because it seems like a lot of coworkers didn't know all of this training was available to them.
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.
There are a lot of bells and whistles in Wrike, and not all of it is easy or intuitive to understand once it's plopped in your lap. It's easier when there are a few choice people who understand Wrike as a platform and articulate it in such a way where it makes it easy to pass it along to others in the group
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.
Jira did not at all help us get our work done as content creators. I think that was because Jira wasn't quite right for our uses. Wrike fits our needs so much better. I can't tell you enough the relief I felt when we adopted Wrike and I never had to use Jira again.
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
The sky is the limit for what can be done in Wrike. We started with 1 use case and within 5 months we migrated several key business practices over to Wrike because they were easier to manage. Use cases so far: process improvement, management review, corrective actions, maintenance requests, month-end financial closing, and document management. As we grow, it's easy to imagine putting even more into Wrike where it becomes a cornerstone for how we do business
Different teams (e.g., contracting, compliance, provider relations) can view updates in real time, comment directly on tasks, and escalate items when needed.
Wrike allows us to template the contracting process (from intake to signature) to ensure consistency across payers and reduce administrative overhead.
Leadership can see the status of negotiations at a glance, identify bottlenecks, and prioritize resources accordingly.
