---
title: Manage conversations
description: Choose the right context and keep discussions connected to their deliverables.
lastVerified: 2026-09-23
---

# 3.2 Manage conversations

Use conversations to ask questions, add background, and follow up on results. When you talk to a colleague, the business context affects the materials and permissions it can use.

## Start a conversation

Start a general discussion from Conversations, or choose a colleague to talk to on the Colleagues page. A colleague that supports several business areas may first ask you to choose one. Select the scope relevant to this work.

Explain the goal and materials before specifying the output format. For example:

```text
Based on the description I provide, list three confirmed capabilities and three open questions.
Include evidence from the source for each item. If none is available, write “Not provided in the materials.”
```

## Continue, find, and archive conversations

Find an existing conversation in the directory and add follow-up questions to retain its context. Recent work is a shortcut; removing a conversation from it does not remove the conversation from the directory.

Use search to find conversations or content. Archiving helps organize history. Deleting and archiving are different actions, so read the impact shown before proceeding.

[![Conversation search and list on the left, with an open group on the right](https://docs.teloa.ai/assets/screenshots/en/conversations.png)](https://docs.teloa.ai/assets/screenshots/en/conversations.png)

*English interface with sample data. Find a conversation through the search and list on the left. The selected group appears on the right, with thread replies below its message.*

## Turn a discussion into a task

When work needs a named owner, execution status, and deliverables, formally assign it through Tasks. Link a conversation or group when needed. A chat reply alone does not show that an independent task has started in the background.

Model responses can contain errors. For prices, external state, and actions that need to be performed, check the sources or actual execution records. Response text is not a receipt proving that a tool succeeded.