A chat survey looks like a conversation, not a form. A trigger tab sits in a corner of the page —
the same tab a popup form has — and clicking it
opens a chat card. The survey asks one question at a time, the visitor answers with a tap on an
option or a short message, the answer stays in the thread as their own bubble, and the next question
appears below it. After the last answer comes a thank-you, and every answer is sent in one request,
exactly like any other type.
An open chat card: the first question answered with a chip, the second waiting for a text answer.
Use cases
Short mood checks of two to five questions — "How was it today?", "What could we improve?" — where
a ten-field form would scare people off.
A first hello: a couple of questions to a new visitor about what brought them here.
Right after a checkout or a support request — a quick word while the impression is fresh.
Any survey where a friendly tone matters more than density: questions read as lines in a chat, not
as a questionnaire.
Questions instead of steps
A chat has no steps. In the editor the Steps section is replaced by Questions: a flat list
whose order is the order of the conversation. Add and drag questions the way you add fields to any
other survey; the field types are the same ones from the shared
catalog.
The Questions section and the live preview of the card.
How a question looks in the chat depends on its type:
One option out of several (single choice, dropdown, yes/no, rating, a scale) — the options are
shown as chips; a tap sends the answer at once and brings the next question.
Several options (multiple choice) — the same chips, but picked ones stay highlighted and the
send button confirms the choice.
Text, email, number, link — a composer line at the bottom of the card, like a messenger's;
Enter sends.
Every other type (date, slider, matrices, ranking, contact form…) — shown as the widget's
regular field with a button under it.
Text blocks and sections — arrive as a message from the survey; the visitor just presses
"Next".
An optional question can be skipped with the Skip link under the answer — the thread then shows
"Skipped" in place of an answer. The last question has no such link: if it's optional, pressing the
send button with nothing entered is enough.
Configuration
The trigger tab — its label is set in Form copy (the
"Button text" field), its position in Styles: the "Bottom right" and "Right" presets, or offsets
in pixels. The chat card opens on the same edge the tab is attached to. A chat has no "Back"
button — the conversation never returns to an answered question — so no text is asked for it.
Header and thank-you — the form title is shown in the card's header, and the success title and
message become the last bubble of the conversation. With the welcome screen enabled, its text is
the first message and the "Start" button is the first chip.
When to show it — the same conditions as a popup's: a delay, a click on an element of your
page, a returning or leaving visitor, the end of the page, every Nth visitor, a cookie. All of them
are described under Settings. While no condition is enabled,
the chat opens only from its tab.
Language switcher for the visitor — a switch in the card's header, when enabled in the
settings.
Block duplicate submissions — after answering, the visitor only sees the thank-you in the
card.
Look — the survey's theme (Attributes) sets the colours
of bubbles and chips; for fine-tuning, Advanced Styles
has its own slots: the card, the avatar, the survey's and the visitor's bubbles, chips, the
composer, the "Skip" link.
Embedding — the same script as a popup form: see step 5 of the
quick start.
Steps display and progress indicators don't apply to a chat and are hidden in the editor. Creating a
chat with AI isn't available yet.
Publishing requirements
As with a popup form, the button text must be filled in for every one of the domain's locales —
a hard error. The main evaluation question and the main feedback text are only recommended here:
their absence is a non-blocking warning, as with an inline form.