Ask and answer questions about all things Guru and knowledge management
- 448 Posts
- 1,438 Replies
Hey Guru Ops folks, a few weeks back I joined the Wizards of Ops community. Recently, Guru has been getting a good bit of love over there across channels. It's possible I had a little something to do with that (:wink:) but clearly others are fans, too. Anyway, I wanted share the :heart: and encourage folks to check the workspace out - it's been active and helpful so far, as I've been expanding breadth and depth on my ops journey. https://wizops.org/#form :thankyou:
Hey everyone! I'm interested to hear of best practices for when missing knowledge is identified, particularly in the use case where the Support agent *knows* how to answer the query, but the process isn't documented yet. It's also worth adding that I'm looking for a particular flow for agents who don't have Author permissions, so can't *create* a new Card. I know this is something that can be solved via Slack, but I'm also interested to hear of ways this could be solved using the Extension, if at all? For context, we're using Zendesk. *For example:* • Agent replies to customer • Agent then wants to flag to Knowledge Council that we need a Card for this process Would the best solution be to use Slack here? Would you use Ask an Expert?
Happy Friday everyone! Show of hands :hand:...who has a Knowledge Council where you work (aka a group of folks responsible for helping to maintain knowledge and uphold established best practices in Guru)? What are some tips for keeping council members engaged and/or leveraging the group to help improve your Guru trust score?
This isn't exactly related to Guru, but I'm wondering how others are managing data erasure requests under GDPR. Do you have an automated system you direct users to? An internal process of asking each dept to see if there's info and delete? We get a lot of these and I'm wondering if there's a better way to handle them.
Is Guru meant for use for standard operating procedures (SOP)? I'm trying to create cards for the next steps for customer onboarding. We have multiple different customer onboarding flows depending on whether they are a current customer or new and which product they are purchasing which also determines which email templates to use. How can I do that while also keeping the cards "byte-sized"? Is there a how-to guide for this use-case?
When using the "Link to Ticket" feature, has anyone figured out a way to see what Cards a Ticket is linked to? In Zendesk, if I'm looking at a ticket, I want to easily see that someone has linked this ticket to the appropriate card without needing extra steps. We're using to track product feedback and bugs so there can be more than one linked card per ticket. I was thinking perhaps some kind of API call that could populate a Google Sheet and filter for that Ticket ID. Google Sheets can be added as a sidebar in ZD, so maybe somehow there's some magic that could work there? Or if the Guru Extension could show what cards this ticket is linked to -that would be stellar!
We've repurposed a few cards from the pre-populated collection frameworks before the new help desk was created, and I can't find the updated URL for this card: https://help.getguru.com/articles/qi7zojc8/Security-Overview If it doesn't exist I don't need it, but would love to include it if I'm just missing it
Hi Everyone - Long story short, we've have some logistics challenges getting our team + partner teams to use the Guru Chrome extension and I'd like to find an easy way for our vendors to confirm they're able to use it. Are there any Chrome browser -only tasks that you can think of they can complete to confirm they've the extension installed?
Question regarding the guru slack bot. Some users experience the app automatically added to their slack and some say they have to add the app. Does anyone know what steps need to be taken so that the app is automatically added in slack for all users?
Hello fellow Gurus! At Pliancy, we encourage everyone to contribute docs where they can, and we do as little gatekeeping as possible. This has led to significant engagement with our docs, both in terms of creation and consumption. We've tripled our team over the last two years, and all the while were biasing for hiring proactive people that wanted to share their knowledge. We knew we didn't want to do any additional gatekeeping, but we increasingly needed a way to administer Guru in ways that the UI doesn't support. So, using the excellent Guru API, we made this CLI tool. Based on a bit of lurking here in the Guru Slack community, we thought others might want some of these features and decided to publish the tool on NPM. It's open-source, so you can use it however you see fit. Please feel free to open a GitHub pull request if you notice any issues or have a feature request. As a side note, you must be a Guru admin for the tool to work correctly. :slightlysmilingface: Features include:
hey y'all. Who has a 'How To Guide' template that they are super proud of and wants to let me steal ideas from it? :smile: My end goal is a template that is fleshed out enough to guide other authors as they fill them out. (Trying to take another baby step toward having other authors live in our system.)
I'm considering creating and managing a Glossary of Terms in Guru. I'm deliberating whether to have individual cards for each term, or group terms under related sections. Grouping is an option as verification is done by different teams. And what's the difference between a Board and a Board Group, and how would I use them differently? Any thoughts....
Anyone have ideas around documenting your overall Guru collection/folder structure? Similar to an org chart, where any employee could view this document at a high level and know where to go for certain information?
Log in to engage in discussions
Use your Guru account credentialsLog in
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.