Can Rovo help reduce repetitive onboarding questions from new employees?

[Miguel Santos]

We're exploring Rovo to improve our internal onboarding documentation because our HR team keeps getting the same questions from new hires.

Most of these questions are about required documents, submission deadlines, and where employees can find the latest instructions. Instead of answering the same questions repeatedly, we're considering building a searchable knowledge base that Rovo can reference.

One recent example involved an employee in the Philippines who needed guidance about renewing a required document before joining the company. We ended up sharing a simple renewal instructions page so they could complete the process without contacting HR again.

Has anyone here used Rovo for this type of internal documentation? Does it do a good job of surfacing the right page based on natural language questions, or does it require a lot of manual organization?

[Akash Singh · Accepted solution]

@Miguel Santos 

Yes, we've built a custom Rovo Agent for a similar use case, and it worked really well for the customer.

In my experience, the biggest factor in the quality of the responses is the quality and coverage of your knowledge base. The more comprehensive and up-to-date your documentation is, the better the agent will be at answering employees' questions. As the saying goes, your agent is only as good as its knowledge base.

Rovo also does a good job of understanding natural language queries, so users don't need to know the exact page title or keywords. As long as the relevant documentation exists and is indexed as a knowledge source, it can usually surface the appropriate information without requiring extensive manual organization.

If you're just getting started, these Atlassian resources are worth reviewing:

• Creating and editing Rovo Agents: https://support.atlassian.com/rovo/docs/create-and-edit-agents/

• Adding knowledge sources to agents: https://support.atlassian.com/rovo/docs/knowledge-sources-for-agents/

One recommendation from our implementation: instead of creating a single agent that tries to handle everything, consider breaking the functionality into specialized sub-agents (for example, HR onboarding, IT setup, benefits, and compliance) and have a parent agent delegate requests to the appropriate sub-agent. This makes the agents easier to maintain, improves response quality, and allows you to scale your solution as your knowledge base grows.

[Marko Josipović]

I've used a Rovo agent scoped to internal technical documentation and it does a solid job surfacing the right page from natural language questions.

The key is having clear, complete pages with descriptive titles.

You don't need heavy manual organization, semantic search handles a lot, but structuring content around the actual questions people ask noticeably improves results.