Loop Returns, headquartered in Columbus, Ohio, offers post-purchase experience software to support ecommerce merchants, which features tools to turn returns into exchanges, support reverse logistics, create custom return policies with workflows, or allow customers to keep items that cannot be restocked or resold.
N/A
Oracle Service
Score 8.2 out of 10
N/A
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
Zendesk Suite
Score 8.6 out of 10
N/A
Zendesk is a customer support solution with built-in ticketing, conversational messaging, and live chat, designed to help businesses of all sizes and industries deliver personalized service at scale. Zendesk's AI agents are trained in CX to help Service teams resolve customer issues faster and more accurately while still providing a human-centered experience. Zendesk ultimately aims to help businesses improve time to value, reduce effort per ticket, and keep costs low.
$69
per month per agent
Pricing
Loop Returns
Oracle Service
Zendesk Suite
Editions & Modules
No answers on this topic
No answers on this topic
Suite Team
$69
per month per agent
Suite Growth
$115
per month per agent
Suite Professional
$149
per month per agent
Suite Enterprise
Contact Sales
Offerings
Pricing Offerings
Loop Returns
Oracle Service
Zendesk Suite
Free Trial
No
No
Yes
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Optional
Additional Details
—
—
20% discount available with annual pricing.
More Pricing Information
Community Pulse
Loop Returns
Oracle Service
Zendesk Suite
Considered Multiple Products
Loop Returns
No answer on this topic
Oracle Service
Verified User
Team Lead
Chose Oracle Service
At the time of our evaluation, the language and API support in Oracle surpassed that of Zendesk. The OOTB Knowledge base solution with Dynamics 365 was lacking in features.
Our company selected Oracle Service Cloud over others at the time because of the customization opportunities. In the original set-up and working with the Oracle team, we were able to essentially create a platform entirely based around our needs as a department. The reporting …
The only software I have used in the past, at another employer, that comes anywhere close to this functionality was Zendesk. It is not a direct comparison as Oracle Service Cloud offers much more than Zendesk's basic support ticketing and communications. At the scale and …
Oracle Service Cloud is more complete and flexible. It is an enterprise platform. 95% of products and capabilities are native and don't need add-ons.
Verified User
Analyst
Chose Oracle Service
We switched from Zendesk to Oracle, and there are definitely pros and cons to each product. Zendesk is definitely easier to navigate and has a more simple feel to it. However, Oracle has a huge advantage in how many different services it is able to integrate into one platform. …
I highly recommend Loop Returns to anyone who is looking for a new returns platform. Their solution is fantastic and the service they provide is top notch. However, budget may be a concern for some businesses as they are more expensive than other solutions. I feel they largely justify the cost increase with their support, but not all companies will feel this way.
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.
Zendesk is good for small teams where work is not passed along to internal teams or situations where escalations lead to further customer interactions and no further oversight is needed. It is weak as a product for larger and medium-sized companies, where processes are in place that are not aligned with its workflow, as it is a very rigid tool.
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.
Is there a way for AEs and CSMs to be informed in a weekly summary of all their accounts and any tickets? Example: Disney submitted a ticket on XYZ. Google has an urgent issue on X still unresolved.
Is there a way for CSMs or AEs to have a Dashboard that's specific to their accounts instead of seeing all the tickets in the queue that are not relevant to them?
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.
Zendesk is an amazing tool for communicating with your customers easily. The communication tickets from sellers to us or from us to sellers are stored, and there are statuses used to make communication easy. We have internal conversations between departments, linked with useful software such as Zingtree, Talkdesk, and Webs.
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.
Pros: The agent interface is sleek, contemporary, and relatively easy to learn compared to many other enterprise tools. For common tasks, admins are given point-and-click options- adding fields, modifying workflows, constructing macros. The knowledge base (Guide) editor is easy to use for non-developers. Drawbacks: Once you move past the initial things - complex automations, reporting/analytics in Explore, and/or customizations integrating the API, it requires much more advanced training to use successfully. Navigating between the different modules (Support, Explore, Chat, Guide) can feel very disconnected; often you are reminded that it really is a "suite" of products brought together -not really one unified platform. If you're using multiple brands managing simultaneous support tickets, or heavily customizing workflows to meet your brand, you may run into a bit of struggle with usability. So: it's a lot more user friendly than the palaces (Salesforce Service Cloud, ServiceNow), but is not used as quickly or with as much streamlined flow as a product made for a small shop. So if you are looking for a great balance, this is a good option if you are a net new organization or an organization on their way to scaling from 15 - 50 employee. Expect some elbow grease from the admin team once learning, adapting, and working efficiently once you move past the basics with your support tickets and initial customizations.
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
We rarely need to contact their support team, but when we do they are responsive. However there have been notable times when communication between myself and the support rep was challenging despite me providing clear explanation of the issue, screenshots, and a thorough explanation of the goal we hope to achieve. It took several back and forth attempt, on a few occasions, to get resolution on an otherwise simple request
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.
Zendesk has tons of available material for training - videos, webinars, articles, etc. The only reason this is not a 10 is because it can be hard to figure out how to navigate to these things and find what you are looking for.
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
I was very satisfied. They have a free trial for 30 days and I recommend you do that and use it. It is very easy to get started with the basics and the build on over time.
The only thing technically complex was single sign-on and integration to Salesforce.com required some tweaks – otherwise setting up system was very easy
Loop Returns had a better core feature set than Returnly, which is why we selected them - though Loop Returns has since acquired Returnly, so this point is more or less moot.
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.
At the time of evaluation, Dynamics had extremely limited knowledge and support capabilities. The UI is clunky, and reporting requires a deep understanding of the underlying data structure. Ongoing maintenance was costly and didn't provide a positive ROI in any sense of the term.
