Giva – Web-native IT Help Desk, Customer Service, Knowledge Management, IT Change Management, Service Request, and Sales Request Solutions
 

 

Sign up for a free trial of the Giva Service Management Suite™

Sign up for a trial of the Giva Service Management Suite™ Free Giva Trial

 

Needs Analysis Tool

Clarify your solution requirements Download Needs Analysis Tool

 

Vendor Evaluation Tool

Compare and evaluate vendors Download Vendor Evaluation Tool

 

Giva Whitepapers

Learn about current industry best practices Download Vendor Evaluation Tool

 

Giva Service Management Suite™ Demo Center

Experience the Giva Service Management Suite™ Giva Demo Center

 

Print This Page Send To Colleague

"Day in the Life" Demonstration

Giva eKnowledgeManager User

<< 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 >>

Knowledge Administration and Reports

Knowledge Status Report – Proposed Knowledge

This report enables the knowledge team to manage proposed knowledge and make comments in the knowledge record history so that users can respond and provide additional information, clarifications, etc.

Initially, the knowledge team receives notification that there is proposed knowledge waiting for them to review and approve/reject. This notification is an emailed copy of the "Knowledge Status report" with all the new proposed knowledge. This notification can be set on a recurring interval such as twice per week.

In this report, knowledge approvers can click on the knowledge record link to access the knowledge record. They can ask questions to the knowledge proposer. This activity is documented in the knowledge record history field. Any new activity in the knowledge record history will trigger an email notification to be sent to the specific knowledge proposer. In the email, there is a link to the record and a copy of the new history entry and also a copy of all history entries for context. This is for the convenience of the proposer so that he understands what is still needed or in question in order for this knowledge to get approved.

After the proposer answers any questions or updates any knowledge record fields, another automatic email notification will go to the list of approvers so that they can take action. This process continues until the knowledge is approved.


<< 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 >>