I'd love to hear Richard Stallman rant about this...he'd probably find a way to articulate, more elegantly, what I'm feeling.
You could read the story behind how we ended up doing that over here
https://www.chatwoot.com/blog/woot-journals-one-year-since-o...
Any plans for that?
But we do have our eyes on marketing use cases(campaigns) in our future roadmap.
Yes, I know Intercom offers the option to seamlessly switch to email, but at that point you could just build a simple 1990's email contact form in a fancy JS popup and it's effectively the same thing.
I understand Intercom made a billion dollar company out of their chat widget because businesses want to look savvy, but that doesn't mean it's actually a good experience for users. As a startup founder myself, I care more about a seamless experience for my customers than for me.
In Chatwoot the channels like email, twitter, Whatsapp etc are also considered primary conversation channels. So its helpful even when your primary support channel isn't chat.
Hosted on Heroku, using Sentry for error tracking, New Relic for performance monitoring, Sendgrid for email. Recently ditched Google Analytics in favor of Plausible for general analytics and Ahoy (Rails middleware) for deeper in-house analytics. Using Intercom for support/chat widget, but planning to switch to Chatwoot. Considering moving off Heroku, but the most obvious contender, Render, doesn't yet have high availability postgres with automatic failover.
Deployment is set up so any push to the master branch on GitHub is automatically deployed to production. Merging to the master branch can only be done via a PR, and needs green status from both linter (Rubocop), tests (Rspec run on CircleCI, both unit and integration) and coverage (100% test coverage required, verified by codecov.io).
UI is Bootstrap (but feeling long in the tooth), and server side rendering with a sprinkling of javascript. Still mulling over hotwire/turbo vs alpine vs stimulus vs react for some upcoming UI that requires more interactivity.