← Cases · UniChina Hub · module
BotFlow
A bot scenario builder: branches, site leads, a note on the deal. Marketing changes the branch themselves
Who it was for
Teams that need a bot with branches around the process, not “another chat script”
Value
A manager sees the scenario as a graph. A landing lead, a Telegram command, a CRM notice — one scheme, without a contractor for every bot.
Interface
Pain
Scenarios lived in JSON, in people’s heads, and in chats with a developer. Changing a greeting or an “if WhatsApp” branch took a sprint. The site and the bot did not know each other.
Goal
A visual builder: trigger → steps → CRM. Lead bot and Mini-CRM in the same loop.
Path
- Node graph: message, buttons, condition, pause, write to the deal
- Triggers: bot command, event, site lead
- Ready template “landing lead → CRM note”
- Lead bot and Mini-CRM for field managers
What’s inside
- Canvas scenario editor
- Several Telegram bots on one Hub
- Branching by channel
- JSON import/export if you need to take the scheme elsewhere
Result
A marketer changes a branch without a ticket to engineering. A site lead enters the scenario instead of a shared chat.
Why this case is telling
A module inside UniChina Hub, but a product on its own: agencies, schools, and services with messenger qualification all use this kind of builder. It shows that custom work is a tool the floor actually uses — not “another admin.”
The live cabinet is private. You can judge the interface in the demo on this page.
More modules from this loop
UniChina Hub
A CRM for an agency: site, Telegram, WhatsApp. One system instead of a boxed tool and manual glue
Survey builder
Public surveys in the site’s look: step logic, CRM tags, completion analytics
Landing and site analytics
The agency marketing site plus its own analytics: block attention, form funnel, leads into Hub
Messenger integrations
Telegram, WhatsApp and the rest in one hub: several accounts, deals and chat on the card