PagesThe ideaPossible forms of the systemTechnical base optionsOpen design questionsLimits and securityPersonalities and profilesUse scenariosScenario 1: Local use: me and my agentsScenario 2: Me, my agents and guestsScenario 3: Company: one departmentScenario 4: The whole companyScenario 5: GamesScenario 6: Customers and suppliersPossibilities for companiesPossibilities for gamesThe INEMA case (for discussion)Sources

Possible forms of the system

A. Observe only ("control room")

A live panel where everything arrives: bots, agents, queues and publications. Nobody writes there. - ➕ Simple, no risk of unwanted action, solves "I want to see what is arriving". - ➖ Does not change how work gets done; you still have to go to Telegram or the terminal to act.

B. Observe and talk

The same screen, but allowing you to message a bot and call an agent by @mention, with one thread per request. - ➕ Joins visibility and action. - ➖ Opens the permission question: who can send what to which agent.

C. Full multiplayer (the one in the video)

Several people, each with their own agents, in shared channels; agents talk to each other; apps and automations per channel. - ➕ It is the whole concept: human team plus agent team. - ➖ It is the most expensive to build and the riskiest for security and cost.

D. Hybrid by layers

Start as A and evolve to B and then C as use shows value. - ➕ Each stage is worth it on its own. - ➖ The risk is that the architecture of layer A does not serve C.