meltano: Give `http://melta.no` troubleshooting help link when plugin fails, with CTA to Slack in web copy
Spec (edited by AJ):
When Meltano fails, we’ll print a standard error message:
[Error description text.]
To contact the Meltano team and access troubleshooting help and resources, visit http://melta.no
Orig. issue description (Douwe)
When meltano invoke or meltano run fails, a user is more likely to manage to solve the issue and stick with Meltano if they join Slack than if they don’t, as evidenced by the number of people who responded to the survey saying the docs weren’t always helpful, but the Slack community was. I imagine a good amount of people that try us out and churn would not have if they had known about Slack. That also lets us reach out to them to learn more about their use case and experience, even if they do end up churning.
So I think we should recommend joining Slack in the product wherever that makes sense.
@tayloramurphy Wdyt? Seems like an easy change with potentially large impact.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 16 (8 by maintainers)
I’ve just updated the melta.no forwarding to go to https://docs.meltano.com/guide/troubleshooting
@aaronsteers that spec looks good to me 👍
@aaronsteers yeah, that’s something we need anyway
I think the fastest and clearest way, without creating tech debt is to create
docs.meltano.com/get-helpordocs.meltano.com/troubleshoot, perhaps as a redirect to something the below:Providing a generic link seems less needing of a way to turn it off - versus a direct Slack CTA which is clearly the wrong CTA if folks are already on Slack or don’t (for whatever reason) want to join. But there on the troubleshooting page, we could optionally tell people how to mute the message.