Changelog

What changed, newest first. We list the things that affect how your assistant behaves — not every internal fix.

Early access

Your app's chat, closer to your app. Version 0.2.0 of the Android, iOS, React Native and Flutter SDKs can put the chat inside one of your own screens, such as a Help tab, open it with a question already typed, and offer your signed-in customer's name, phone and email in the chat's forms. When your team answers a customer who asked for a person, the SDK tells your app the next time it is opened, so you can show a dot until they read it. SDK reference.

Your menu or services, in the chat. Add your dishes, products or treatments with prices, options, photos and sections — or import a photo of your menu, a PDF, a Word document or a CSV, check the drafts and publish. The bot answers prices only from this list, shows the items it talks about as cards, and checks questions like "anything vegetarian under 200?" against everything you sell. Guide.

Orders in the chat. Customers add dishes to a cart and place an order for pickup, delivery or their table, or simply type "two butter chicken and three naan" and add what the bot lists with one tap. The Orders screen chimes, and every move you make shows on the customer's order card. Payment stays at the counter, the table or the door. Guide.

Bookings in the chat. Set your hours, slot length and closed dates; customers pick a free time for a service and you confirm it on the Bookings screen. Two people can never take the last place, and a patient's note is never sent to the AI or put in an email. Guide.

WhatsApp alerts for orders and bookings. Switch on WhatsApp alerts on the Orders or Bookings screen and every new order and booking reaches your phone, with a reminder when one is still waiting. Each team member chooses for themselves, and messages go only to the number they sign in with. Guide.

Popular, goes well with, and a Sales card. The Popular row and the item cards now follow what customers actually order, and the Overview shows today's orders, your best sellers and how many chat visitors go from the menu to an order.

Actions: answers from your own system. Connect your own API and the bot can look things up while it is talking to a customer — an order's status, a delivery date, a booking. You say when to use it and what to ask the customer for; the bot collects those details, calls your API from our servers and answers from the reply. It works on the website widget, your bot link and QR code, and every app, with nothing to install. Requests are signed, your API key is stored encrypted, and you choose which fields the bot may see. Guide.

Visitors can send photos and documents. A paperclip in the chat takes up to three files a message — photos up to 5 MB; PDF, Word, text and CSV up to 10 MB. The AI describes a photo the moment it arrives and answers from that; when your knowledge does not cover it, the bot says so and you see the file in Chats with a note of what was understood. Switch it off under Install if you would rather not. Guide.

Names, leads and a Leads screen. Give a chat a name, mark it as a lead — New, Contacted, Qualified, Won or Lost — and add a contact and a note. Leads lists them with a CSV export. The old Leads screen, for visitors waiting on a reply from you, is now called Waiting on you, and a visitor who leaves their details there becomes a lead automatically.

Summaries, a daily digest, and a PDF. Summarise any chat into a factual report — intent, outcome, sentiment, action items, a follow-up message ready to send — or a whole day into topics, unanswered themes, leads and training suggestions. Both download as a real PDF in your bot's language. 40 summaries a day per bot, separate from your answers.

Welcome flow. Walk a new visitor through a few questions — name, phone, what they are looking for — when the chat opens or after their first question. Answers are saved on the chat, shown to the AI, and can mark the chat as a lead. One flow per bot, edited under Welcome flow; the Test screen runs it. Guide.

A bigger (or smaller) chat button, and a chat-bubble shape. Install → Appearance has a new Button size — small, medium or large — that resizes the whole button, not just the logo inside it. Button shape gains a chat bubble: a rounded square with a tail on the side facing your page. Both preview on the Install page before you save.

The chat floats above its button. Opening the widget no longer swaps the button for the panel: the panel rises above it and the button becomes the close chevron, the way visitors expect. A new expand control in the header makes the panel window-height and up to 760px wide for long answers, and Escape closes it.

A refreshed look. Softer elevation, a slate palette that reads well on light and dark sites, a pill-shaped composer and a highlight on the header band. Nothing to install — it is the same one script.

Logo size grows the logo, not the button. "Large" used to make the chat button taller and the medium logo sat in a wide band of padding. The button is a fixed size now and the logo takes the space around it; the Install page previews the exact button.

Your app, on every platform. Android and iOS SDKs, plus React Native, Flutter, Ionic and a WordPress plugin. All of them open the same chat your website visitors get, so a change you make in the dashboard reaches your app immediately — no app-store release. The source is public at github.com/telybotai/telybot-Sdks.

A QR code for your bot link. Download it as a PNG and print it on packaging, receipts, menus or a sticker at the counter. Install → Bot link.

Your bot link looks like yours. Pasted into WhatsApp or Instagram it now unfurls with your bot's name, your welcome message and your colour, instead of a bare grey card. It also paints instantly instead of showing a blank screen while it loads.

Test your bot before you go live. The Test screen previews your assistant on six surfaces — website, mobile web, embedded, Android, iOS and the shareable link — and now actually answers you while your bot is still in draft. Visitors still cannot reach it until you go live.

Documents. Upload PDFs, Word files and text files as knowledge. Very long documents are read up to a limit, and the source now tells you when that happened rather than quietly reporting success.

Short facts are never dropped. A one-line fact — "WiFi password: …", "Hours: 9–9" — used to be lost during processing if it sat next to a long block of text. It is now always kept.

The bot link works with domain restrictions. Restricting your bot to your own domains used to break your shareable link. Our own page is now always allowed; other sites are still refused.

Inline chat fills its container. Embedding the chat inside a page now sizes correctly instead of floating as a small card.

Your escalation contact is private. Your phone or WhatsApp is no longer included in the widget's public configuration. It is still shown to a customer at the moment the bot hands over.

Answer cap counts honestly. A question the AI read but could not answer now counts toward your monthly answers, because it cost real work. Saved-answer replies and refusals before the AI still cost nothing.

Appearance settings. Accent colour, button position and label, set from the dashboard without touching your website.

The unanswered loop. Questions the bot could not answer collect with a count; answering one turns it into a saved answer immediately.