
Configure investigations under AI agents → Kai Support → Settings → Investigations. This replaces the separate Kai Resolve setup. You need a plan that includes investigations; administrators decide where they run.
Open Investigations in Kai Support’s settings.
In Boards, check whether board teams are enabled.
If needed, choose Turn on board teams and configure the boards under Settings → Project → Teams → Boards.
Choose a team for each board and turn on Kai’s investigations for the boards where it should work first.
Resolve any blocker displayed beside a board before enabling it.


A board with investigations off is worked by its people. Enabling a board changes how its tickets are handled, so start with a board your team can monitor.
Add written sources under Knowledge. Connect repositories through Settings → Apps, then choose the repositories Kai Support may answer from on its Code page.
Open Tools on Kai Support to review its available actions. Permissions for a connected app are set on that app. Its Behaviour and Memory & context pages also apply when it investigates.
Review the sections on the Investigations page for automatic investigations, bug reports and handovers. When it runs adds triggers for tickets Kai takes on its own.
A Let Kai Support answer workflow step can set its own investigation policy. Open the live workflow under AI agents → Workflows and check that step when a particular customer path behaves differently.
Open Model & limits. Everyday answers and investigations are shown separately; the investigation model is picked by Gleap. Code checks have their own model and reasoning settings where available.
Review Investigations a day and Monthly budget. When a limit is reached, the board’s people get the conversation with Kai’s notes instead of another investigation.
In Investigations → Hand-overs, choose Hand-overs land on for supported cases. Bug reports always land on Bugs. Check the board’s team and assignment settings so someone owns the result.
Send a demo question that needs a deeper check. Confirm that Kai uses the intended evidence, asks your team when necessary and leaves useful findings when it hands over. Test the workflow customers actually run.