Yes, exactly that. What are the best practices for this. If you have examples of the emails, that'd be great! We have a small community and we're not receiving too many accepted solutions. Maybe the system email is not clear enough.
I'd recommend to keep it simple.
Just a title like "Your <CommunityName> post got replies!" and a body like "Hi <Username>, Good news! Helpful members have replied to your post. <Topic> We hope you found their replies helpful. Feel free to post again to continue the discussion. If you got the help you needed, please click on the “Accept as Solution” icon on the post. This helps lets other community members find helpful answers on <CommunityName>. Thanks for joining the discussion!"
Also, the accepted reminder solution alone shouldn't be your only tool in trying to increase the number of posts marked as solutions.
When I started at my previous community, use of the Accepted Solutions was very, very low. This surprised me as it was a support based community, we had strong numbers of superusers and a high percentage of resolved posts. It was clear we had to make Accepted Solutions more prominent.
We used a number of mechanisms to successfully increase the number of Accepted Solutions. Some of them might also work for you. Here's what we did:
- Introduce a much more prominent green tick logo on Accepted Solutions to make them really stand out at browsing level
- List the latest Accepted Solutions prominently on the front page to highlight how many and how often posts were being solved
- Use leaderboards prominently to highlight users who were authoring the most solutions
- Advertise the use of the Accepted Solutions functionality in moderator signatures
- Use the Accepted Solutions reminder email to alert users 7 days after they started a thread that their post had received replies
- Highlight Accepted Solutions in FAQs, welcome posts, help text, weekly community updates, etc
- Educate the moderation team to mark answers as solutions if it was obvious that the user's issue/question had been successfully resolved. Eg they had come back and said "Yes, that's fixed it" but just hadn't click on the Accept as Solution button.
I would recommend considering one additional step to Jason's excellent reply. Because of the value to the community and users to having Accepted Solutions, I would consider using internal resources such as people from support to select a reply as a solution, or even provide a reply, to questions that are getting lots of views. You can easily go into LSI, click on Content, Forums, and then Conversations a bit to the right. If you didn't change the date range or the scope, you are seeing the most viewed Topics across the community, over the last 30 days. For any that are from public forums, these views are likely mostly coming through external search. If they have Solution views in the last column, you are in good shape (although it never hurts to review the solution for accuracy and whether it is still current). But if Solution Views is 0, at least for the top 10, I would strongly consider asking Support or someone with the appropriate expertise to create a reply that contains the solution. These top 10 might also make great content for a blog article, since we know this is the information that users are seeking. Don't be surprised to find that some or many of the top 10 may have been created some time ago. You can also click back on Forums on the left and drill into specific forums, particularly if some are more oriented towards support.
Good stuff @RobbL, I agree.
Community moderators can also certainly mark one of the replies to a message as an Accepted Solution, which can help promote and encourage the use of Accepted Solutions. And your team should definately be striving to provide answers for any questions that don't get a response within your desired timeframe.
I would just note some small amount of caution about marking existing replies as solutions yourselves - you want your team to be sure that the solution has solved the issue to the original poster’s satisfaction. Often users say thank you, that worked, great solution etc in a reply but don't mark it as a solution. In those cases your team should definately do it for them. You might also get them to reply and say something like "you're welcome, and we've taken the liberty of marking the reply as an Accepted Solution so that others can more easily find it." Again, helping to reinforce the importance of using the functionality to everyone.