It's cute with Less Accounting, because obviously accounting is necessary and you could never get rid of it all (or want to). But it's not cute with neglect. Neglect is not a business necessity, and "Less Neglect" just reminds me of all the neglect your app probably won't address.
The name is a downer.
"Neglect is a passive form of abuse in which a perpetrator is responsible to provide care for a victim who is unable to care for himself or herself, but fails to provide adequate care." ~Wikipedia
We use TestFlight a lot in our iOS apps. TestFlight is great for tracking what your users are doing inside your app, and logging errors. LessNeglect goes a step further and lets you tie users and actions together with an open communication channel.
I'm going to use this specifically to allow users of my iOS apps to send me support requests, and to also track in-app purchases.
After looking at the screenshots, I had a better idea. From my understanding, it's a feed of the actions happening on your website. So, rather than having a "Facebook feed of latest news from your friends", you have a "Feed of latest actions on your website".
Again, from my understanding, the way it works is by providing an API to the developers. Basically, for every actions on my website, I'd send an API call to lessneglect.
I think I like it.. mostly because I find it's very hard to follow my users across my websites to know what's happening. I use external tools such as Google analytic and mixpanel.. but even then, it's more of a "stats" page than a real feed of what's happening.
I think the homepage has some cool UI effect but the important messaging is missing. I'd cut the "Turn upside-down" or "Less Neglect is web software that takes the job of supporting customers to the next level.".
Sounds like you've groked the big concept, but we'd love it if people didn't have to ponder over it before understanding what it is. Thanks for taking the time.
I don't understand the customer support aspect of the tool beyond offering a customer view and messaging. The video demo glosses over what a customer support issue would look like since the person had already figured out the problem by the time Support could respond. Can you offer a demonstration of what an exchange might look like if support was needed?
Also, your use of the word "proactive" made me think that the tool helps anticipate problems. Every example demonstrated reaction(sending emails after a sign-up or payment event). Even your Crewpedia case study was a reactive example because support had to respond and make changes to the UI based on how people were using the page. Can you offer some examples of how the tool allowed users to expect an event? Otherwise, I suggest using a different word such as "insightful" or "contextual".
The concept of proactive (as it exists in our beta) is more in the sense of "fix their problem before they have to ask you to fix it". But our goal is absolutely to help you to "fix their problem before they know they have a problem".
We've been able to do that to a certain extent with FolioHD customers manually by seeing patterns in their usage where we can suggest an optimization.
We see a user uploading images one by one and can shoot them a message saying: "hey john, did you know that you can select all your images at once when you're uploading? save some time!"
or, we see someone uploading custom images to use for their homepage slideshow that are branded with logos that don't look great in their portfolio proper, so we can reach out and say "hey jamie - did you know you can create a separate gallery for your homepage features and then hide it so it doesn't show up inside your portfolio?"
So this is what we mean when we say "proactive". When we see one or two people having problems, we can help them out to best use our product. And if we see a lot of people missing key features, we know that we need some UX work.
It's been pretty great, and that's why we figured we should polish it up and release it for other people to use.
I would recommend a JS API to reduce barriers to entry.
Even better if it can install a little widget on my site that allows the user to ask a question or view their past conversations, a la intercom.io.
We need to put a lot more work into the onboarding process (we created the whole public site and api docs and demo wizard over the weekend) so if you have any good examples of "getting started" flows that make sense, please send them my way.
Developers who get it are immediately delighted so you create a positive experience from the start for your first users and naturally limit the early access to people who can actually start pushing data to your service themselves.
Yes, please steal it. We debated whether it would be a good idea to do API-only registration, but the response so far has been mostly really positive.
As far as pricing and details, if you can shoot us an email, we can chat offline and see if we can come up with something reasonable. support at lessneglect.com
I'm, however, a bit surprised that you used real user data in the demo. I don't know exactly how FolioHD works, and I don't know if the data we see in the demo are already public, but it kind of made me tick.
I have already sent events but the dashboard insists on always showing me the wizard (and i have to click close wizard)
Also once you are logged in, how do you get to the API docs?
The main site insists on redirecting you to your dashboard if you are logged in.
Lastly, I seem to be getting some server 500 errors on some ajax requests. please see your support email.
Just what i've been looking for my 4k to 5k daily users ~30k monthlies users