Hey everyone! I'm a developer based in Ukraine, working on a messaging platform called Wexio. The idea came from watching small businesses juggle WhatsApp, Instagram DMs, Telegram, and email all at once, it's chaos, especially when you're a team of 2-3 people.
- Built a unified inbox with a visual flow builder and AI chatbots
- Spend most of the day working with Next.js, TypeScript, and GraphQL
- Use Strapi for CMS
- Utilize Radix UI for components - Recently focused on SEO and accessibility improvements (PageSpeed rabbit holes are real)
I also started writing about conversational AI and chatbot strategy on our blog. Figured Hashnode would be a good place to share some of that and connect with other builders.
Happy to chat about anything related to omnichannel messaging, no-code automation, or just surviving as a dev founder. Cheers!
This resonates a lot — I've built WhatsApp automation systems for clients in India and the multi-channel chaos is real. The visual flow builder + AI chatbot combo is especially powerful because it lets non-technical business owners actually customize their responses without writing code. One thing I'd suggest looking into: automated invoice and payment follow-ups through the platform. For small businesses, the biggest ROI from messaging isn't just customer support — it's closing the payment loop. Built exactly this for a CA firm recently and it cut their collection time by 60%. The Redis-based rate limiting approach is smart. Keep building!
I had been a part of a company who did the same but for businesses, not end users. They merged all the customer queries coming via different channels into a single screen.
Really cool idea. Unified inbox for WhatsApp/Telegram/IG DMs is something a lot of small teams really needsounds like a real pain point solved.
Curious how you’re handling message sync + rate limits across all those platforms?
BridgeXAPI
this is actually super interesting, especially the part about juggling multiple channels
one thing I kept running into when working on messaging stuff is that even if the inbox / orchestration layer is clean, the underlying delivery is still kind of a black box
like you can build a great unified system on top, but if routing or carrier behavior shifts underneath, things start acting weird and it’s hard to trace why
curious if you’ve run into that as well when scaling across channels
or do you mostly rely on providers to handle that layer?