Intelli automates WhatsApp, website, and social customer conversations with trained AI assistants.
Grounded in available product and source data
AI customer engagement for WhatsApp and social is what Intelli is purpose-built around: rather than a generic chatbot bolted onto one channel, it's designed for B2C businesses juggling customer conversations across WhatsApp, a website widget, and social platforms all at once.
A visual, no-code builder is the starting point — a business creates an AI assistant, defines custom conversation flows, and trains it on a knowledge base built from its own information, rather than a generic model guessing at answers. Those assistants don't just handle conversations solo; they also suggest replies to human team members working the same thread, which matters for the messages that genuinely need a human touch. A unified inbox pulls WhatsApp conversations into one place with team collaboration and assignment built in, so a support team isn't juggling multiple logins to cover one channel.
Broadcasting is where scale shows up most concretely: campaigns can reach up to 2B+ WhatsApp users worldwide, personalized for promotions, order updates, or alerts, with analytics tracking delivery rate, read rate, and click-through rate rather than leaving a business guessing whether a campaign actually landed. The site's own example numbers — a 98.4% delivery rate, a 76% read rate, and a 21.3% click-through rate — give a concrete sense of what a well-run campaign looks like on the platform, though results for any specific business will depend on list quality and message relevance.
Beyond WhatsApp, Intelli covers a website chatbot widget, Facebook, Instagram, Messenger, and email/Gmail, plus unspecified third-party integrations. Three self-serve tiers scale mainly by contact volume, AI-credit allowance, and number of WhatsApp numbers connected, from a Website Widget starting plan up through a dedicated WhatsApp AI Assistant plan, with a custom Enterprise tier adding a dedicated account manager and advanced security for larger operations. The site states it serves 300+ businesses and positions the platform around 24/7 operation — worth noting that AI-handled coverage still depends on the knowledge base being kept current, since an assistant can only answer accurately from what it's actually been trained on.
WhatsApp is the primary focus with a dedicated API, but the platform also covers a website chatbot widget, Facebook, Instagram, Messenger, and email/Gmail, so a business isn't limited to one messaging channel.
No, per the site's positioning — the visual builder is aimed at non-technical team members configuring flows and uploading knowledge-base content directly, rather than requiring engineering resources for basic setup.
The site cites specific example figures — a 98.4% delivery rate, a 76% read rate, and a 21.3% click-through rate — though actual results for any given business will depend heavily on contact-list quality and message relevance, so these are worth treating as a benchmark, not a guarantee of matching results.
Mainly contact volume, monthly AI-credit allowance, and how many WhatsApp numbers are connected — the entry Website Widget plan covers a single team member and a smaller credit pool, while the WhatsApp AI Assistant plan adds a dedicated number and a larger contact and credit allowance.
Both — the assistant can respond directly, or suggest a reply to a human team member working the same conversation in the unified inbox, so a business can choose how much is fully automated versus human-reviewed.



These 12 comments were collected from the discovery source. ProductVisit does not host replies in Release A.
Hey Product Hunt 👋 I'm Samson, co-founder and CPO at Intelli. We built this for a reality most customer engagement tools don't build for because they don't understand nor relate to: in emerging markets, WhatsApp is how people buy, ask, and pay. So we built an A customer engagement platform that's WhatsApp-native first, then multichannel across Instagram, Messenger, web chat, and email. What makes it different: – AI assistants trained on your own data, not a generic bot – Local payment rails built in: M-Pesa, MoMo, Paystack, Flutterwave – Broadcast campaigns, lead qualification, and support in one inbox – Live in about 15 minutes We're an official Meta Tech Provider serving 200+ businesses. We launched on Peerlist on monday this week and it inspired us to come and launch on product hunt too. Would love your honest thoughts and questions. What does your current customer engagement tool get wrong? I'll be here all day.
2 source upvotesCongrats on shipping. With AI conversations the hard part is rarely the happy path, it's the handoff: knowing when the AI should stop trying and pull in a human before the customer gets frustrated. How does Intelli decide that escalation moment? That line is what makes or breaks trust for the business owner.
2 source upvotes@david_marko Hey David, thanks for the congratulations and question. Escalation can happen through business-defined rules and AI-detected signals. There's inflection points that enable the AI to escalate the issue; and some business set "triggers" that help guide this process. When that trigger happens, the conversation moves into the team inbox with the full history and customer context, so the human agent can pick up without making the customer repeat everything.
2 source upvotes@productrambler Hey Lavakumar, thanks for the question; no we currently don't handle or capture behavioural/emotional cues from conversations because there was no demand for it from our user base. Their focus was on other factors that directly contribute to their revenue.
2 source upvotes@dhiraj_patel5 Hello Dhiraj, Yes Whatsapp has shown typically higher AI resolution rates than web chat.
2 source upvotesCurious how Intelli handles intent signals beyond the words, do you capture any behavioural or emotional cues from conversations? That layer tends to be where leads actually convert or drop off.
1 source upvotesGood approach. Is WhatsApp showing higher AI resolution rates than web chat in your early deployments?
1 source upvotesCongrats on the launch! I love seeing more products built with emerging markets as the default instead of an afterthought. Curious if businesses are using Intelli primarily for customer support, or is WhatsApp increasingly becoming a full commerce channel (sales, payments, and retention) on your platform?
1 source upvotes@luki_notlowkey Thanks Luki. We built Intelli with emerging markets as main focus because we are from these emerging markets and most of the software we are using often comes to us as an afterthought. We needed to contribute to change that in our own way. To answer your questions:- Businesses using Intelli primarily are seeking for customer support tools but the use is spiralling into customer engagement. Whatsapp is indeed becoming a full commerce channel(we call it conversational commerce) but some segments of emerging markets haven't caught up to it so the focus is on customer support and engagement for now.
1 source upvotesCustomer support AI is crowded but the multi-channel part is the hard problem - most tools work fine on one channel and fall apart when you mix WhatsApp, email, and live chat in the same conversation thread. What does the handoff look like when the AI can't resolve something? That moment is where most platforms lose customer trust fast.
1 source upvotes@galdayan Customer Support AI is crowded, that's a fact. There's so many players and differentiating oneself is a bit tricky. What you have mentioned about multi-channel being the hard problem to solve is something that we also agree with/on and are working towards making that experience the best. The handoff is a mix of AI detected signals and business defined logic. The escalation to human chat is handled seamlessly in that way. We don't want to see an endless and annoying loop of customers stuck with AI who want to access human support but can't.
1 source upvotesRunning community launches, the WhatsApp-native plus local-rails combo (M-Pesa, Paystack, Flutterwave) is the part most support tools ignore — buyers in emerging markets transact in-thread, not on a separate checkout page. One concrete edge case: when a customer pays via M-Pesa inside a WhatsApp conversation, does the AI assistant receive the payment confirmation as context so it can move the conversation forward or trigger fulfilment, or is payment a siloed step the agent never sees?