Microsoft Dynamics 365 is a CRM providing sales, marketing, and service functionality. It is offered as SaaS and on-premise. Dynamics 365 is part of the larger Dynamics suite of business intelligence and ERP products.
$44
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.
It is average. I feel some free CRMs might be better for some organizations depending on their needs. MS Dynamics has potential, but there is kind of a 'white elephant' feel to it.
Provides our company access to manage and customize the folds tailored to our needs. We needed to have certain paragraphs on certain paperwork per customer. MD 365 has those options to customize where needed and remove when not. The system is easy to navigate, and training can be done in a matter of days, even without prior knowledge of the system or similar systems.
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.
Best to use for AP - like in our organization, there are plenty of AP bills, so with Dynamics, we can quickly enter the same into the Excel utility, which means CSV-based upload, and then we can easily upload the same to the software. It's a time saver.
Best for Bank reconciliation - MS Dynamics makes Bank reconciliation easy. Banks can easily sync with software and easily get reconciled.
Generating invoices to customers and directly sending them to their inbox is easy with this software.
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.
Small learning curve, obviously. You won't figure this out in a day, a week, or even a month. But given time, you can learn to be an expert. Or you can always get a consultant or hire in somebody. But learning the tool isn't out of the questions by any means.
Licensing can be confusing at times and isn't cheap, but it is cheaper than Salesforce. Plus no additional fees for data calls to better integrate your D365 CE data with other systems.
The Classic user interface left a bit to be desired, but now with the much-improved Unified Interface, the web client and the mobile client look the same, much more modern, and have more flexibility and power behind them for customizers as well.
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!
CRM has allowed us to keep all of our data in one place that is easy for all users within the company to view. I came into the company after they had been using CRM for about 4 years. They have all said that since we have used this it has helped us control work processes better, it has allowed us to be able to track things so much better, and has been something that has helped unite many processes that used to be all over the place. We are currently using CRM 4.0 and are planning on upgrading in the next 18 months to the 2011 version. Support for 4.0 is almost all but dried up. Understandably so. Some of the customization we have done, and a plugins we use, are now contained within the 2011 version so we are looking forward to that upgrade. We use an email marketing company as well, and they primarily support the 2011 version, but their product connects and is integrated within CRM. This is a great benefit as well so that all of our marketing information can be contained in one location.
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 usability is easily adopted for users familiar with other Microsoft products. Dynamics 365 has several interfaces that cross over browsers and tablets. These multiple interfaces will be phased out and updated to a single unified interface eventually to provide the same usability across all devices. The backend configurations is slowly improving with the introduction of PowerApps compared to pre-D365 Online versions
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.
Our partner, Ledgeview Partners has been FANTASTIC to work with. They are always timely in their response and have taken time to understand our business and our specific needs. We've made a lot of advanced customizations and they have been a great help in making those updates.
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.
We used a data warehouse to house our data, and our IT team and implementation vendor worked diligently ahead of time to construct idea implementation plans. Out of millions of records- we had less than a dozen errors, which is remarkable. My major insight is simply having a group of completely devoted individuals working towards your goal who fully understand the desired outcome. Focused resources for implementation season are critical to success.
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.
Microsoft Dynamics was part of a system overhaul for a local school, and we looked at many products. If we had used it for a company with low turnover, then it might have been more feasible. They needed something a new person could learn quickly, someone who might also be learning marketing terms at the same time - especially if there is nobody to train the individual now expected to know the system. Similar issues occurred with all of these programs (we called it being too big for their britches), and one of the bigger things we liked was that it is more compatible with MS Office products in both technical and visual appeal. If you have a steady employees who use a CRM consistently, low turnover, and those who are very familiar with Office products, Dynamics would be the smartest option for you. Unfortunately, this was just not true for the school environment
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.
On our purchase, I'd been interrogated about our usage. Our needs are met by Microsoft Dynamics 365, which is simple to use. With so much data and information available, we must ensure that it is presented correctly to managers. Due to a lack of use, we don't have to spend as much money on Salesforce.
My company's preferred program right now is Microsoft Dynamics 365. We use it to keep track of customers and important sales metrics in a streamlined manner. Anyone familiar with CRMs will find the tool extremely useful. Considering that we have a good turnover, this product will be used for its basic segments. As a result, there are few chances of error with Microsoft dynamics because it is so easy to use. Many options for recording data on these leads are available. It meets our needs and pays off.
For those without a centralized, all in one solution for major HR, Finance and other departments, Microsoft Dynamics 365 has vastly improved employee time utilization and profit.
Migrating clients from on-premise to the cloud has reaped benefits including better security, no unscheduled downtime and frequent updates to functionality.
Those transferring from cheaper solutions have lost money in the aim to be better integrated with other Microsoft products and AI they don't really utilize.
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.
