Hi AI Innovators,
One idea I would love HiBob to explore is making its product documentation available as an AI-ready knowledge source for customers' own enterprise AI platforms, such as Microsoft 365 Copilot.
The use case is not primarily about asking simple questions such as “How do I configure X in Bob?” The bigger opportunity is using Copilot as a design partner for HR processes, while giving it sufficient HiBob product knowledge to understand what is actually possible.
For example, imagine that I want to redesign our Performance Review process.
I could work with Copilot on our requirements, process design, review cycle, forms, workflows, communications and internal documentation. However, for Copilot to provide really useful recommendations, it also needs to understand the possibilities, terminology and constraints of HiBob.
Ideally, I could tell Copilot:
“Help me design our new Performance Review process based on these business requirements, but make sure the proposed solution can actually be implemented in HiBob.”
Copilot could then combine:
- our internal company context and requirements
- our policies and existing Microsoft 365 content
- HiBob product knowledge
- the specific process we are designing
It could help us design the process, identify requirements that may not fit HiBob's capabilities, suggest alternative approaches, and help create implementation and user documentation.
I think this requires two things from HiBob
1. Make the documentation easily available to customers
Today, we can access HiBob's documentation through the Help Center and other resources. But for this use case, I would like a simple way to obtain the complete documentation, for example through a “Download all documentation” option or a regularly updated PDF/document package.
The important part is that I can bring this knowledge into my own Microsoft 365 Copilot environment and use it as a knowledge source for my agents and chats. Today, the process is Print page + Save to PDF for every bit of heartcorehr.hibob.com-knowledge I want my agent to read, and thats an exhausting process.
2. Make the documentation AI-ready
Simply combining the existing Help Center pages into one large PDF would only solve part of the problem.
The knowledge available to us today comes in different forms: written user guides, screenshots, videos, known limitations and practical details discussed in forum posts, and information about upcoming functionality in release documentation.
For a human user, it is possible to navigate between these different sources and build an understanding of how something works. For an AI agent, however, the quality and structure of the underlying knowledge becomes extremely important.
I would therefore love HiBob to use AI, human expertise, or a combination of both to create documentation specifically structured for consumption by AI agents.
For example, the AI-ready documentation could bring together:
- what a feature does
- how it is configured
- important terminology and concepts
- prerequisites and dependencies
- known constraints and limitations
- relevant information currently communicated through screenshots or videos
- useful knowledge currently found in community/forum discussions
- relevant changes or upcoming functionality from release documentation
The goal would be a structured and comprehensive representation of HiBob product knowledge that an AI agent can understand and reason from, rather than simply a collection of Help Center articles.
Why does this need to live in our own AI environment?
Because much of the value comes from combining HiBob knowledge with sensitive internal company information.
I may want Copilot to consider our organizational structure, internal processes, policies, existing documentation and other confidential information when helping us design an HR process.
For that reason, a chatbot on top of the public HiBob Help Center would not solve the same problem. I want the HiBob knowledge to come to my enterprise AI environment, rather than having to send our sensitive business context to an external chatbot.
The ideal combination would be:
Our company data and requirements + our Microsoft 365 Copilot + AI-ready HiBob product knowledge
This could move us from simply searching HiBob documentation to using HiBob product knowledge while actually designing, implementing and documenting better HR processes.
Performance Reviews are just one example. I could see the same concept being valuable when designing onboarding, compensation processes, workflows, employee lifecycle processes and many other areas of HiBob.
For customers already experimenting with Copilot and AI agents, I think having access to official, comprehensive and AI-ready HiBob product knowledge could be incredibly valuable.
Best regards,
Øyvind