Just recently reached out to Kam, founder of Papercups, on LinkedIn as I had read his article about them going through YC. I wanted to know more about people's experiences with remote YC batches, and Kam responded very quickly and set up a call with no hesitation.
If you're looking for great chat solutions made by great people, check this out :)
Funny thing is, Chatwoot did their HN launch just 2 days ago [1], so I’m curious to see a head-to-head comparison between Papercups and Chatwoot, two nice-looking chat products that happen to be open source.
To reiterate some of the differences, or why people might choose us at the moment:
- A lot of our users really like our Slack integration. For small teams, this means they don't even really have to use our dashboard if they don't want to, because they can do everything from Slack. [0]
- We offer a live screen sharing feature [1]
- We're working on a library to offer complete customization of the chat UI on your website [2]
This makes me wonder if website chat could be implemented by connecting user directly to Slack or other messaging service of your choice and skipping the "admin panel" part?
Yup! To be honest, a lot of the smaller teams using Papercups with our Slack integration rarely need to interact with the admin dashboard if they don't want to. (But it turns out that having a dashboard to manage unresolved questions, add private notes/labels/tags to customers/conversations, etc. is still pretty helpful)
Switched to Papercups from Drift a few months ago. Really like how dead-simple it is and the fact that we can reply and resolve customer threads right in Slack.
One downside of Discord is that we use threads in Slack to manage conversations, and I don't think Discord has great support for threading. But I know some solutions have worked around this by spinning up a new channel for every new conversation... still need to figure out the ideal UX.
You're not, slack is bad. Google chat is surprisingly good but light on integrations. We tried discord but it's a little too childish. The push to talk is amazing for engineering teams though.
questions I had when looking at home and features page..
Is it encrypted? in transit? data at rest?
I see 'enterprise option' for self clouding - guessing this means data is sent to third parties - is that hosted in the USA?
Really like the screensharing bit - is this share either screen? (site admins and or site visitor?)
- is that encrypted? Is that (or any info) stored? (by site owner or and third parties ie papercups.co
We use https so its encrypted at transit. We host with heroku and fly.io. So we use their encryption policy for our cloud solution.
We have papercups-eu.io which is hosted in Frankfurt and is encrypted at rest.
For those who are more privacy contentious we have a self hosted solution. Where we collect logs and anonymized data to make our product better and debugging purposes.
35 comments
[ 2.1 ms ] story [ 85.3 ms ] threadhttps://github.com/papercups-io/papercups/wiki/Features
In the meantime, here are some screenshots from our GitHub wiki: https://github.com/papercups-io/papercups/wiki/Features
And our demo page: https://app.papercups.io/demo
Just recently reached out to Kam, founder of Papercups, on LinkedIn as I had read his article about them going through YC. I wanted to know more about people's experiences with remote YC batches, and Kam responded very quickly and set up a call with no hesitation.
If you're looking for great chat solutions made by great people, check this out :)
1: https://news.ycombinator.com/item?id=26501527
To reiterate some of the differences, or why people might choose us at the moment:
- A lot of our users really like our Slack integration. For small teams, this means they don't even really have to use our dashboard if they don't want to, because they can do everything from Slack. [0]
- We offer a live screen sharing feature [1]
- We're working on a library to offer complete customization of the chat UI on your website [2]
[0] (We need to set up a better recent demo video of our Slack integration, but if you skim our changelog you'll probably get the gist: https://github.com/papercups-io/papercups/blob/master/CHANGE...)
[1] https://storytime.papercups.io/
[2] https://github.com/papercups-io/chat-builder
https://chatlio.com/
Creates a short-lived channel per chat. It works well in terms of sharing responsibilities with a team and allowing people to jump in easily.
I did feel a bit of unease with having customers in the same place as our "private" conversations.
We ship a web-embeddable Matrix client. The users' browser connects directly with a Matrix server of their choice (or a default one).
[1]: https://cactus.chat
and auto-prune to delete all messages after X number of hours - a new project could happen quickly with this.
[0] https://docs.papercups.io/api-endpoints
[1] https://docs.papercups.io/webhook-events
One downside of Discord is that we use threads in Slack to manage conversations, and I don't think Discord has great support for threading. But I know some solutions have worked around this by spinning up a new channel for every new conversation... still need to figure out the ideal UX.
Is it encrypted? in transit? data at rest?
I see 'enterprise option' for self clouding - guessing this means data is sent to third parties - is that hosted in the USA?
Really like the screensharing bit - is this share either screen? (site admins and or site visitor?) - is that encrypted? Is that (or any info) stored? (by site owner or and third parties ie papercups.co
We have papercups-eu.io which is hosted in Frankfurt and is encrypted at rest.
For those who are more privacy contentious we have a self hosted solution. Where we collect logs and anonymized data to make our product better and debugging purposes.