Here are a few guidelines on how to use the create valuable posts, so that others in the Community can effectively use and apply your insights:
Follow the Community Code of Conduct
Feedback and constructive criticism are welcome. Disparaging, harassing, mean, or snarky remarks about Desktop Health, its employees, affiliates, vendors, partners, or other community members will not be tolerated. We’re all friends and professionals, so let’s keep it polite. We don’t like having to remove comments, but we reserve the right to do so without warning in order to maintain a positive community experience for everyone.
If you need support, contact us first!
This forum is for learning and sharing your knowledge with others. If you need help with your printer, prints, software or other service or product from Desktop Health, you should contact Customer Support so they can assist further. If you already have a conversation going with Support, great! Feel free to post about it here, but keep in mind that posting here does not take the place of contacting the appropriate channels.
To get the most out of the Community and your interactions with Support, make sure to read through the relevant sections of the Knowledge Base!
Use the search bar
We maintain a thorough Knowledge Base and there are many other users in the Community, so there's a good chance someone has already made a suggestion or asked a question similar to yours. Keeping conversations in existing threads makes them easier for others to find, and helps keep the Community organized.
Vote for posts and comments that add value
Votes do matter! See a post or comment you like or agree with? Use that up arrow! Feel like making a post that just says "+1"? Please use the upvote button instead. Post a comment to share your thoughts that further the discussion.
Give details, examples, and tell us about the problem you’re trying to solve
The most helpful posts are the ones that describe the nature and scope of a problem. Try to share the following information in your post or comment:
- Summary of the problem
- Your support case number (see: “If you need support, contact us first!”)
- What you’re trying to accomplish
- What steps you’ve tried already
- Photos, if relevant
- Other necessary information or resources
It's much easier to address requests for help if we clearly understand the context of the issue, the problem, and why it matters to you.
Rest assured we will read your post, but we may not respond
Our team dedicates time each week in the community to read your comments, answer your questions, and ask you questions about your feedback.
That said, we simply can't respond to everything. Team members may engage in conversations, ask follow-up questions, or even start threads on topics they’re exploring. If your post or comment doesn’t receive a response, don’t worry. Remember this is a forum for sharing knowledge with peers and if you need help directly from Desktop Health, contacting support is the best way to do that.
Posts are not guaranteed a response. This forum is simply for sharing your challenges and how you use the product, but it is not a case/resolution system.
Post maintenance and archiving
Requests that have been inactive (have not received a new comment) for 6+ months may be archived. These are retained internally and remain visible to the Desktop Health team. This helps to keep the community navigable and helps us prioritize the topics that are most important to the largest number of users.
This doesn't mean your post was bad, or that it wasn’t useful. It just means that it wasn't something that came up for a lot of users. Since we keep records, if the same topic pops up again, we’ll aggregate that information behind the scenes.
Comments that turn disparaging, mean, or are otherwise unhelpful to the conversation may be removed without warning. You're allowed to express frustration or dissatisfaction, just remember there are real people on the other side of the screen. Your colleagues and your neighbors can see these comments if they Google your name. So keep it civil and professional.
Thank you for reading this and for understanding how we address Community posts. We value all feedback and we're happy to have a place to engage in these conversations.
Post is closed for comments.