---
title: "Set up Kai Support investigations"
description: "Choose the boards Kai investigates, configure triggers and handovers, and set investigation limits."
url: https://help.gleap.ai/ro/articles/383-set-up-kai-support-investigations
collection: "Investigations and Kai Code"
updated: 2026-11-01
language: ro
alternates: [en]
---

# Set up Kai Support investigations

Choose the boards Kai investigates, configure triggers and handovers, and set investigation limits.

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.

### Choose the boards

1.  Open **Investigations** in Kai Support’s settings.
    
2.  In **Boards**, check whether board teams are enabled.
    
3.  If needed, choose **Turn on board teams** and configure the boards under **Settings → Project → Teams → Boards**.
    
4.  Choose a team for each board and turn on Kai’s investigations for the boards where it should work first.
    
5.  Resolve any blocker displayed beside a board before enabling it.
    

![Kai support investigations screen in the Pied Piper demo project.](https://staticfiles.gleap.io/p613b5dd730aed737108f87ab/F7DcsUdUunmZYWWGbam1tBWzXOFPlvVFpKkb2HgcttzwGTquox1I3aRYarsylcVmEIkc7ymSEHI.png)

![Kai Support answer-step controls, including investigation and forwarding settings in the Pied Piper demo project.](https://staticfiles.gleap.io/p613b5dd730aed737108f87ab/VzlDTu5bIQBYv8cBCORmqLegMN3m6OnZE5fw4ZwNmeIxFjoZ9idG0tb7DhIAlAi6an2bzjGwg11.png)

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.

### Give Kai the evidence and tools it needs

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.

### Set when it steps in

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.

### Set models and limits

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.

### Choose the handover destination

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.

### Test the complete path

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.

### Related

-   [How Kai Support investigates hard cases](https://help.gleap.ai/en/articles/382-how-kai-support-investigates-hard-cases.md)
    
-   [Connect a tool to an agent](https://help.gleap.ai/en/articles/248-connect-a-tool-to-an-agent.md)
    
-   [Connect a code repository](https://help.gleap.ai/en/articles/264-connect-a-code-repository.md)