Changelog

The site, version by version.

Read what changed in the pages, content and navigation. Each entry names the version and its date.

Chawo is preparing for launch. We are taking early-access requests; AI and channel connections are not available yet.

Request early accessRead the product notes

Site release history

  1. 0.12.7

    Site

    A compact header keeps navigation, demo requests and language choices in one menu.

    • Open the menu beside the Chawo logo to browse pages, request a demo or switch between the published languages of the same page.
    • The menu works on small screens and without JavaScript. Keyboard users can close it with Escape and return to the menu control.
  2. 0.12.6

    Site

    The home page introduces Chawo as a service for sales chatbots and customer conversations.

    • Explore bots, broadcasts and human handovers first, then see how written or spoken instructions will become a scenario. The early-access stage stays visible.
    • Shorter Russian headings and navigation labels leave more room for the content on smaller screens.
  3. 0.12.5

    Site

    After submitting a form, the confirmation opens on the Chawo website.

    • The confirmation also works without JavaScript. Secure connections keep the confirmation cookie protected, and the request retains its page and campaign source.
  4. 0.12.4

    Site

    Send a question or request a callback, with a saved confirmation and recovery after a connection error.

    • Contact and early-access forms work in English and Russian, including without JavaScript. Repeating the same request preserves its original confirmation.
    • Site administrators can configure notifications, a phone schedule and optional analytics. These services remain off until their own settings are supplied.
    • When a new site version is available, a notice lets you reload after finishing your form.
  5. 0.12.3

    Site

    Explore the planned AI scenario experience through a furniture enquiry and human handover.

    • The site explains the planned path from written or dictated instructions to a scenario you can review; AI creation is not available yet.
    • A furniture enquiry connects the example diagram, conversation and designer handover. Channel icons share one clear availability explanation.
    • Product notes, plan descriptions and four illustrated articles help you review one familiar request before changing an existing bot.
  6. 0.12.2

    Site

    Channel icons reveal their names and availability, and the example follows one sales enquiry.

    • Select a channel icon, hover over it or reach it with the keyboard to read its name and status. The explanations also work without JavaScript.
    • Telegram bot delivery is at launch; the other five inputs are on the roadmap. This boundary remains visible below the icons.
    • Repeated links have been removed from the diagram and cards. The sample enquiry and human handover now follow one story.
  7. 0.12.1

    Site

    The site brings conversation branches, a human handover and illustrated articles into one visual system.

    • Follow a message through the example scenario, pause it or replay it. The steps and the example conversation show the handover as you reach it.
    • Four articles now have cover images and illustrations, and the blog opens with a featured publication.
    • English and Russian pages support both colour themes and narrow screens, with readable static versions when motion or JavaScript is unavailable.
    • Editors can update article covers, descriptions and illustrations from the site editor.
  8. 0.12.0

    Site

    The home page follows one conversation, from the first message to the person who takes over. Language choices now open in one menu.

    • The flow, three steps, example conversation, roles, prices and recent posts share a quieter layout on desktop and mobile, in English and Russian, with both colour themes.
    • Questions and the capability list are on the product page. The investor contact is in the footer, and one early-access form finishes the home page.
    • The language menu shows the published English and Russian pages by their native names and works without JavaScript.
  9. 0.11.4

    Site

    Each status on the site now has its own mark in front of the word, and the dot on an input chip is that same mark.

    • Ships today, at launch, in progress, planned, and on the roadmap each carry a mark to the left of the status word.
    • The dot on an input chip is the compact form of that mark: at launch is a half disc, and the roadmap is a dashed ring.
  10. 0.11.3

    Site

    The first-screen canvas now takes six channel inputs in one node, with WhatsApp Business and email on the plate and a status dot on each mark.

    • Telegram bot, a Telegram account, WhatsApp Business, website chat, voice, and email sit as six marks in one Inputs node, instead of a stack of named cards.
    • WhatsApp on that node is WhatsApp Business. Email is on the roadmap, and the dot on each mark says whether that input is at launch or on the roadmap.
  11. 0.11.2

    Site

    Channel marks now sit in the same chips on the channel board and in the footer as on the first-screen canvas.

    • The channel board on the Telegram page shows each name beside a chip with the channel mark: a paper plane, a round bubble with a handset, a microphone.
    • The footer shows the same five marks in smaller chips, still without a public account link.
  12. 0.11.1

    Site

    The first-screen button now opens a three-step section: connect a channel, draw the flow, and let the runtime answer until a person takes over.

    • See how it works now scrolls to a section below the canvas, not to the canvas card itself.
    • The three steps name a Telegram bot at launch, the canvas that ships today, and answers from your material at launch, each with its status word.
  13. 0.11.0

    Site

    The home canvas now sits in a card. Channel marks sit on the inputs, and one message on the diagram follows the path to Book a call.

    • The first screen holds the canvas in a framed card. Nodes stay inside the card and below the header.
    • Each channel input has a mark next to its name: a paper plane for the Telegram bot, a person with a plane for a Telegram account, a round bubble with a handset for WhatsApp.
    • One message on the diagram leaves the Telegram bot and follows the path to Book a call. When movement is off, that same frame stays still.
  14. 0.10.3

    Site

    The footer now shows channel marks without public accounts, and the legal and contact pages exist while their text is being prepared.

    • The footer shows Telegram, WhatsApp, website chat, voice, and mail as marks with names, and does not link them to a public account.
    • Privacy policy, terms of use, and contact pages now exist in English and Russian. The text is being prepared.
  15. 0.10.2

    Site

    A missing address with a file suffix now returns the not-found page, and the changelog link follows the newest published release.

    • An English or Russian address with a file suffix that is not a page now returns the heading, the lead, and both destination links.
    • Step numbers on the Telegram page keep contrast against the coral mark in both themes.
    • The invitation strip no longer makes the page wider than the window while it is waiting to enter the screen.
    • The changelog link to the latest release follows the newest published release, including a release added in the admin.
  16. 0.10.1

    Site

    The not-found page now arrives as a complete document, without a script.

    • A missing English or Russian address returns the heading, the lead, and both destination links in the first document.
    • Both theme images arrive in the same document.
    • A page published after the build still opens. An unknown address keeps the not-found status.
  17. 0.10.0

    Site

    A published edit in the admin now shows on the live domain, and a copy change in the repository reaches the live domain on deploy when an editor has not changed that page.

    • After an editor publishes a page in the admin, the live domain serves that page.
    • A copy change in the repository is applied on the next deploy when the editor has not changed that page.
    • When the editor has changed a page, the live domain keeps the editor version.
  18. 0.9.1

    Site

    Channel names now sit beside a shared set of marks, and the footer can show public channels when they exist.

    • Telegram, WhatsApp, website chat, voice, and mail share one set of outline marks.
    • The home diagram, the channel board, and the integration pages use that set; the word of the channel stays next to the mark.
    • The footer can list public channels. None are published yet, so the row stays empty.
  19. 0.9.0

    Site

    The site now has a blog with notes from the current build, and the home page points to the latest notes.

    • A blog lists posts by category, with the date and reading time on each card.
    • Four notes cover the canvas, the run ledger, local-first work, and the first plan.
    • The home page shows the three latest notes and a link to every post.
    • Blog stands in the header after Pricing, and in the footer with the other pages.
  20. 0.8.1

    Site

    Questions stay readable on inverted sections, and the access form is the same on every page that carries it.

    • Answers on the pricing page keep contrast against the inverted section behind them.
    • The early-access form on the pricing page now records an address, as the home page already does.
    • The three plan cards share one layout, with the Design limit held in a slot the other cards leave empty.
    • A status word looks the same wherever it appears, and each changelog entry has its own address.
  21. 0.8.0

    Site

    The home page now names three roles in a small sales team.

    • The third section of the home page now shows three roles inside one small sales team.
    • Each role opens with the line that names you, then the work that seat gets and how far it has got.
    • All three roles stay on the page without a script, and a selected role is marked by more than colour.
  22. 0.7.0

    Site

    The first-screen diagram can now be moved and zoomed.

    • The home-page diagram is a live canvas: it can be panned, zoomed, and shown in full.
    • Hovering a step lights the path from the start of the conversation to that step.
    • Without a script the same diagram remains as a static picture.
  23. 0.6.2

    Site

    Investor contact, the browser mark, and the header now use their quieter dedicated forms.

    • The investor sections now open a dedicated contact address.
    • The browser tab uses the four-stripe small Chawo mark.
    • Early access remains in the header as a navigation-weight link without a filled plate.
  24. 0.6.1

    Site

    Published pages now keep both channel-name locales when existing content is refreshed.

    • Existing pages accept newly added required block fields without being recreated.
    • English and Russian channel names stay attached to the same channel row.
    • Refreshing committed content replaces an editor change only when overwrite is requested.
    • The content check now compares a fresh import with an update of existing content.
  25. 0.6.0

    Site

    The first screen now frames Chawo as chat management and automation.

    • The headline names chat management and automation in one compact statement.
    • Five channel inputs meet one editable flow, with a written status beside every input.
    • The flow uses ports, curved connections, and a dotted editor canvas across the first screen.
    • On narrow screens, the canvas moves below the copy and keeps its labels readable.
  26. 0.5.0

    Site

    The Chawo mark now names the site in its header, footer, and browser tab.

    • The striped Chawo mark replaces the temporary text wordmark in the header.
    • The footer places the Chawo logo with the product credit.
    • The browser tab now uses the canonical small Chawo mark.
    • Every size keeps one coral stripe in both color schemes.
  27. 0.4.2

    Site

    Runs of fact sections now change surface and pair each heading with its explanation.

    • Consecutive fact sections now move through page, panel, and inverse zones.
    • On wide screens, each heading sits beside its explanation; on narrow screens, the pair stacks in reading order.
    • Explanations use a type step between body text and a page lead.
    • Product limits now place each refusal in its own definition block.
  28. 0.4.1

    Site

    The footer gained a brand mark, and the not-found page gained a themed illustration.

    • The footer places a brand mark beside its text label.
    • The error illustration adapts to the dark and light themes without client-side JavaScript.
    • A generated asset manifest records the source plugin, its version, and the generation date.
    • Verification compares every published brand asset byte for byte with the plugin source.
  29. 0.4.0

    Site

    Editors can now place uploaded images in page layouts while preserving localized descriptions and existing page changes.

    • An image block keeps the uploaded file’s proportions, alternative text, and optional caption.
    • Each image can follow the content container or fill the width of its page zone.
    • Translator access is limited to non-default locales.
    • Seed updates can target globals, pages, releases, or media separately.
  30. 0.3.1

    Site

    Prices, capability status, questions, exchanges, and the first-screen flow now have distinct visual structures.

    • The home page now shows the three published launch prices beside the boundary that nothing is for sale today.
    • Capability status leads a two-column register instead of sitting as a small label.
    • Questions use two columns, and the example exchange makes the handover the visible turning point.
    • The first-screen flow and its Russian decision label have more room.
  31. 0.3.0

    Site

    The site now has distinct page zones, larger headings, square-cornered cards, and interaction states for its controls.

    • Background changes separate each page into distinct visual zones.
    • Large headings set the reading order at the start of each page.
    • Cards use flat surfaces and square corners in place of the previous soft shapes.
    • The site has a dedicated mobile menu, and controls show hover and pressed states.
  32. 0.2.1

    Site

    Russian flow labels now stay inside their nodes on the home-page canvas.

    • The call, follow-up, and qualification labels now wrap at word boundaries.
    • Each label keeps its full wording while fitting the node that owns it.
  33. 0.2.0

    Site

    The site now publishes Russian pages, chrome, release notes, and locale-specific status.

    • Russian pages keep the English document structure while carrying their own copy.
    • The language switch links the same published page without client-side JavaScript.
    • Payload publishes English and Russian locale status independently.
    • The copy gate checks Russian vocabulary and catches English field fallback.
  34. 0.1.8

    Site

    The site now records its changes on this page, and screenshot checks compare exactly.

    • This page lists each site update by date and version.
    • Each entry names the changes included in that version.
    • Release notes now appear alongside the site’s other published pages.
    • Screenshot checks now compare exactly.
  35. 0.1.7

    Site

    The product page corrected two boundary statements, and non-canvas hero leads regained their earlier measure.

    • The product page now names the delivery and model-call boundaries from the capability register.
    • The home page keeps its title within the 60-character limit.
    • Non-canvas hero leads now use the measure from before the home redesign.
    • The desktop end-to-end check guards that measure.
  36. 0.1.6

    Site

    The site added comparison pages for Salebot and Jivo with sourced capability rows.

    • The Salebot page traces each comparison row to its published source.
    • The Jivo page distinguishes its website widget from Chawo’s roadmap widget.
    • Localized block fields supply the comparison labels and source links.
    • The footer now links both pages under Compare.
  37. 0.1.5

    Site

    Payload became the site content source, with early-access submissions, redirects, and authenticated preview.

    • The develop server reads published pages and globals from Payload.
    • The seed adds absent pages, forms, and globals while preserving editor changes.
    • The early-access form records submissions without client-side JavaScript.
    • Payload records now drive redirects and authenticated draft previews.
  38. 0.1.4

    Site

    The site gained its Payload foundation, admin route, reusable blocks, seed, and source parity.

    • The Payload admin route exposes page, media, user, and global schemas.
    • Pages reference nineteen reusable blocks through the shared block field.
    • Published pages remain identical while editors move content into Payload.
    • Publish hooks validate copy and revalidate page and index routes.
  39. 0.1.3

    Site

    The home page gained a first-screen flow canvas, progressive motion without JavaScript, and a ten-block reading order.

    • The home page drops four blocks and keeps a ten-block reading order.
    • Wide screens place the flow canvas beside the hero copy, while phones place it below.
    • CSS runs the flow motion and removes it when the reader requests reduced motion.
    • The no-script page preserves the same text and canvas.
  40. 0.1.2

    Site

    The repository gained the Payload content schema for pages, blocks, localization, and publishing.

    • The database design maps eight collections, three globals, and nineteen reusable blocks.
    • One locale dictionary and a shared block order govern every field.
    • The schema specifies page validation, previews, migrations, and source parity.
    • The dependency manifest pins Payload packages to version 3.88.0.
  41. 0.1.1

    Site

    The home page now names chat bots, broadcasts, chat automation, AI, and Telegram in its first screen.

    • The hero eyebrow carries the category terms above the handover claim.
    • The first-screen heading locates the bot-to-person handover on the canvas.
    • The lead ties each stated capability to its register status.
    • The footer mirrors the category language from the first screen.
  42. 0.1.0

    Site

    The site reframed Chawo around three named pillars and documented the work ahead.

    • The mission names the three product pillars and the seams they cover.
    • The roadmap keeps planned work and decisions that need an owner in one place.
    • CSS treats motion as progressive enhancement and removes it for readers who request reduced motion.
    • Each published update carries a version that the running site reports.