tufu
Start free
Docs menu

Changelog

Changelog

What changed in tufu, newest first, in plain words.

On this page

November 1, 2026: simpler pricing#

  • One pack price. More answers are $10 for each 1,000, in any amount, on every paid plan, and they never expire (see Plans, answers and packs).
  • Simpler model counts. Each model uses a fixed number of answers a reply: Claude Haiku 5.5 1, Claude Sonnet 5.5 10, Claude Opus 5.5 25. Reasoning levels are now for your own AI key, and the bot's settings say what your month comes to on each model (see Answers).
  • Scale includes 25,000 answers a month, with priority email, an onboarding call and free installation help.
  • The daily summary is part of every paid plan.

November 1, 2026: tufu 2#

tufu 2 does the next step, works wherever your customers are, and is safe to change. The whole story is on What's new in tufu 2.

  • Playbooks. A few questions in your own words, then a booking link, a lead, a webhook or a handoff with the answers attached. The bot answers side questions and comes back to the step it was on (see Playbooks).
  • Booking links. When a visitor wants to talk, the chat offers your Calendly or Cal.com page with their name and email filled in, on every plan (see Bookings).
  • Bookings in Google Calendar. On Team and Scale, the bot finds free times in your calendar, the visitor taps one, and it's booked, with the invite sent to them (see Bookings).
  • Drafts, versions and test questions. Changes to how a bot answers go to a draft you can try first; each publish keeps a version you can restore. On Team and Scale, test questions run on publish and show which answers changed (see Publishing changes).
  • Telegram. On Team and Scale, your own Telegram bot answers from your docs in private chats and groups, and /human brings the chat to your inbox (see Telegram).
  • Look it up. On Team and Scale, the bot can look up a signed-in visitor's order or account in your own system, read-only, and sees only the fields you allow (see Look it up).
  • tufu in your own Claude. On Team and Scale, Claude Code or Claude Desktop can list what needs you, read a conversation and reply, with an API key whose scopes you choose (see MCP).
  • A direct link and a help page. Share one link to your chat, or frame it in a page. Opened on its own it's a help page: the Ask box, the questions people ask most, and a way to reach you.
  • The Ask bar. The Ask console as a bar at the bottom of every page, from Put it on your site or the WordPress plugin.
  • WordPress plugin 0.3.0. Choose the chat bubble or the Ask bar under Settings → tufu AI (see WordPress).
  • Write your own answers, and more files. Text and question-and-answer knowledge right in tufu, and Excel, CSV and JSON files read row by row (see Knowledge).
  • A daily summary. From Starter up, every morning: what the bot answered, what it handed off, and who's still waiting.
  • The chat in six languages. Its buttons and labels follow your visitor's browser: English, Spanish, French, German, Portuguese or Arabic.
  • New plans. Starter and Scale join Free and Team, with people unlimited on every plan (see Plans). Free's new limits start at each team's next monthly reset.

October 27, 2026#

  • Inbox filters. Narrow the list to one channel or bot, to answers a visitor marked not helpful, to visitors who left an email, or to the last day, week or month. A waiting conversation shows how long it has waited, highlighted past your reminder time. New keys: r to reply, e to resolve (with 5 seconds to undo), ? for the list.
  • Saved replies. Keep the answers your team sends again and again, and send one with /name in the inbox, by email or in Slack, or pick one to edit first (see Saved replies).
  • A lighter chat. The chat window on your site loads about 40% less than before (and no display font), so it opens faster on a slow connection.
  • Privacy Policy, DPA and Subprocessors now describe lead forms and webhooks: what a form can collect, how consent is recorded, and that lead details go with their conversation.
  • Plainer legal and security pages. The Security page, Privacy Policy, DPA, Subprocessors and Terms now describe the kinds of provider we use instead of naming each one, and say only what they need to. The full list of providers is available on request.

October 26, 2026#

  • Leads. Your bot can ask visitors for their details in the web chat: when they ask for a person, after its first answer, or before the chat starts. Leads show in your inbox with their conversation, marked New or Followed up. On Team, add your own questions, get pinged for each new lead and export them (see Leads).
  • Webhooks. On Team, tufu can send each new lead, and each change to one, to Zapier, Make or your own server as it happens, signed so you can check it came from tufu (see Webhooks).
  • "What was wrong?" after a thumbs down. Visitors can say an answer was wrong, didn't answer their question or is out of date. Knowledge gaps show the answer that didn't help and the pages it cited.
  • Reports lead with "Handled by the bot": conversations the bot answered without a person and without a thumbs down on its last answer. New cards show where visitors asked for a person and why answers didn't help, and the arrows compare the last 30 days with the 30 before (see Reports).
  • Your setup checklist ends with a real answer. "Answer a real customer" ticks itself off the first time your bot answers a visitor, and the "put it on your site" email now comes a day after your bot has read your docs.

October 25, 2026#

  • WordPress plugin 0.2.2. Check it's live on tufu on the plugin's settings page opens your bot's Put it on your site page, which says whether the chat has loaded on your site (see WordPress). The help for typing the IDs points to that page too.

  • Exports are safe to open in a spreadsheet. Nothing a visitor typed can run as a formula in Excel or Google Sheets, and the messages file now has your team's replies too, not just the visitor's messages and the bot's answers (see Your account and data).

  • Confluence tokens are now stored encrypted. And editing a Confluence source keeps its token: leave the API token box empty when you change something else and the saved token stays.
  • "Refresh every week" only where it works. Uploaded files, zips from a link and Slack threads no longer offer it: they're never read again on their own. Re-read them from their page when they change.
  • "Last loaded" means your real site. On Put it on your site, the time under "Live on" is the last time the bot loaded on your site, never a copy running on your own computer.
  • An email with only a screenshot still arrives. A support email, or a visitor's emailed reply, that holds only attachments reaches your inbox, with the file names noted. tufu can't open attachments yet.
  • Removing something asks first, and names it. Cancelling an invitation, removing your saved card, a Discord channel or a connected login now asks before it happens, like deleting a bot always has.
  • Answers in your visitor's language. Your bot replies in the language each visitor writes in, unless your instructions say otherwise.
  • Easier with a keyboard and a screen reader. On a phone, the open chat keeps Tab inside it and closing it puts you back on the chat button; screen readers read each answer once it's complete, not word by word.