
Telegram, widget and API in one inbox for every request. AI drafts replies from your product context and logs — your team just presses Tab.
One tool instead of chat, email and spreadsheets. Your team replies faster; customers wait less.
Customers write where it's convenient — you reply from one inbox. Answers go straight back to the chat.
Press Tab instead of typing from scratch. AI already knows your product, docs and production errors.
Embed support in your product in minutes: a widget with page screenshots and a REST API with idempotency.
CRM, Zapier or your own script creates tickets with one POST — no API key or heavy integration.
AI sees what went wrong in production around the request — and suggests a precise answer, not a template.
Roles, statuses and assignment in one click. Operators sign in with a password; admins via GitHub.
Sign in with GitHub, connect your Telegram bot, Gemini and repository — all in settings within 10 minutes.
Messages from Telegram, the widget and API land in one inbox. Real-time updates — no page refreshes.
AI has already drafted a contextual reply. Tweak if needed and send — the customer gets an answer in seconds.
Below is the real Duck Float widget in demo mode. Type a message and see exactly what your customers will get.
A script tag with a data key before </body> — no SDKs, bundlers or dependencies.
Shadow DOM guarantees the widget never clashes with your site's styles.
Until the first click — just one script and a single config request.
Color, position and greeting are customizable in the panel settings.
What changes when support moves into a single inbox
Everything is free while the open beta lasts. No credit card required.
Paid plans will come after the beta — early teams get a discount.
Connect your tools in a few clicks — secrets encrypted, each workspace's data isolated.
The essentials — from setup to security
Signing up with GitHub takes about a minute. The Telegram bot connects with a BotFather token, the widget with a single line of code before </body>, and the API with a secret API key from settings.
You describe your product and typical answers in settings. The AI combines that with the conversation history and prepares a draft — the operator accepts it with Tab or edits it before sending.
No. The AI only prepares a draft in the reply field — every message is sent by an operator. You always control what the customer receives.
Live chat with instant updates, visitor context (name, email, custom data), and customizable color, position and greeting. Styles are isolated via Shadow DOM.
Yes. The public API lets you create requests from any backend, and webhooks notify your system about ticket events — from creation to closing.
Free and unlimited during the open beta. Paid plans will be announced in advance, and early teams will get a discount.
Practical notes on customer support, AI drafts and support channels
Comparing ways to add live chat to a website: iframe, script, Shadow DOM. How not to break your layout, slow the page, or leak privacy.
Comparing AI drafts and autonomous chatbots in support: where a bot fits, why auto-replies are risky, and what a small team should choose.
A sober look at AI in customer support: which uses genuinely save time, where the limits are, and why the "AI proposes, human decides" approach wins.
A simple "frequency x cost of error" matrix that shows what is safe to automate in support and where a human is irreplaceable. With examples.
How to keep one tone of voice in support when different operators reply: a style guide, do/don't examples and a shared product context.
When a business needs a support API instead of forms: requests from your backend, mobile app and internal tools. Scenarios and examples.
Free start with GitHub. Your first Telegram ticket arrives within minutes after connecting the bot.