The title is a bit misleading, It's not fully open source. There is an enterprise folder which you can't use without a subscription. And its not clear which Features are OSS and which are source-available. As for tips for the product, think about supporting the Matrix Protocol, which has many social media bridges, other than that it looks good.
Show HN: Open-Source Intercom with Help Center
11–20 of 27 posts
Re: Show HN: Open-Source Intercom with Help Center
#12What do people here use to keep customer information in sync between their customer support crm, and their db for example? What's the common solution to "Customer updated their name => Have to update their info on stripe, chatwoot, and six more places"? Other than "Update everything for every single api call"…
Re: Show HN: Open-Source Intercom with Help Center
#13The title is a bit misleading, It's not fully open source. There is an enterprise folder which you can't use without a subscription. And its not clear which Features are OSS and which are source-available. As for tips for the product, think about supporting the Matrix Protocol, which has many social media bridges, other than that it looks good.
Can someone familiar with chatwoot help answer what features are locked behind a subscription if any?
Re: Show HN: Open-Source Intercom with Help Center
#14The title is a bit misleading, It's not fully open source. There is an enterprise folder which you can't use without a subscription. And its not clear which Features are OSS and which are source-available. As for tips for the product, think about supporting the Matrix Protocol, which has many social media bridges, other than that it looks good.
Re: Show HN: Open-Source Intercom with Help Center
#15What do people here use to keep customer information in sync between their customer support crm, and their db for example? What's the common solution to "Customer updated their name => Have to update their info on stripe, chatwoot, and six more places"? Other than "Update everything for every single api call"…
Re: Show HN: Open-Source Intercom with Help Center
#16We switched from Front to Chatwoot 3 months ago, self hosted on our infrastructure.There are some rough edges, and integrating Facebook and Instagram channels are a bit of work but it's globally working very well. And we save quite a buck every month in our scenario managing 5 brands and 4 channels per brand. Main issues are: mobile app can be improved and browser notifications are inconsistent. Wishlist: a desktop a…
The FB/Instagram channels are a pain to manage (even for us) due to the app review cycle. This is a common problem in the community. Recently we have seen many rejections in Instagram API reviews without a specific reason. Some of the alternatives the Meta developer review team suggests are also not working. We are trying to make this flow better using a hosted app or something. Open to ideas here.
We are aware of the issues with the mobile app. It is getting a revamp now, hope most of the issues are resolved by it.
Re: Show HN: Open-Source Intercom with Help Center
#17I love the website. I'm an intercom user but I'd love to move away from it. I don't use it for the chat, and use it more for onboarding emails, user views, and walkthroughs - does chatwoot plan to offer these in the future?
Re: Show HN: Open-Source Intercom with Help Center
#18Apart from rent and salaries, customer chat is our single biggest expense (at very low volume usage, it not being our core business at all). Chatwoot is making it very awkward for the industry and I am glad they do.
Re: Show HN: Open-Source Intercom with Help Center
#19The title is a bit misleading, It's not fully open source. There is an enterprise folder which you can't use without a subscription. And its not clear which Features are OSS and which are source-available. As for tips for the product, think about supporting the Matrix Protocol, which has many social media bridges, other than that it looks good.
I sure hope that many more chat/customer-messaging-adjacent platforms begin to adopt matrix protocol support underneath! So many services exist on top of email/smtp protocols, and that has allowed for such creativity...It boggles my mind that the same has not been done for chat (or at least chat for customer support) - it seems like we have so many competing, proprietary chat protocols for these types of use-cases! As a customer, i don't want to have my interactins trapped only in the provider's platform...Just like email, i want to keep a record of my interactions with customer support...and leveraging a shared, universal set of protocols would help in that regard. I'm an admitted matrix fanboy, so that's my preference, but even xmpp or seomthing like that should universally be adopted!