Inbox
Inspect Conversations, Sources, runtime traces, and session metadata.
The Inbox stores Visitor and Assistant turns. Open a Conversation to inspect the exact stored transcript.
Conversation list
Use search and available filters to narrow the list. Each row identifies recent activity and its current Conversation state.
A session that contains only proactive Notifications has the Notification only marker. It becomes a normal Conversation after a Visitor replies.
Swipe a row to the left, or select its Actions button, to show Archive, Flag and Delete. A full swipe archives the Conversation. Select Archived to restore it or Flagged to find your marked Conversations. Archive and Flag affect only your own list. They do not change the transcript or its analytics. Delete asks for confirmation and removes the transcript. A Conversation under legal hold cannot be deleted.
Conversation detail
The detail view can show:
- Visitor and Assistant messages
- the Flow that handled a turn
- named Source citations
- Visitor feedback
- escalation state
- launch and device metadata
- the verified SSO subject and configured identity claim
- stored Thinking information when the member Role permits access
Verbatim Message actions and Basic replies do not contain a Thinking trace. Search knowledge answers can contain tool and progress events.
API integration calls also appear in the trace. Their events show which endpoint supported the answer.
Take over a Conversation
You can answer a Visitor yourself. Open the Conversation and select Take over. You must be an Editor, an Admin, an Owner or a Support Agent.
When you hold a Conversation:
- The Assistant does not answer. Each Visitor message is saved and shown in the Inbox, but no Flow runs and no model is called.
- A reply box shows below the transcript. Your reply goes to the open Widget with your display name. The Visitor does not have to send a message first.
- The Widget and the Inbox show a line when you join and when you leave.
- Other Members see who holds the Conversation. Only one Member can hold it at a time.
Select Release to give the Conversation back to the Assistant. The next Visitor message starts a normal turn. An Admin or an Owner can release a Conversation that a colleague holds.
Your replies are operator messages. They are not AI answers, so Insights, answer verification and feedback do not count them. The JSON export and the printed transcript mark them with the sender Operator and your name.
The Widget checks for your replies every few seconds while you hold the Conversation. It also checks every 15 seconds for 5 minutes after the Visitor sends a message, so it can show that you joined. An idle Widget sends no extra requests.
Quick Texts
Quick Texts are saved replies for the reply box. Editors, Admins and Owners create, edit and delete them in Settings > Quick Texts. Each Quick Text has a title, a body and an optional folder.
To insert a Quick Text, type / in the reply box. Continue to type to filter the list by title. Select a Quick Text, or press Enter, to put its body where you typed /. You can change the text before you send it.
A body can use the template variables that Flow actions use, for example {{user.name}}. Ciele fills them in from the Conversation that you answer. A variable that has no value becomes empty text.
Every Member who can reply can use every Quick Text. You can also manage Quick Texts with the API, the ciele quick-texts CLI command and the manage_configuration MCP tool.
Create quality work
Use the available Improvement action when an answer needs correction. The new item links back to the affected Conversation message.
Use Exports when you need structured records outside the Inbox.