Skip to main content

Internal Engagement - Strategies for Customer Questions

  • January 21, 2026
  • 1 reply
  • 12 views

atwhite
Forum|alt.badge.img+1

Hoping to open a conversation with this one! 

Our customers love getting answers in our Community; those who post and get a response often report it’s faster than Support. Outside of that, we have a few challenges we’re trying to address:

  • We have a lot of ways for customers to reach us: Community, multiple Support channels, emails to CSMs or Sales team, etc. 
  • For that reason, employees may answer the same question multiple times. 
  • Questions answered in other areas don’t benefit future customers (or employees). 
  • Because of these many channels, employees often disregard the Community. Not only do they see it as a customer-to-customer space, but also as another channel to think about, so they see it as extra work rather than a vehicle for scale that would reduce work over time.

We’re looking this year at ensuring that, regardless of where a question is asked, if it could be applicable to others, the answer ends up in the Community. We’re not sure how to do this, as it represents both a technical challenge (meeting employees in their existing flow of work and finding a way to route existing responses from Support tickets or emails into the Community) and a behavioral challenge (needing to change perceptions of effort and value by employees). 

Hopefully that’s enough context...but I’d love to hear what thoughts others have about this. Have you solved (or at least partially solved) challenges like this? What systems or incentives have you used? How have you kept it simple? 

Thanks in advance!

1 reply

mitchell.gordon

I worked at an organization that community was their support instance. We would focus on awarding the authors of the answers with monthly merch. 

Implemented a support question of the week. You can add to an existing blog location and tag them all and title the posts all the same or a new content location. We utilized this to get answers to commonly asked questions that week. We would meet with support senior to get on the same page for a topic at the start of the week and give them until the end of the week to create the post. Sometimes this was a few lines or a paragraph plus. Tried to keep posts in short snippets. Worked really well and was needed when an AI tool basically took over entry level support. Everything went to a bot chat that indexed community and other locations. If the user wasn’t able to find an answer, they either were prompted to create a post in community or a ticket based on their support level with that org.

 

I worked at another org that hired moderators for their community. They were long standing employees that migrated from support or PM work to help answer full time questions brought up in the community. Very large scale organization and community for this one.