The SAP Customer Data Cloud, based on Gigya (acquired by SAP in 2017) is a product suite that allows users to identify consumers, business customers, or partners across devices and channels to drive registrations and engagement; manage access, permission, and consent; and transform data into unified customer profiles.
N/A
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.
It's best suited for business business to turn digital interaction in to richer and high value and experience that reach across computing platform also it offers a holistic and integrated approach to managing customer data and enhancing and personalized experience.it also draw actionable insights.because it offers wide range of products . perfect customer insight data solutions
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.
SAP's Customer Data Solutions provide a comprehensive customer view by collecting detailed data, including age, web activity, and buying history.
The software's strong analytics features give valuable information about how customers use content and products, so we can enhance our strategies.
SAP Customer Data Solutions offers insights to create specific marketing campaigns that sort audiences by preferences, browsing, and purchase behavior.
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.
I find the interface a bit complex and challenging to navigate. I remember having difficultly grasping it completely especially when I was new to the system. Simplifying the user experience would make it more accessible for everyone, making tasks quicker and more intuitive.
integrating it seamlessly with other software and platforms could enhance its functionality. I would really really love an integration between BenchMark email marketing tool.
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!
On the whole I am really impressed with SAP Customer Data Solutions and would highly recommend that other professionals look at this software to enhance their B2C and B2B sales
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.
We mostly work with the API which is of very good quality and is well documented.However, some of our success is also due to having very talented developers on staff, and also understanding advanced gamification design. The tool supports a talented team! It won't actually do everything for you automatically.
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.
Customer Data Solutions availability has been pretty good, anytime there has been any issues like I mentioned before, support staff has been quickly avialable to help trouble shoot things. Customer data solutions has had very few outages during out time using it as well and when they happen it's a quick resolution.
There are some latency issues. The 24 hour caching problem mentioned earlier is a problem. Sometimes the Gigya system makes two calls instead of a single call if we go directly to the social platform. For this reason, it's sometimes more efficient to go direct rather than use Gigya.
We have had multiple instances of help from Gigya to get our custom implementation working, including detailed technical assistance to a third party. We have found Gigya to be thorough and timely in their responses to all queries, which are consistently excellent.
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.
They trained me in a train the trainer model. I then trained the internal team. Total training was about two hours, with an additional two hours for system setup. Training was maybe a little thin, but the system was fairly easy to learn and this wasn't really a problem.
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.
There was a bit of a learning curve in the beginning, and perhaps we were unclear on some of our requirements. Once they figured out what we wanted though, things went pretty smoothly. Just some minor hiccups in the beginning
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.
There is a dedicated team for SAP setup that helps in providing specialized or customized services to the user. The platform's accessibility lets us obtain reports and information in real time so we reach clients at the proper moment by optimizing delivery time appealed to us the most.
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.
