Customers do not think about your internal processes. If Telegram is convenient — they write in Telegram. If the chat on your site is one click away — they click the chat. But for your team every new channel is another tab, another account and another place to miss a message.
One inbox instead of three tabs
In Duck Float every request — from the bot, the widget or the API — becomes a ticket in a shared inbox. A ticket has a status, history, tags and a source. Operators see all channels in one list and reply from one interface — the reply goes back to the customer wherever they wrote from.
What each channel brings
- The Telegram bot — the fastest start: a BotFather token, and customers are already writing to you in a familiar messenger.
- The chat widget — live conversations right on your site. One line of code, Shadow DOM, visitor context: name, email, plan.
- The public API — requests from your backend, mobile app or internal tools.
Shared context
The most valuable thing about a single inbox is not convenience — it is context. Conversation history does not depend on the channel, AI drafts work the same everywhere, and webhooks notify your system about every event. The team stops juggling tabs and simply replies.
