← Cases · UniChina Hub · module
Messenger integrations
Telegram, WhatsApp and the rest in one hub: several accounts, deals and chat on the card
Who it was for
Teams whose leads arrive from Telegram, WhatsApp and the site — and drown in managers’ personal phones
Value
The thread lives on the deal card, not in someone’s pocket. You can connect several bots and instances without a zoo of cabinets.
Interface
Pain
A manager writes from personal WhatsApp. History leaves with the person. Site, bot and chat are three worlds. amo widgets don’t cover personal Telegram.
Goal
One channels screen: status, several connections of one type, leads and chat in CRM.
Path
- Channel cards: personal Telegram, bot, WhatsApp, email
- Several connections per type (multi-tenant)
- Chat and notes on the deal card
- Mini App for the field, without losing context
What’s inside
- Telethon (QR) and Telegram Bot
- WhatsApp via Evolution API
- Connection statuses and webhooks
- TG/WA feed on the deal
Result
A channel is part of Hub, not an integrator add-on. The deal knows where the person came from and what they were already told.
Why this case is telling
A separate case for teams who arrive with “just glue WhatsApp and Telegram.” Glue only pays off together with the deal card and permissions — otherwise it’s a chat in a vacuum again.
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
BotFlow
A bot scenario builder: branches, site leads, a note on the deal. Marketing changes the branch themselves
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