Mark Smith's Analyst Perspectives

Is NetSuite Sweet for Customers?

Written by ISG Software Research | May 26, 2016 4:58:59 PM

It’s widely agreed that customer experience is now the most important dynamic for business. Any organization that wants to retain loyal and even vocal customers should do everything possible to ensure and maintain customer satisfaction. Software companies, especially those that promise to provide CRM and effective interactions across any channel at any time, should be good examples of embracing the methods they prescribe for using their products. But do they?

Maybe our organization is not having great luck at the moment. We just went through a bad experience with Salesforce, which had a cascading technology failure (known as #NA14) of its data center and database operations that shut down thousands of customers that, like us, use its software. Of course, technology problems happen, but there is no excuse for poor communications that don’t explain a situation and provide regular updates, not to mention prompt resolutions. Customer communications and supporting processes ought to make customers feel that they and their business are important to the provider. Salesforce CEO Marc Benioff was more than communicative and listened to comments on the issues directly through social media; now we wait to see what changes the company will make in its customer relationship processes and communications.

Unfortunately, around the same time as this fiasco another one occurred, originating with the cloud-based ERP provider NetSuite. Here again there appear to be some very large challenges with its customer relationship processes and resulting customer experience. Our analyst firm tracks and has recommended NetSuite as part of our research practices and advisory services to organizations and business professionals on applications, as in this analyst perspective by my colleague Robert Kugel. In October 2013 NetSuite announced its acquisition of TribeHR,  a cloud-based provider of a human resources management system (HRMS) for small and midsize businesses. Our firm at the time and continued to be a happy customer of TribeHR but also an advocate of and reference for its efforts, as I wrote in 2012 and part of our human capital management research coverage.

After the acquisition, at end of 2015, I received an email from an individual supposedly at NetSuite billing us for use of TribeHR. I was not sure if the message was legitimate, as the usual form of business communications to a customer and did not identify the person’s position in NetSuite. As you may know, it is a common scam to send invoices and ask for payment without context; this is an issue the FBI’s Internet Crimes Division is actively addressing where individuals are asking for payments through emails and PDF that appear to be legitimate. We ourselves have been attacked by these scams though our governance processes have prevented any mispayments. I sent an email reply to ensure that the sender actually was from NetSuite and asked for the agreement for the invoice; I got a generic reply that did not identify the person or department and said only that the invoice was related to back billing for TribeHR access. I asked again for proper identification and a copy of the license agreement and terms for payment. This was the last I heard about it. I never got a call from an account manager or anyone else at NetSuite to address the situation. Of course it could have been resolved easily if NetSuite had embedded online billing and payment from within the application. Obviously this was not a satisfying customer experience for something as easy as clarifying an invoice and setting up recurring payments from our organization.

Then, out of nowhere, on April 22 our instance to TribeHR was shut down without notice. Attempts to log in by anyone in our company received this boilerplate message: “Your account is currently suspended. We are sorry for any inconvenience this may cause. Please email support@tribehr.com and collectionsteam@netsuite.com to reactivate your account or submit related questions.” I sent an email, and the HCM Customer Success team at TribeHR responded quickly to let me know they were investigating. Clearly the vendor could and should have been more proactive. We have a prominent website, I myself am easily found through social media, and most importantly I am the main contact within TribeHR where I am listed as the system administrator and human resources contact. All NetSuite had to do was use the customer information in our instance of TribeHR. Any communication at all could have remedied this situation; it was even worse since the communications with me in December were never followed up as I requested.

Next a new person contacted me for the first time, saying he is our account manager. He told me that the invoices were sent to a person who has not been with the company for seven years at an outdated mailing address. I requested that the outstanding invoices be updated and consolidated in one agreement. I signed a new agreement on May 10 and emailed it back, requesting a credit card link so we could get it paid immediately. I was told that once the order was processed we would get an invoice and payment link. This was important as the terms on the agreement I signed said that payment was due upon receipt. But the updated invoices from the beginning of the year and a link to pay them did not come.

Then on May 24, our system again became unavailable for use. In response to my inquiry our instance was reactivated and I was informed that it was not clear why we were turned off and that the invoice would be sent to our accounting for payment. I thought it weird that no one from NetSuite had called or emailed to let us know it would be turned off. Forcing customers to chase a software vendor to pay for services is certainly not a best practice.

At this point I thought it would be worthwhile to make sure that the CEO of NetSuite, Zach Nelson, knew about our problems and poor customer experience, so I put it on Twitter to elevate the situation: “Looks like @NetSuite just shut off @TribeHR customers from access to its HRMS - not a good signal to HR & biz for them! #FAIL @ZachNelson” and then “@NetSuite @TribeHR @ZachNelson and email my rep and it is turned back on! When do sales control customer access to apps?”

Five hours later I got Zach’s response: “Should we be mailing the collection notices to someone else in your company?” I responded “@ZachNelson @NetSuite @TribeHR you are really out of touch! I asked your sales rep to get our accounting team an invoice to pay & waiting!” and “@ZachNelson @NetSuite @TribeHR if you would like emails to your team I am happy to provide! Instead of accusing me / get the facts!” and “@ZachNelson @NetSuite @TribeHR or use your new online billing / subscription system with online payment for your own business! Free advice!”

A basic email to our account rep, who by the way has been more than easy to work with, by Zach would find out that we are trying to pay for services and have been shut down twice because of NetSuite having old information and are still waiting for a payment link. Not one to get falsely roasted on Twitter, I responded, “When did CEO of your SaaS provider trying to falsely roast you on Twitter become customer best practice? Ask @netsuite @ZachNelson #FAIL.” I expected it would be obvious that roasting a customer and industry analyst was not necessary when a simple response to request a call or direct message on Twitter could resolve it. But Zach responded on Twitter, “If sending 4 email notices between December and April is considered ‘No Notice’ then the answer would be yes,” which is a response to my asking, “Do you turn off your customers with no notice?” These were my next responses to Zach: “not difficult to see your org/process made mistakes multiple times - I signed agmt & waiting for invoice” and “an apology is easy to give a customer/analyst on your mistakes not mine if you looked at what happened.” and “been a happy customer of TribeHR and supporter of your efforts! Not sure dishing on me makes any sense!” and “@ZachNelson and for the record, been a fan of @TribeHR read  https://marksmith.ventanaresearch.com/2012/11/15/building-your-workforce-into-a-strong-tribe/ … then became a customer & reference - ask @josephfung.” This turned into a late-night rant because I was concerned that our instance would be turned off again. And all of this for invoices that do not add up to more than $500 USD.

As an industry analyst and chief research officer covering the spectrum of applications, tools and technology for business (and the overall top-ranked enterprise software analyst in 2011), I was hoping for more courtesy in these communications. We do get much communications from analyst relations like we get from other vendors to help us recommend NetSuite unless we diligently pursue it. I noted in listening to the keynotes from NetSuite SuiteWorld16 along with announcements about new offerings like SuiteBilling, which it announced on May 17 and demonstrated, that if it is as advertised, it should resolve such issues as billing and payment for subscriptions. NetSuite could even embed this system directly into TribeHR or provide it to customers through a secure login. If NetSuite is using its billing applications for subscriptions it should process bounced emails and develop professional business communications to effectively engage with customers. Any of these is a better approach than emailing PDFs to customers –manually sending invoices is a worst practice. As we have written, the subscriber experience impacts recurring revenue. It is amazing that NetSuite’s people cannot even look up customer information in the system it rents to customers and doesn’t bother to go to the customer’s website and call them if they can’t get information from their own system. Instead its CEO roasts the CEO of their customer and head of an industry analyst firm that recommends NetSuite on Twitter without proper investigation. Let me just say that it does not take long for bad customer experiences to impact future business, as word travels fast today.

If NetSuite is in the business of serving small businesses, which was the backbone of its growth, then it should know that asking them to print and mail checks for a low monthly subscription of less than $200 is not a best practice and impacts their efficiency. Asking small businesses to wire money is worse because as anyone knows it could cost a small business $15 or more, which is 5 to 10 percent of this invoice and amounts to a penalty to the customer. Software companies like NetSuite should progress like those in other industries that service small businesses, such as healthcare, insurance and other recurring payments; they allow a customer to use ACH for recurring invoices and eliminate manual or costly methods for payment especially if you do not allow credit card payments online. Also, applications like NetSuite should have accounting and billing contact information so that the information is updated by the customer and easy to access and email or even make a phone call. Also, any issues related to the use of the software should be notified to the administrator or in this case also the head of human resources. Since the business is renting the software, the courtesy of contacting them is an industry best practice. These are my recommendations for NetSuite and any software-as-a-service provider, including Salesforce, for which I also provided recommendations in its communications and the billing and payment processes.

We at Ventana Research know that recurring revenue challenges finance, accounting and billing departments as we have written, and that it is easy to say that you should use the software you sell for your own business. We understand that engagement throughout the customer life cycle is the largest recurring revenue challenge in 55 percent of organizations, according to our recurring revenue research. As a negative, example as administrator of our TribeHR instance I have not received updates on the direction of the application. This is a concern for us when we hear the loud partnering communications from NetSuite about a competitive approach from UltimateHCM and are not clear on the future of TribeHR. Our research also finds that payment processing and account management are two of the top five capabilities desired by organizations for a recurring revenue system. In addition our research finds that customer renewals are the largest expected recurring revenue challenge. So we have empathy for NetSuite in this situation. Our research and clients show that improving communications in the billing and payment cycle along with the operation and improvements to the software are essential for long-term success and to customer retention. This improvement is part of what we have articulated is critical for customer experience in 2016 using digital technologies.

The customer experience I have described suggests many areas in which NetSuite needs to improve its communications, contracts, billing and payment processes. Right now it is not so sweet for customers of NetSuite, and its leaders should take to understand the issues in its communications and customer processes to ensure that situations like ours don’t happen again. NetSuite has been operating since 1998 and providing applications in what is known now as cloud computing and should have these processes well defined and refined. TribeHR was acquired in 2013 and by this time should be better integrated as a business and technology into NetSuite and its customer relationship processes so there should be no excuse for what our organization has experienced. We suggest that other small or midsize businesses should re-evaluate any further use of NetSuite and place on hold any evaluation of NetSuite until the company improves its customer and subscriber experience and communications.

No one is perfect, including our company, but I am standing by for a public apology for the clear mistreatment and abuse from CEO Zach Nelson and NetSuite. He could have passed this issue down to the customer service team (and hopefully customer success team) to resolve. Remember our organization was not the cause of this bad customer experience and lack of customer relationship processes. As you see I have documented the experience well, and those who want to see what not to do, just contact me.

Regards,

Mark Smith

CEO and Chief Research Officer