Nathan
My feedback
1 result found
-
28 votes
An error occurred while saving the comment An error occurred while saving the comment Nathan
commented
Linking and copy and paste are options. We are talking about support interactions so the fewer clicks and applications the better to adopt the right behavior (saving the knowledge).
With the enterprise option, does it have to be the entire database? Could we not have a pick and choose option? Im guessing this would an API thing that is out of my scope.
I was looking for a shorter term option (exporting) before a potential longer term option (some kind of integration).
There may always have to be a copy and paste element so may be exporting is not the right term for me to be using.
Anyway any ideas here much appreciated.An error occurred while saving the comment Nathan
commented
Thanks Jonathan. It is an option, but i may want the source of truth to be outside of mattermost, and i would therefore prefer to link out than in, if that makes sense.
Take this engagement we are currently in for example. If it happened in a mattermost channel, i would export it to our other knowledge management (KM) system, and then if someone else asked the same/similar question, i would link them out to where ive saved this interaction.
I want it to be collaboration and KM rather than collaboration vs. KM.
Nathan
shared this idea
·
And to answer your other question, im not sure if this is something supported by other chat systems - this is the first time ive asked. Im asking in here because my colleagues have started to use this application and really like it.
Im trying to find the balance of real-time, quick and easy collaboration with capturing the knowledge output from these interactions. Helping to turn tacit knowledge into reusable explicit knowledge. Essentially stop people having to ask and answer the same thing over and over again, by saving it, making it searchable and browsable through KM.