Cabi.Chat Campaigns
Cabi.Chat Campaigns are the graph's executables. A project does not only wait to be found; it acts through campaigns. A campaign belongs to a project, runs on that project's oracles, and does one job in the project's name. Telegram first.
Six kinds
- Radar. Finds public messages in Telegram groups where people ask for what your project offers.
- AI Scout. Reads the public groups you picked in batches, at the interval you set, and gives you an overview by your agenda: what matters to you and what is noise. Its picks can go to a radar.
- Announcements. Posts your posts in public groups that allow promotion.
- Reactions. Your oracles react to fresh messages in groups at a chosen pace.
- Join chats. Your oracles join a list or preset of groups, following each group's rules and Telegram's limits.
- Leave chats. The reverse.
What a campaign is made of
A project, Telegram groups, oracles, and where the job needs it, posts and a Swappable agenda Cabi.Chat Ignite — Agendas. Every slot takes cards or workspaces of cards, so one preset of groups or one team of oracles serves many campaigns. Cards shared with you with execute (x) rights can be attached too.
Lifecycle
Every campaign is created paused. Start and stop are one button. Radar, AI Scout, Announcements and Reactions run until you stop them. Join and Leave finish on their own once every oracle has walked the list. Start checks what is missing and says so; a run whose groups or oracles resolve to nothing ends as Failed.
Campaigns run only on Pro projects.
Operators
A campaign can be shared with write access. An SMM specialist or an agency can tune, start and stop it on your behalf; the performance stays with you.
Performance
Every campaign that sends has a performance view: messages sent, groups, oracles, replies, a timeline, a breakdown per group, and each message with its status: live, replied, removed.
Cabi.Chat Radar
Cabi.Chat Radar — With or without an oracle
Cabi.Chat Announcements
Cabi.Chat Radar — Telegram group presets
link
link