Oracle Service is the help desk and customer experience management platform from Oracle. The technology was developed and supported by RightNow Technologies as RightNow CX for cloud-based call center automation, until that company's acquisition by Oracle in 2011 for about $1.5 billion.
N/A
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.
We were running for many years the RightNow solution in a self-hosted type solution. We were being forced to the cloud to get updates to the software which prompted us to evaluate other products. RightNow Cloud and TeamSupport came out on top of our list of features we wanted. …
Oracle Right (Oracle Service Cloud) was an important evolution in the group's ombudsman channel management processes. We brought the Oracle Service Cloud to digitize the processes for capturing and managing the group's ombudsman channel, no longer operating manually (MS Excel).
Oracle Service Cloud (Right Now) brought about an important evolution in the management processes of the group's ombudsman channel, where activities that were performed manually, repetitively and with risk of errors, are now operated by the Right Now platform itself, whether by API, or by automation of the tool.
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.
Oracle Service Cloud needs a better built in integration with Oracle Social Cloud or it needs to build in more Social network capabilities.
SMS is handle via a third party application but could be built in as part of the product.
The knowledge foundation product needs a better way to handle multiple languages. Currently you have to purchase an additional interface for each language. You can purchase the more expensive Knowledge Advance which does have a better language feature.
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.
Although RightNow is extremely flexible, the flexibility comes with a price. It is often not intuitive which settings you need to change (and under which menus these setting are buried) to enable the system to do what you want. Also, sometimes the system can do things you need, but you don't initially realize it. When RightNow sells a system to a new customer, I think it should come with X hours of consulting time with a RightNow expert. The customer should be able to consult with this expert over the next year to get advice concerning how to configure the system to achieve desired needs. Often RightNow Support would just answer "no" when I asked if I could do something, but then I would find another way to achieve my goals after talking with other companies using RightNow.
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.
The learning curve is fairly steep; but for something that has this much capability, it's nearly impossible to make it "easy". The layout and organization are at least reasonably intuitive. The hardest part-- the "weakest link"-- is the portal development (where you can build help centers and other end-user pages.) The capabilities there are significant, but the learning curve for that part is especially steep and it takes a fair amount of expertise to be able to update it.
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 a lot of tabs and fields on our incident workspace, which should slow the system down, but it's still quite fast, and we continue to optimize whatever is possible.
Technicians seem to be assessed based solely on how quickly they close the issues. I've had to reopen requests multiple times because they didn't actually solve my problem. Also, when the issue has even a moderate amount of complexity, the technicians often instruct me to "open another SR" to handle the other issue. I'm the customer, I shouldn't have to follow their processes, they should handle that for me. But even when I create the new SR, it seems like their right hand isn't talking to their left - they aren't reading back to the previous issue for context. So I get bounced around a lot, and I have to tell them how to do their job
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.
Most of our training was given while doing user acceptance testing, and getting the system approved by the market. When ever we were in doubt, our implementer helped us along. Later on we started exploring by our selves.
Work with a RightNow expert during the implementation. Explain features that would you like to have. Often, somebody who really knows the system can show you what you need to do to achieve the desired results. Where a RightNow support engineer or a consultant might say "the system can't do that," a RightNow application engineer will listen to what you need, and often come up with an alternate path to achieve it
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.
TCS' customers who also selected Oracle Service Cloud over Salesforce Service Cloud and GE's ServiceMax in the Mfg. vertical in which I work, did so because of the robust ability of Oracle Service Cloud and its APIs to integrate with other value-add solutions for manufacturers such as IoT applications, Big Data Analytics, and Field Service applications.
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
