Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management.
$10,000
per year
eDesk
Score 10.0 out of 10
Small Businesses (1-50 employees)
eDesk is an eCommerce Help Desk purpose built for online sellers. eDesk integrates with marketplaces, channels, webstores and social channels and consolidates them into one shared dashboard. The solution provides tools and order data to help users to speedily turn around issues. eDesk allows users to respond to customer queries and meet their Service Level Agreements (SLAs) with Amazon and eBay. eDesk is designed to provide all the order, product, and delivery data within customer…
$0
per month
Pricing
ServiceNow IT Service Management
eDesk
Editions & Modules
Starting Price
$10,000.00
per year
Shopify Entrepreneurs - 300 Tickets
$39
per month 300 Tickets
eDesk Team
$69
per month per user
eDesk Professional
$109
per month per user
Shopify Entrepreneurs - 2,000 Tickets
$158
per month 2,000 Tickets
Offerings
Pricing Offerings
ServiceNow IT Service Management
eDesk
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
These are yearly plans paid monthly for using eDesk. Month to month plans are available
More Pricing Information
Community Pulse
ServiceNow IT Service Management
eDesk
Features
ServiceNow IT Service Management
eDesk
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
ServiceNow IT Service Management
8.8
68 Ratings
7% above category average
eDesk
10.0
1 Ratings
19% above category average
Organize and prioritize service tickets
9.967 Ratings
10.01 Ratings
Expert directory
8.051 Ratings
00 Ratings
Service restoration
7.956 Ratings
00 Ratings
Self-service tools
9.965 Ratings
00 Ratings
Subscription-based notifications
8.963 Ratings
10.01 Ratings
ITSM collaboration and documentation
9.060 Ratings
10.01 Ratings
ITSM reports and dashboards
8.162 Ratings
00 Ratings
Ticket creation and submission
00 Ratings
10.01 Ratings
Ticket response
00 Ratings
10.01 Ratings
ITSM asset management
Comparison of ITSM asset management features of Product A and Product B
ServiceNow IT Service Management
8.3
61 Ratings
1% above category average
eDesk
-
Ratings
Configuration mangement
8.060 Ratings
00 Ratings
Asset management dashboard
8.159 Ratings
00 Ratings
Policy and contract enforcement
8.952 Ratings
00 Ratings
Change management
Comparison of Change management features of Product A and Product B
ServiceNow IT Service Management
8.9
62 Ratings
4% above category average
eDesk
-
Ratings
Change requests repository
8.862 Ratings
00 Ratings
Change calendar
8.856 Ratings
00 Ratings
Service-level management
9.058 Ratings
00 Ratings
Self Help Community
Comparison of Self Help Community features of Product A and Product B
ServiceNow IT Service Management
-
Ratings
eDesk
10.0
1 Ratings
22% above category average
External knowledge base
00 Ratings
10.01 Ratings
Multi-Channel Help
Comparison of Multi-Channel Help features of Product A and Product B
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
Great for companies that sell on marketplaces and want to merge all of their communications. It saves our customer service agents tons of time, and it also connects easily with ChannelAdvisor. It would not be appropriate for a company that does not sell on marketplaces.
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
They were not even close to offering what xSellco has and the ease of using the platform. eDesk by xSellco is a great price point, is very easy to use, and it also integrates with ChannelAdvisor and Big Commerce, which was a determining factor for us. It also is an Amazon partner and ensures that they are adhering to all of the strict communication rules Amazon has.
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.