+++ nonce = "330494191513632774" project_nonce = "999" owner = "596642625" language = "en" title = "Two surfaces, one platform" content_hash = "96e5d8ff986af4a2a2c6f1f0c677fbc4710471fad172a5034bab84e2f5c1117c" +++

Two surfaces, one platform

Cabi.Chat lives in two places at once. The web cabinet is where you do the work. Telegram is where the work meets people.

The cabinet is the workspace: projects, QnAs, search, radars, presets, balance, the inbox for leads that originate inside the cabinet itself.

Telegram is a strategic surface, not a side channel. It's where your audience already is, and it's the largest accessible communication platform with an open API — campaigns reach into public groups there, oracle agents speak on behalf of projects in DMs, and conversations continue inside Telegram without anyone leaving the app they already use every day. Telegram conversations stay in Telegram.

Native chats in the cabinet are a separate, parallel surface — primarily for outreach and engagement that starts inside the web UI when Telegram isn't the right channel.

Cabinet and Telegram serve different jobs: one for setup and depth, the other for reach and convenience. They are not bridged today.