-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Moving Support to In-App #105
Comments
In addition, we can use the data this generates to perform analytics on bug reports/feedback over time by feature area helping us answer whether we are getting better/worse
If we are to continue using it I think there should be clear channels and purposes such as:
It should be super clear that support is in-app and we should also avoid doing support in there at all costs; we've seen that people can (rightly) get frustrated when questions are being answered in there apart from their own which often happens.
This should continue as an option in the help menu, and only bugs/feedback are routed to Zendesk |
If we're announcing this in Slack and people are getting an autoresponse from hey@ I don't think we also need to do this |
All for this, but I don't think this will drive engagement or community by itself. We need a value proposition for why users would want to join the Slack, and a plan of how to deliver that. Each of the above also has it's own, better, more targeted channel for those topics. Community Chat: Squeak |
There are three common interactions we have with customers:
I agree we should make #1 public (so others can benefit from the answers) and #2 and #3 should be somewhere else. And we should make it clear in both places what the purposes are for both forms. Why did we move away from Slack?On Slack, there were a lot of use case questions. We'd answer them, but the threads would quickly disappear because of Slack's data retention limit on free accounts. That's where Squeak! came in. We wanted a way for all of that rich knowledge to live on. Why not Zendesk?There are a few issues: 1. Volume is growing, and we don't have the capacity to respond to everyone individually. This leads to customers feeling like we don't care about them if they're not paying us. Ideally we want every customer to feel valued. What do other companies do?Forums are a common way to make knowledge publicly available and allow power users to jump in and help answer questions (in addition to staff). A great example is Fly.io's community. What makes sense for us?1. Product usage/use case question = public, so this can be indexed, and others can benefit from replies Concerns about Squeak!1. Some questions need context - we're working on that, considering adding Sidecar to the website for our internal users More details about what I'm driving to help improve question asking/answering on posthog.com |
I'm not sure this really answers the question of what's happening with Slack and how/if Squeak will become the community support option? |
If I'm not mistaken Squeak will still be answered/moderated by the PostHog team? Maybe long term we have community engagement there but not yet. |
My suggestion/proposal based on the comments and direction above is that we, over the next few weeks, take the following steps:
I'd appreciate feedback or vocal agreement on this, as it'll obviously be a very visible issue. I'd be happy to handle all comms and site updates to make this happen in an upcoming sprint, though would need help from Team Bandwagoneers (@fuziontech 🤞 ) to make the Welcome Bot changes. |
Going to close this for now, as it's stale and most of the stuff is either done or low prio |
We're changing how support at PostHog works and, as a result, there are a bunch of things which we should either update or discuss. This issue is part checklist to make sure we don't miss anything and part thinkpiece about what the impacts may be.
What's changing?
The rationale for making these changes is that, by funnelling requests through the app, we can more effectively triage them and give users a better experience. We can also better prioritize requests.
What needs to be updated/done?
We need the external/internal linking
capability to merge in, and then update links in a lot of places. This would allow us to have a link which directs support requests into the app, and to the modal.
Potentially, we should archive the existing Community channel and create a new version from scratch, to remove all the support questions from there?
Open questions
There are two big questions which I haven't seen a clear answer proposed for.
What about the Slack?
An obvious side effect of funnelling all user feedback and support requests into the app is that there will be really no reason left for people to use the Slack channel.
One solution is that we doubledown on turning the Slack into our contributor/beta community, so that everyone in a beta is added there and we engage with them there for real-time feedback.
Another opportunity would be to invest in making the Slack a true community and we put together a schedule of community events and opportunities to galvanise this. This would be non-trivial and is something that should be planned in a separate issue.
The final option is that we should simply close the Slack, or not make any further changes. Obviously not a very desirable outcome.
What about Squeak questions?
In addition to the Slack, we also funnel users towards
/questions
to get support.I'm unclear on what the plan is in this regard if, as has been discussed, we want to funnel all bug reports, support requests and product feedback through the app. Are these questions going to remain? Will this be the new 'Community Support' channel? If not, should we remove 'Community Support'?
The text was updated successfully, but these errors were encountered: