One bot, four channels: what actually differs between web chat, WhatsApp, Messenger and Telegram"Put the same bot on WhatsApp and Telegram too" sounds like a configuration change. It is not a hard project either — but the parts that differ are not the parts people expect. The messaging APIs are8 min read·chatnory.hashnode.dev8h ago
Multi-tenant from day one: keeping one customer's chatbot data out of another'sThe first version of almost every B2B tool is single-tenant by accident. You build it for one customer, it works, a second customer arrives, and you add a customer_id column. That column is now the on7 min read·chatnory.hashnode.dev8h ago
What an AI support chatbot actually costs per conversation"How much will this cost to run?" is the question I get before any technical one, and the honest first answer is annoying: less than you fear, in a shape you did not expect. People budget for the inde8 min read·chatnory.hashnode.dev8h ago
Six guardrails that stopped our support chatbot inventing answersA support chatbot that makes things up is worse than no chatbot. A missing answer costs you one email. A confidently wrong answer about a refund policy costs you an argument, and the customer has a sc6 min read·chatnory.hashnode.dev15h ago
Putting an AI chatbot on WhatsApp: the five parts of the Cloud API that cost me a weekThe hard part of putting a chatbot on WhatsApp is not the chatbot. It is WhatsApp. The messaging itself is a plain HTTPS POST and you will have it working in twenty minutes. Then you spend a week disc7 min read·chatnory.hashnode.dev15h ago
