back_office_ops · services · workflow
TIM centralizes IT knowledge management across hospitality clients with Guru
TIM's knowledge was fragmented across Slack, Google Workspace, and Confluence with no integration between tools, making information costly to maintain and difficult to search. High staff turnover in the hospitality sector made the fragmentation worse.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Employee submits a question
An employee asks a question and Guru retrieves results from Drive, Jira, and other connected platforms.
Tools used
GuruAI Training CenterSlack · partnerGoogle Workspace · partnerJira · partnerIntercomConfluenceGoogle Drive
Outcome
Guru gave TIM a centralized knowledge repository spanning Jira, Google Drive, and other tools, reducing time spent searching and context switching, and enabling employees to maintain knowledge quality through a dedicated Knowledge Council.
What failed first
Atlassian's AI was siloed within its own product and slow to roll out, making cross-tool queries impractical. Attempts to build a custom integration with developers were abandoned as too complex.
Results
Time savedreducing the time spent searching for information and context switching
Grounding & classification
Source type: vendor customer story
28 fields verified against source quotes.
enterprise searchknowledge searchknowledge basefailure mode describedhuman review describedmetric backednamed customersource backedtools describedworkflow describedhospitalityprofessional servicesemployee productivitytime savedvendor customer storyback office opsdata sync enrichment