- Took me under 5 mins to sign up and have this running on our entire site. They use a good CDN, because adding it to our site has had no noticeable increase in page load times.
- Highly accessible. Chatlio leverages all of the notification features built into slack. I couldn't ask for more. Our entire team had access when it was set up, without needing to create new accounts, or log into another site on yet another Chrome tab.
- Great customizations. Check their site for full details, but coloring, language, and contextual stuff (what to say when there is no attendant, etc) is super easy to work with.
- John (the lead at Chatlio, I believe) has been nothing but helpful. When I asked for help making the chat appear on a 10 second time delay, he had the code back to me in less than 20 mins. I was impressed.
- They are already making great updates. They recently launched a 'take screenshot' feature, message editing, and have reporting and operator rating features in the pipeline.
My company struggled with implementing and making a profit center out of live chat functionality. Chatlio has been fantastic. Its worth every penny.
If you want to see a live implementation, ours is here: http://sequoiawaste.com. I'll be hanging out chatting with people who are interested for the next hour or so.
A non-Slack alternative: I was looking for this feature, but wanted to move my company away from Slack to one of the free chat platforms like Rocket.Chat, Mattermost, Zulip, etc. So I researched, and found that only Rocket.Chat has its own version of this live-chat feature (though no doubt much less mature). I'm looking forward to switching over to Rocket.Chat soon (I have no affiliation with them).
Hope this helps folks out there looking for live-chat integration options. It's pretty cool to be able to chat with potential users directly from company chat!
I don't mean this as a dismissal in any way--if this works as advertised I'd much rather show this product to a client than have them goad their developers into trying to build and maintain a feature spec'ed on a (to them) random person's tweet.
But in all seriousness, before you install a Slack App, make sure to verify how much permissions they request. We at Chatlio strive for asking for as little permission as possible. If some feature requires more, we ask for that on an as-needed basis after signup.
If you're creating an entirely new channel and archiving it every time, does that mean my archived channels list will be full of potentially thousands of channels? Ignoring that I'll struggle to find channels I may want to revive (we archive channels a lot here), will Slack cope well with this? (We've seen what happens if they have over a certain user count.. so I'd be worried what would happen here.) Is it possible to entirely wipe a channel after a certain period of time rather than archive?
Update: OK, I'm an idiot. I just realized I could spin up a second free Slack account just for this use..
I run this small email-helpdesk<-->Trello app  and I thought I was the only one trying to come up with the best ways to map features from what Trello has builtin to what my app needs.
Users sometimes find it awkward, but in the end it works very well.
DISCLOSURE: I work at Chatlio
EDIT Slack has some recommendations on this: https://get.slack.help/hc/en-us/articles/208492868-Making-vo...
The chat box submits to a lambda which puts the message on SQS. App consumes sqs and puts in DB (for durable storage) and posts to slack room. Responses are then sent via pusher back to the chat box (a react component)
Is anyone aware of something like this being available for commenting services like Disqus which are used on blogs? It would be nice to manage replies through Slack, as a lot of time is already spent there.