Super pumped to be officially launching our community this coming Monday, along with some other cool features at Tiller. https://community.tillerhq.com
Right now, we use Intercom to handle all support inquiries. Weāre getting burned out on the one to one model because we get a lot of the same questions and having folks post them to a community where we (and our enthusiastic customers) answer them gives a one to many benefit. So weāve ramped it up, and weāre seeding content. Itāll be a slow to build we know, and Mondayās launch is really just adding it to the onboarding for new customers. We expect to learn a lot and continue refining.
We hope to use it to answer questions about our suite Google finance spreadsheet templates (which are transitioning to our āplayground brandā Tiller Labs) and discussions for recommended workflows that donāt fit the box of the templates as theyāre built.
We think our product is perfect for a community because itās collaborative and great for tinkerers (the sky is the limit with a spreadsheet, right? )
So, finally, to my question, how would you recommend we handle the flow of new topics and replies happening in the community and work that into our existing support workflows?
The replies from topics donāt make it into Intercom because of their automated flagging mechanisms (we were hoping to have those funnel into a special team inbox so none slip through the cracks). We donāt field support directly out of our email inboxes and we like having a queue based system to make sure we donāt miss inquiries.
Some ideas:
Set aside a specific block of time each day to participate in the community and do this in shifts across all our support staff (but how can I be sure Iāve read and responded to everything and then how does my teammate efficiently know what Iāve already addressed?)
Divvy up categories/sub-categories to a specific teammate by day (I handle template questions on Mon, Wed, Fri) during my scheduled block
Something else entirely?
Ideally, we want this to make us more efficient and Intercom isnāt going away. Instead weāll use it primarily to address core product questions/issues like bank data feed connections that might have sensitive data users donāt want to share in the community.
Yes, my team is primarily responsible for support. Yes it is an additional channel where we hope customers will post and answer questions related to recommended workflows + advanced how toās that we typically answer via 1:1 channel (Intercom).
Yes, our whole company is bought in and fully backing the community!
In my experience the key is flexibility. There isnāt really a one-size-fits-all answer. You might find that some people have a natural affinity towards the community while others donāt enjoy it as much. If thatās the case, Iād consider a division of labour.
If everyone (or no one) loves it then blocks of time is a good option. A category split works well if you have subject matter experts but otherwise it doesnāt necessarily equal a fair balance of workload because some categories will naturally be more busy than others.
If it were me Iād start with scheduled half day blocks and then revisit at the end of the first week to see how thatās working for everyone. Assuming youāll be responding publicly onsite itāll be easy to see which questions remain unanswered.
Thanks for the feedback here @HAWK. Things are going pretty well so far and itās rolling along and growing pretty organically.
Itās still slow enough right now that I can pretty much stay on top of the new discussions and we have some engaged customers who are also helping answer questions. Just what we wanted, and weāre loving it!
One challenge we foresee in the future when the volume is a lot higher (and are already seeing a little), is that we havenāt figured out a really efficient way to know whatās not been addressed either by another community member or a co-worker. So when I log in during my āblockā of time how do I quickly know what needs my attention without scanning to see ādoes this one have a reply?ā āis there only one profile icon next to a post?ā and then after I address what I can during my block, how will my co-worker know whatās not been addressed when she comes online. It seems that whatever is flagged as āunreadā or ānewā for me wonāt appear as such for her.
Any ideas on a workflow to help manage that since weād like to use our individual accounts vs a shared account?
I definitely support the approach of using individual accounts but Iād recommend waiting to see if this will actually become a problem. We have a very busy support community here (and a team of 36 who are all tasked with responding to questions) and we havenāt yet found this to be a blocker.
We are experimenting with a āsomeone has read thisā indicator for PMs (which is another support channel that we use) which might be able to be extended to public topics in the future if enough people need it.
Thanks for the reply. Within your team of 36 how do you manage to know what hasnāt been addressed by someone else on the team? Is it strictly looking within the Discourse community itself and certain folks are responsible for specific categories or is it a free for all?
Iāve found that sorting on number of replies lets me know when someoneās topic hasnāt received a response yet, but this is not a very efficient workflow and I have to do it for each category because we have our home page organized by category vs all posts by ālatestā like the meta forum here.
Itās a free for all. There are generally three statuses ā a question has been answered (no action needed), a question hasnāt been answered (action needed) or a question has whispers discussing the best course of action.
You donāt have to have that as your own homepage though. You can have latest.
How can you tell which is which is what Iām asking. There is no obvious or efficient way (as far as I can tell) to see which ones have been answered, not answered, and which have whispers (though we donāt have whispers turned on right now).
Maybe this is something weāll try in the future, but have tried to organize around a ājobs to be doneā concept. What is the user trying to do when they land on the forumā¦ and make sure they can explore/find the appropriate content based on their job vs needing to see a thread of whatās got a big flurry of activity.
You could mark the ones answered as āSolvedā if the answer given is final. But I do see what you meanā¦ a sort of ticket system like:
Open - not answered
Pending - answered but still pending
Closed - answered sufficiently and closed.
The āTicket termsā are subject to whatever words you want to use. Is this more of what you are looking for? And to have an icon represent each type?
You can get all unanswered posts for a topic list by adding ?max_posts=1 to the URL in your browserās address bar. There is a theme component that you can install on your site that adds an āUnansweredā button to the siteās navigation: Unanswered Filter.
If you would like to find only topics that have not been answered by staff members, but may have been answered by other members of your community, you could add a Data Explorer query to your site that returns a list of those topics. It is now possible to allow groups to run Data Explorer queries, so you could add the query to your support group page.
A good approach for dividing support work among a team is to have members of the team watch the categories or topics that they are comfortable answering questions in. For example, I watch our wordpress category, because I donāt expect any other members of the team to answer WordPress related questions.
The Assign Plugin is very useful for dividing up work among a team. We make a lot of use of it on Meta, especially in the bug category.
A lot of the support work we do at Discourse is handled with PMs that are emailed to our support team. We use group PM inboxes to know what needs to be dealt with. PMs that have been handled get archived. We also use the Assign Plugin to assign PMs to team members. We have enabled the āOn group messages publish group read stateā setting for our Support group. With this setting enabled, we can know which team members have read a PM.
Whispers can be useful for support work if there is a need for internal discussion before answering a question. They can also be used to let other staff members know that a support request is being handled.
Thanks so much! This is great feedback on how to use Discourse for support.
Iām experimenting with the āunanswered filterā right now. Thanks for sharing that component with me. Is it possible to further filter the list to exclude a specific tag in the results?
We use Discourse for documentation too and we donāt necessarily expect those topics to need a reply. Iām guessing the ?max_posts=1 is just filtering the latest list based on number of replies?
Either way this will help! Iāll also share your other feedback with our team as we continue refining our process.
I donāt think this can be done with the unanswered filter, but it can be done from your siteās advanced search page. The āWhere topicsā section of the search filters has a āzero repliesā option. Select that option, and then add -tags:tag-name to the search bar exclude a specific tag from the results. Hereās an example search query that will return topics with no replies, but exclude topics tagged with feature: Search results for 'status:noreplies -tags:feature' - Discourse Meta.
Another approach to this would be to add a Data Explorer query to your site that gives you the results youāre looking for. It is now possible to allow groups to run Data Explorer queries, so this could be a good solution for a group that is responsible for customer support.
Yes, this can be done with Tag Groups. To create a tag group, go to your tags index page (/tags). Choose āManage Tag Groupsā from the top right menu.
Create a new tag group with the tags you want to restrict to staff members. Tag groups give you three options for how the tags can be used:
Tags can be used by everyone
Tags are visible to everyone, but only staff can use them
Tags are visible only to staff
Select the last option so that the tags can only be used and seen by staff.
all!
)
