Field Service (formerly known as Field Service Lightning) is a customizable, mobile-friendly field service hub in Salesforce. It provides tools to manage work orders, scheduling, and a mobile workforce.
$50
per month per user
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
ServiceNow is a fast-growing service management provider that went public in 2012. 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, and (on the higher tier ITSM Professional plan) ITAM and software asset management.
ServiceNow far outweighs Salesforce in its case management and has easy forms for work order creation. It's much easier to integrate with and has better workflows and troubleshooting tree guides. However, it's not ideal to be used for a CRM nor does it have anywhere near the …
ClickMobile can be implemented in virtually any organization that has a need for a Mobile Workforce Management system. The only real limitations or concerns will be with the backend hardware architecture. Sectors that have really seen the best utilization of the software are ones that have a dynamic service schedule and need to be extremely flexible with their customers service needs. In a day where customer service is so important to an organizations ability to remain the market leader it is extremely important for an organization to consider implementing a mobile solution. For organizations that already have a mobile management solution in place it is critical that they continuously reevaluate the system in order to remain competitive in their market and drive down operational costs. Change can be difficult for many organizations and the buy-in from the Field resources, who will ultimately be utilizing the mobile solution on a daily basis, will be critical when implementing something like ClickMobile. If the field resources are not able to accept a change to process then Change Management needs to take place during the implementation. It is generally a good rule to begin Change Management at the beginning of any large project, such as one where a mobile solution is being introduced.
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!
ClickSoftware is still being used. As far as I can tell it will be used tomorrow as well. Once you make the commitment to run with that as your scheduling engine, it would take a lot of effort to evaluate and implement another companies' solution without significant disruption to your service organization.
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.
We had to contact support a number of times related to bugs that our admin/dev teams were not able to troubleshoot. Unfortunately the Salesforce support was not super helpful, asking us to perform steps that we already completed and included in the original support ticket. Then the problems couldn't be reproduced so ultimately the tickets got closed without resolution. LWC support in the mobile app is severely lacking.
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.
Overall the training was quite informative but did lack detail in some areas. It had all of the necessary content for an experience product user but didn't offer enough information for a new user to complete the training and then feel comfortable in real-world situations running or managing the software. I would recommend this course for anyone with at least 1 year of full-time exposure to the ClickSchedule product.
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.
I know of IFS but I do not think it is a worthy or close competitor to Salesforce Field Service lightning as its not that user friendly yet with a complicated interface. Also it does not have the name and respect and brand value that Salesforce commands in the market thereby making it easier for Business to approve.
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.
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.
