We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
User story for 8(b) on dev roadmap, re: follow-up emails.
Let's say a registered user has published a new Q. The app should immediately follow-up with an email saying, roughly ::
Thank you for posting your question to AskThem - here's a permalink to your question, which you can share over email and social media:
[link]
... remember to circulate your question to reach the signature threshold, and we'll help you push for a public response.
For more info about how to gather support for your question, please visit our FAQ:
Thank you,
[contact info]
... then in the future, we'll want to have another follow-up prompt as Change and others do, but this is sufficient for now.
The text was updated successfully, but these errors were encountered:
I'm happy to edit this copy in a file anywhere on the app you recommend - of course I can finalize that if you point me to the right place.
Sorry, something went wrong.
derekeder
Successfully merging a pull request may close this issue.
User story for 8(b) on dev roadmap, re: follow-up emails.
Let's say a registered user has published a new Q. The app should immediately follow-up with an email saying, roughly ::
Thank you for posting your question to AskThem - here's a permalink to your question, which you can share over email and social media:
[link]
... remember to circulate your question to reach the signature threshold, and we'll help you push for a public response.
For more info about how to gather support for your question, please visit our FAQ:
[link]
Thank you,
[contact info]
... then in the future, we'll want to have another follow-up prompt as Change and others do, but this is sufficient for now.
The text was updated successfully, but these errors were encountered: