Lightning Tools Lightning Forms vs. Verint Voice of the Customer

Overall, there are many use cases for which Lightning Forms provides a slick, easy to develop and extremely useful solution. Request forms that need to be actioned and inspection forms are the scenarios that we have used them for so far, which have seen a lot of success. We have decided that other scenarios that are perhaps more sensitive, for instance forms that may contain special category data relating to our customers, are less appropriate given the permissions/licensing constraints of both SharePoint and Lightning Forms.

Verint Voice of the Customer is very well suited for measuring how satisfied (or dissatisfied) the customer base is in close to real time. Also well suited for identifying pain points across the experience. Not sure if the platform is well suited for measuring multiple interactions for a specified journey or a specific audience experiencing a specific journey

Incentivized

• Simple user interface - users of the forms intuitively aware of how/where to input information. This is in part due to being able to show or hide different questions or areas of the form, and making them required or not, based on previous answers.
• Low/simple code - building complex forms with automation and multiple dependencies or lookups is relatively easy once you get started. You have the power of JavaScript to use and do some quite clever things if you can get to grips with it - a lot of solutions are only a Google away.
• As it is based on SharePoint, it integrates perfectly with the rest of the M365 suite. Things like PowerAutomate enhance its functionality even further.

• Excellent Customer Service, training resources.
• Stable Platform- If a user gives a low satisfaction score, Verint Voice of the Customer can alert support teams to reach out and resolve the issue promptly.
• Verint Voice of the Customer gathers customer feedback on OhioMeansJobs.com, it can capture survey responses after job searches, resume uploads, or virtual workshops, giving a holistic view of user experience.

• The styling of the form can sometimes be slightly awkward to use depending on what you're looking to do. For instance, if I was looking to highlight fields that users have missed (left empty), I would need to set up a validation for that question and then set a style for that particular field for when it is invalid. When you have a large and complex form with lots of dependencies, this is awkward.
• Support for complex and niche issues is slightly lacking in my experience. I submitted a helpdesk ticket for help with a strange issue I couldn't figure out, which took several weeks to get a response to. Because it is niche, it's more difficult to find an answer by searching the internet. Luckily, knowing there is likely to always be a fix if you find the right place/use the right formula, I manage to resolve the issue with some trial and error.
• It is disappointing that Lightning Forms does not integrate with the MS Lists app. Having the ability to access the form through the list app would add in a lot of useful functionality, including a better experience for users when taking photos to add as attachments.

• Integrating with Google Analytics did take several sessions with their support team, so that could use improving
• Needed additional assistance from their technical team because of the configuration
• Limited customization for standard deployment survey templates. Some reports are a bit outdated

Incentivized

The cost versus product is a good value, so it all depends on the customer's needs/wants, and of course, budget

Incentivized

It is very user friendly both to me who is building the content (with little background knowledge of coding etc., other than what I have picked up from using products like PowerAutomate, PowerBI, a bit of html etc.) and to end users of varying levels of IT proficiency. This has been extremely important as we have used the forms to make relatively large process changes, and need to have our users on board and seeing that it is actually easier than it was before.

Overall usability is easy and while I have been using it for years and used to it, new users seem to be able to create surveys without any training or hand holding. Simply create a login and they can figure it out themselves quickly because of the intuitive nature of the layout. Verint could use to improve or update the user interface as it seems very dated visually.

Some support has been okay, but in one instance of a fairly complex problem, the support team were not able to provide me with a fix within a few weeks, before I was able to find a workaround myself.

Every support contact I have had, be it by email, live chat or phone, I have had my issue resolved very quickly, efficiently and professionally by a knowledgeable and well trained support team member. Having worked in technical support many years ago myself, I can appreciate the level of service and quality of support offered by Verint. I would, without hesitation, say that Verint offers one of the best support experiences out there.

We were using Microsoft Forms, SharePoint Lists and PowerAutomate to attempt to do much of what we are currently doing. Functionality is very limited in comparison. The ability to make questions required based on previous answers was a massive improvement from normal SharePoint List forms and has greatly improved the quality of data. Also just the very visual display and customisation is much better.

OpinionLab is one of the few out there that does two things very well in it's space: 1. Customer Feedback - just feedback, not surveys. Feedback is free text without more than one or two structured questions. Most survey systems offer too many options, and their reporting is made for structured data analysis not analysis of the open text fields. Some of the other tools viewed did not have the best features for medium or large scale deployment, from an analysis perspective, real-time data extract and download, or customization for branding.

Incentivized

• We changed the process by which site colleagues report repairs on behalf of customers. Instead of emailing them into a shared inbox, they now report them using a lightning form. We have seen a great improvement in the time taken for our team to log the repair issue from the time is arrives with them.
• We anticipate that streamlining our void property reletting process by using a SharePoint kanban board view with lightning forms (providing a single platform for all things void) will reduce avoidable days vacant and therefore reduce our void loss.

• Collect data around our login experience where eventually we were able to release a GPE directing customers to utilize our virtual assistant
• Verbatim around the claims experience allowed us to update our Claims Status page to provide more detailed, transparent information to the customer around the status of their claim.

Incentivized