taaron

9 ms·

31.
by taaron 5y ago
I actually think this was a big reason why we did a landing page chatbot - because everyone else had one. The original scope was just a chatbot for support, but the logic was heck we were paying for it so why not use it in more places.
32.
by taaron 5y ago
Interesting way to put it. I guess the funny thing is as a consumer, I do personally dislike chatbots beyond direct support (simply because it beats long-chain emails back and forth).
33.
by taaron 5y ago
Random sales rep is a great analogy...and I suspect that was why so many people found our chatbot annoying.
34.
by taaron 5y ago
Yep, ours was intercom but the other common ones are drift, hubspot, freshchat. Seems like these have spread everywhere in the past few years to the point where every website has one.
35.
by taaron 5y ago
Hmm, I guess (a) was redundant because it could have been (and is a link). (b) and (c) trigger a specific funnel that assigns that message to someone in our team, so those had to be triggered from the bot. (d) is just a nice way of saying &
36.
by taaron 5y ago
True. That Amazon chatbot is a whole different league in terms of intelligence than any of the out-of-the-box chatbots from intercom etc though.
37.
by taaron 5y ago
It asked whether you wanted to: (a) Wanted access to Workflow86 (our product) (b) Chat with sales (c) Chat with support (d) Just browsing and each of these options then funneled into another action or question e.g. assigning it to a human,
38.
Ask HN: Does Everyone Hate Chatbots?
24 points by taaron 5y ago|45 comments
39.
by taaron 5y ago
Sure, by "operations" we essentially mean a collection of processes which governs the right way to do something. It could be, for example, the steps you want a developer to take when making a pull request, or how a reported bug or
40.
by taaron 5y ago
Thank you! Really interesting point re the "data middle ground". I guess the problem has always been with the "spokes" to connect that data middle ground/"hub" to other apps. This has either required pre-b
41.
by taaron 5y ago
Let us know how you go! We are happy to offer the full white glove treatment for our early users. If you need a feature, we work hard to turn it around for you :)
42.
by taaron 5y ago
Pretty different to Zapier. I'd say Zapier is very focused on piping data between different apps and tools, and is fantastic for establishing those connections. Our focus is on consolidating and running as much of the core operations a
43.
by taaron 5y ago
On prem isn't a standard feature, but it is something we can work out on a case by case basis. Will check out your tip on "orchestration" contracts, thanks!
44.
by taaron 5y ago
Fixed! Our apologies - we did not foresee this much traffic from this post, so it got hugged to death for a while.
45.
by taaron 5y ago
Nope, built ourselves and no relation to n8n :) Like n8n the focus is a visual builder where you drag, drop and connect modules together. n8n has more of a focus on integrations/piping data between different external SaaS tools. Our fo
46.
by taaron 5y ago
100% agree, there is a certain mindset required to go from "stuff I do everyday" into a structured process. We've found it sometimes takes a bit of pre-work, like mapping the basic process on paper or a whiteboard, to smooth
47.
by taaron 5y ago
A few others in this space include Process Street and Piepfy. I am biased, but I do think we have them beat for functionality and pricing though. Give them a go, give us a go, let us know what you think!
48.
by taaron 5y ago
Yes, large and established enterprise is a tough one to crack. As a consultant, I've seen teams still running Lotus Notes (!).
49.
by taaron 5y ago
We've actually had this exact discussion - based on feedback, we might switch over from "else then" to "otherwise" very soon.
50.
by taaron 5y ago
"the first thing I looked for in the docs was authorisation controls/checkpoints." We've got a component called the Assign Task that was pretty much built for this - its pretty flexible, but it is mainly used to create a
51.
by taaron 5y ago
Shoot us a message if we can help in any way! Happy to build out a sample workflow or proof of concept, all we need is a description of what is involved in a process of your choice.
52.
by taaron 5y ago
Not as a standard feature, but it is something we can do on a case by case basis. Happy to chat further about this, just shoot us a message!
53.
by taaron 5y ago
Right now our main point of difference is consolidation. We allow users to build and manage more of their workflow with just one platform vs duct-taping together 6 different SaaS tools like you would in Integromat. Our thesis is that it is
54.
by taaron 5y ago
It absolutely does make sense, I was actually in corporate law before consulting! "does this product incorporate any sort of digital signature / approval process?" We have a component dedicated to building out approval steps
55.
by taaron 5y ago
Thanks for the heads up! Just fixed.
56.
by taaron 5y ago
Thank you! 100% agree. The amount of operational expertise and knowledge held by non-technical people is massive. Empower the individual to unlock, capture and scale their expertise as software and you really do get true digital transformat
57.
by taaron 5y ago
Our bad! Currently stripping back the chat bot messages as we speak.
58.
by taaron 5y ago
Thank you! There are still some things that need some more smoothing out, so let us know if you hit any rough patches. Also feel free to shoot us a message if you need any help (on-boarding, tips, build a process for you, whatever). We shou
59.
by taaron 5y ago
Thank you! Currently it is +$7 per user seat per month BUT we are reviewing our user seat pricing. Based on feedback, we'll likely separate out pricing based on user role i.e. a per editor/admin/builder user seat price and a
60.
by taaron 5y ago
Workflow86 was built based on my experience as a consultant and then running ops in my own start-up. All teams develop specific ways of doing things - how they handle pull requests, respond to incidents, handle bugs, hire new employees etc.

More ›