Separating end-user community content


3 댓글

  • Nicole Saunders
    Zendesk Community Team

    Hi Joelle - 

    When you say different queues, are you talking about on the UI side within your community or something else? 

    Internally, what we did is create a Gmail address that we subscribed to everything in the Community. Then we use their labels and filtering system to sort out the notifications from new posts and comments that need to go to different teams, and that helps us sort out the moderation of topics managed by different groups. 

  • Joelle Waksman

    Hi Nicole -

    I'm referring to the admin side of things under the "moderate content" section within the community. It sounds like your idea is on the same path, but seems like not the ideal scenario. Especially because, at least in my experience, you don't get notifications until a comment/topic is posted, and we are currently approving/denying content first. 

    Here's what we are trying to do:

    Within our community we have multiple topics, one of which is our Idea Portal. The idea portal is currently managed by our UX team and we'd like to keep it that way. However, the other topics and other posts ideally can be managed by our CS team. Instead of just scrolling through each post and seeing if it's under "ideas" or not, I would be great if we could separate the content that needs to be moderated by topic. Even with a label or something.

    Your email idea may work. Are there any other options?

  • Jessie Schutz
    Zendesk team member

    Hey Joelle!

    Unfortunately the platform capabilities here are pretty limited. The only other thing I can think of is, if you're on one of the Guide and Support plan combinations that support it, you could create the Idea Portal as a separate brand with a separate Help Center. That way the moderated content for each Help Center would appear in the moderation queue where it was posted.

    I'm sorry we don't have any better solutions for you!


게시물 댓글 달기가 중지되었습니다.

Zendesk 제공