> For the complete documentation index, see [llms.txt](https://docs.saas.haut.ai/haut.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saas.haut.ai/haut.ai/releases/changelog/version-2026-22.md).

# Version 2026-22

## Release date

May 26, 2026

## Consumer Apps

### Survey and Klaviyo improvements

Consumer App surveys now support richer contact collection and consent handling for CRM workflows.

* Added **Full name** and **Phone number** survey question types. Full name collects first and last name separately, and Phone number uses a dedicated phone input. Learn more: [Add and Customize Survey into Consumer App](/haut.ai/haut.ai-features/consumer-apps/add-and-customize-survey-into-consumer-app.md).
* Added WhatsApp transactional and marketing consent collection for Klaviyo-connected Consumer Apps. This helps brands collect the consent needed for service-related and marketing WhatsApp messages.
* The Klaviyo **Skin Analysis Complete** event now includes survey answers, including Email, Phone number, Full name, and other survey questions when configured. This enables audience segmentation and flow automation based on survey responses. Learn more: [Data Sent to Klaviyo](/haut.ai/quick-start-guides/no-code-app-for-e-commerce-businesses/integrate-consumer-app-with-klaviyo-crm/data-sent-to-klaviyo.md).
* No integration changes are required for existing Klaviyo flows. Brands can optionally update Klaviyo segments and automation logic to use the new survey answer fields.

### Analytics

* Added PostHog analytics integration for Consumer Apps.
* Improved the SkinGPT experience inside Consumer Apps when only one image is available.

### Hair Consultant App

* Fixed the **Show less / Show more** control so it no longer appears for short concern descriptions.

## SkinGPT

* The compare mode toggle for Effects is now enabled by default for all companies. Learn more: [SkinGPT Overview](/haut.ai/haut.ai-features/skingpt.md) and [Effects Library](/haut.ai/haut.ai-features/skingpt/effects-library.md).

## Studies

* Removed the quality check toggle from Studies. All Studies now enforce strict LIQA quality check mode, and this mode cannot be disabled. Learn more: [Studies](/haut.ai/haut.ai-features/studies.md) and [LIQA](/haut.ai/haut.ai-features/liqa.md).

## Authentication

* Fixed a Google authentication callback issue that could interrupt login during OAuth session restore. Learn more: [Login and authentication](/haut.ai/administration/login-and-authentication.md).

## API

* Added an endpoint for batch deletion, enabling manual removal of a batch's results and images. This is an opt-in API action for cleanup workflows; no customer action is required unless you want to use the new endpoint.

***

{% hint style="warning" %}
Not a Haut.AI client yet?
{% endhint %}

<a href="https://haut.ai/book-a-demo?utm_source=referral&#x26;utm_medium=saas_docs&#x26;utm_campaign=Docs_SaaS_HautAI" class="button primary" data-icon="user-vneck">Book a demo</a> <a href="https://haut.ai/product/ai-skin-analysis?utm_source=referral&#x26;utm_medium=saas_docs&#x26;utm_campaign=Docs_SaaS_HautAI" class="button secondary" data-icon="external-link">Platform overview on haut.ai</a>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.saas.haut.ai/haut.ai/releases/changelog/version-2026-22.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.