When I looked at where small products actually talk to their users, a lot of it was not on the classic social networks. It was in a Discord server, a Telegram channel, a Slack community.
So Clienzo treats those as channels, with the same composer, schedule and per-channel result as Facebook or LinkedIn.
How each one connects
Each chat app has a different idea of what "connecting an app" means:
- Discord: you paste a webhook URL from the channel's Integrations settings. No login, no review. Up to 2,000 characters and 10 files per message.
- Telegram: you add the Clienzo bot to your channel or group, then post the short code Clienzo shows you. That proves you control the channel before anything gets linked to your account.
- Slack: a normal sign-in, then you pick the channel.
- Viber: you paste the token from the channel's developer tools.
None of them needed a platform review, which is a large part of why they shipped quickly.
Alerts in the same place
In Discord, Telegram or Slack, Clienzo can also tell you things: a post published, partly published or failed, or an account that needs reconnecting. You pick which events. For a small team that already lives in Discord or Slack, that beats another email.
Why not Microsoft Teams
Teams was on the first list and came off it. It is built around enterprise tenants and admin approval, which is the opposite of the people Clienzo is for: founders and small teams who decide for themselves.
What I cannot measure here
The trade-off: chat apps do not report views or reactions to an app for each message. Those channels show a blank in analytics, as described in part 5. You find out how a post did by being in the conversation — which, for these channels, is the point.
Next: one inbox for the comments coming back.
Originally published on jonasnguyen.com, where I write about building Clienzo and the next startups.
Top comments (0)