+++ nonce = "330588787077808328" project_nonce = "999" owner = "596642625" language = "en" title = "Leads and the inbox" content_hash = "f15bc0b457f21fc4b16f1ea02ab75ae5141322da25c67fbc76c24a01bfbd3643" +++

Leads and the inbox

A lead is a conversation that has started. The correspondent you got into contact with (or who reached out via your project), plus context: which project triggered, in what thread, in what status.

The cabinet inbox is split into tabs by surface, and the distinction matters.

The bridged tab is the bridge to Telegram conversations. In its current state this bridge is not fully applicable: to continue a conversation that started in Telegram, you need Telegram itself. The cabinet shows that the lead exists and its basic context.

The native tab is for chats that live entirely inside the web UI. This is a separate surface for outreach and interactions that originate inside the platform, when Telegram isn't the right channel. These conversations are read and written entirely in the cabinet.

An oracle works on behalf of the project on the Telegram side — grounded in QnA, in the project's voice, within its rules. You decide when to step in personally; until that moment the oracle carries the conversation in the same thread the lead lives in.