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
Veeva CRM
Score 7.7 out of 10
N/A
Veeva CRM is an enterprise customer relationship management application for pharmaceutical, biotech, consumer health, and animal health companies. CRM supports field sales and medical teams, including primary care, specialty care, key accounts, retail sales, and medical science liaisons.
N/A
Pricing
ServiceNow IT Service Management
Veeva CRM
Editions & Modules
Starting Price
$10,000.00
per year
No answers on this topic
Offerings
Pricing Offerings
ServiceNow IT Service Management
Veeva CRM
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
ServiceNow IT Service Management
Veeva CRM
Considered Both Products
ServiceNow IT Service Management
No answer on this topic
Veeva CRM
Verified User
Partner
Chose Veeva CRM
As Veeva CRM is built on Salesforce' platform, both solutions have rather similar look, feel and offered set of functionalities. Veeva CRM is geared up specifically for the pharmaceutical industry - to my understanding, there is an agreement between the companies, preventing Sal…
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.
Good for larger teams with a lot of activities and therefore a good justification for the investment. Great for 'as above' + the companies looking to integrate Veeva CRM with other Veeva offerings, such as Align, Inslight, Zinc/PromoMats etc. Not so great for smaller organisations or those with more slightly more restricting budgets.
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.
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.
Oftentimes it is the field sales force that heavily influence the choice of the CRM solution. It appears that many of our field sales force prefer Veeva. Happy reps = more actively used CRM = clearer understanding of the reps' activities.
Veeva offer 2 implementation versions - out of the box implementation (around 6-8 weeks to install) and 'all singing, all dancing' implementation (based on the length of your specific string). You can pick one and therefore influence your ROI accordingly.
Again, as Veeva CRM is pretty much a de facto CRM solution, this is good for scalability if/when rolling it out across multiple regions/branches
