LogMeIn Resolve is an IT management and support solution designed to help organizations take control of their IT infrastructure. The platform combines features like remote monitoring, access, and support with tools such as ticketing, AI-assisted task automation, and patch management.
$29
per month
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
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.
N/A
Pricing
LogMeIn Resolve
ServiceNow IT Service Management
Editions & Modules
Remote Access
$29
per month
Remote Support Plus
$55
per month
Standard Endpoint Management
$70
per month
Premium Endpoint Management
$78
per month
Premium
Contact Sales
ITSM Standard
Custom Quote
ITSM Pro
Custom Quote
ITSM Enterprise
Custom Quote
Offerings
Pricing Offerings
LogMeIn Resolve
ServiceNow IT Service Management
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Discount available for annual pricing. MDM is available as a standalone or as an add-on. Additional endpoints and agents and save up to 20%
ITSM Pro and ITSM Enterprise also are available with optional "Plus" add-ons. These include AI Agents, an AI Agent Studio, and other features that augment the capabilities of the platform using AI Virtual Agents to automate tasks.
ServiceNow is robust and highly scalable, often favored by larger enterprises, while Zendesk and Freshservice offer user-friendly interfaces and customizable workflows that cater to smaller to mid-sized businesses. Now, comparing GoTo Resolve to these platforms, it stands out …
Task management is easy in ServiceNow compared to JIRA, Freshdesk, and other tools. Asset management and change management is easy in ServiceNow. Community support is the major advantage for ServiceNow. The API and extensibility of ServiceNow are very high. Considering …
I don't think I have ever encountered a scenario where LogMeIn is inappropriate. I work directly with customers 80% of the time, and even when I need to help a fellow IT professional out, LogMeIn is my go-to option. Viewing and reviewing all the units I manage is very helpful; it saves me a lot of time, especially after the frequent long-term power outages (where it surpasses the USP's protection) we often experience in our area.
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.
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!
I would say yes, we would definitely renew, everyone likes it in the IT dept, and there are more features we have yet to put to use. I am expanding the Windows update / Endpoint features as I get time, and the remote PowerShell console is unbeatable for me at present when facing remote computers that are not letting create a new remote PSSession.
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.
Navigation is easy and friendly. It does almost everything, but being cloud, it gets slow. Session recording is allowed. Zoom in and out feature works very well, especially during remote sessions and multiple machine sessions simultaneously. Dual-screen monitors are accessible. East and convenient user interface. The diagnostics feature is outstanding, and it gives detailed diagnostics of the system. So these are the pros that prompt me to provide such ratings.
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.
Usually available without a problem, although sometimes calls get dropped or users sit in empty meeting rooms while waiting for an admin to arrive, while the call is actually going on.
If you are connected to someone with proper bandwidth, there are no issues at all. With all things, if you connect to someone with dial-up (yes, it still exists), the performance is terrible.
Ive used their tech support a handful of times, and each time they have been able to help me sort out any hiccups or kinks that arise. They have a resourceful knowledge base, and have experts available for training and troubleshooting. I often recommend them to my other coworkers and colleagues because of the ease of use and security
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.
GoToAssist SeeIt was very easy to implement. As long as your techs have a basic understanding of most remote support tools they will be able to understand this product easily.
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.
I previously used Dameware but since they came out with the new version, I find it difficult to use. Many times, it takes a long time to connect using Dameware and the added time if it connects at all adds to the user's frustration as well as my own
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.
We are able to solve 99% of technical issues remotely.
Our productivity rate has increased because we are able to conveniently seek out assistance in the matter of a few minutes.
As this is compatible with Microsoft products like teams, this has allowed us to collaborate and save time and money by using existing software to submit tickets for assistance.
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.
