> For the complete documentation index, see [llms.txt](https://docs.askyazi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.askyazi.com/build-a-study/in-chat-vs-whatsapp-flows.md).

# In-chat vs WhatsApp Flows

Understand the two ways a Yazi survey appears on WhatsApp, in-chat messages or a WhatsApp Flow form, and choose the right one for each part of your study.

A Yazi survey can reach participants in two ways. **In-chat** sends one WhatsApp message per question, like a conversation. A **WhatsApp Flow** opens a form inside WhatsApp that shows one or more questions per screen, with tick boxes and a **Next** button. This page explains the difference and when to use each.

{% hint style="info" %}
**In short:** in-chat works for every question type and every WhatsApp number. Flows are quicker to complete and usually cost less to send, but cannot take voice notes, video or location, need a Meta-verified number, show only on phones, and handle logic at the end of each screen rather than per question. In a multi-activity study you can mix the two.
{% endhint %}

## What the participant sees

Here is the same four-question survey sent both ways.

{% columns %}
{% column width="50%" %}
**In-chat survey**

Each question arrives as its own WhatsApp message, and the participant answers in the chat: they tap a button, pick from a list, type a reply, or send a photo, voice note or video. Their answers sit in the conversation like any other chat, and they can stop and pick up exactly where they left off, even days later.

<figure><img src="https://358667285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzMRQUXiGQlBwWdg6WEmG%2Fuploads%2FELv0ciMzHErTCRgzbNBb%2Fph-inchat-chat.webp?alt=media&amp;token=57f0f428-2e28-44b3-90e3-3e4d959de09c" alt="An in-chat survey on WhatsApp: each question arrives as its own message and the participant replies in the chat"><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="50%" %}
**Flow-based survey**

The participant gets one message with a button (**Continue** by default). Tapping it opens a form over the chat. Questions sit on screens with radio buttons and tick boxes, a progress line and **Question 2 of 4** at the top, and **Next** and a back arrow to move through. Answers on a screen are saved when the participant finishes that screen.

<figure><img src="https://358667285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzMRQUXiGQlBwWdg6WEmG%2Fuploads%2FavezW19PAxOMQID4rIjl%2Fph-flow-screen.webp?alt=media&amp;token=23d372c3-0e6f-452e-942e-3a4c24be00f6" alt="A Flow-based survey: the questions open as a WhatsApp form, one screen at a time, with Back, progress and Next"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column width="50%" %}

<figure><img src="https://358667285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzMRQUXiGQlBwWdg6WEmG%2Fuploads%2FbOhA2aqRSGtwj8idVIVr%2Fph-inchat-form.webp?alt=media&amp;token=7d8a667a-5b6c-409e-8b9d-55d9fdd8326f" alt="In an in-chat survey, a multi-select question opens a small form for that one question, then the chat carries on"><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="50%" %}
**Forms inside an in-chat survey.** Even in an in-chat survey, some question types open a small form for that one question: Multi Select, Matrix, Rating Scale and NPS arrive as a **View question** button that opens a tick-box or grid form. The participant taps **Submit**, their choices appear in the chat as a reply (for example "Dashboard, Reports"), and the next question arrives as a normal message.

The difference from a Flow-based survey is that the form covers one question only. In a Flow-based survey the whole survey runs in the form.
{% endcolumn %}
{% endcolumns %}

## Choose the format

Open **Build > Study configuration > Participant experience** and pick a **Builder Mode**:

* **In-chat survey**
* **Flow-based survey**
* **Live Form** (a web form participants open from a link, with a WhatsApp-style chat). This is early access. See [Live Forms](https://docs.askyazi.com/study-types/live-forms.md).

<figure><img src="https://358667285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzMRQUXiGQlBwWdg6WEmG%2Fuploads%2Fx7SCQ8Bu4kox4KSdHANf%2Ffs-participant-experience.webp?alt=media&amp;token=3644293d-feeb-49f8-9013-49b5a1220eba" alt="Study configuration > Participant experience: choose In-chat survey, Flow-based survey or Live Form, and the study language"><figcaption></figcaption></figure>

If **Flow-based survey** is greyed out, the study contains a question type a Flow cannot show. Hover over it to see why.

When you choose **Flow-based survey**, a **Flow Configuration** section appears under the builder modes:

* **Call-to-Action Message**: the chat message that comes with the button, for example a consent line.
* **CTA Button Text**: the label on the button that opens the form (**Continue** by default).
* **Show welcome screen** and **Welcome Message**: an optional intro screen at the start of the form. Turn it off and the form opens straight on the first question.

<figure><img src="https://358667285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzMRQUXiGQlBwWdg6WEmG%2Fuploads%2Fam1tkdh1Phl7cYJIDImt%2Ffs-flow-config.webp?alt=media&amp;token=961c4313-e6c8-4c23-bd05-b687a24450e3" alt="Flow-based survey selected: Flow Configuration sets the message and button that open the form, and an optional welcome screen"><figcaption></figcaption></figure>

Switching mode asks you to confirm. Moving to **Flow-based survey** warns that some question and block logic may not carry over, so review your logic afterwards. Moving back to **In-chat survey** clears the Flow welcome message and button text.

## Side-by-side comparison

<i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes** means it works, <i class="fa-circle-half-stroke" style="color:$warning;">:circle-half-stroke:</i> **Partly** means it works with limits, and <i class="fa-circle-xmark" style="color:$danger;">:circle-xmark:</i> **No** means it is not available.

|                                             | In-chat                                                                                                                                                      | WhatsApp Flow                                                                                                                                                 |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| What the participant sees                   | One WhatsApp message per question                                                                                                                            | A form that opens over the chat, one screen at a time                                                                                                         |
| Speed for the participant                   | Conversational pace                                                                                                                                          | Faster, especially for long closed-question surveys                                                                                                           |
| Single Select and Multi Select              | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes** Lists and buttons in the chat; Multi Select opens a tick-box form per question | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes** Radio buttons and tick boxes on the screen                                      |
| Voice notes, video and location answers     | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes**                                                                                | <i class="fa-circle-xmark" style="color:$danger;">:circle-xmark:</i> **No** The Flow option greys out                                                         |
| Photos and documents                        | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes**                                                                                | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes**                                                                                 |
| Matrix questions                            | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes**                                                                                | <i class="fa-circle-xmark" style="color:$danger;">:circle-xmark:</i> **No**                                                                                   |
| An image shown with a question              | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes** Sent as a message above the question                                           | <i class="fa-circle-half-stroke" style="color:$warning;">:circle-half-stroke:</i> **Partly** Check how it appears in the Test Simulator before you rely on it |
| Logic and routing                           | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes** Per question: skip to, screen out, Only show if                                | <i class="fa-circle-half-stroke" style="color:$warning;">:circle-half-stroke:</i> **Partly** At the end of each screen, forward only, plus Only show if       |
| Going back to the previous question         | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes** With a **Back** button, where you allow it                                     | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes** The back arrow on each screen                                                   |
| Leave and come back later                   | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes** Resumes at the exact question                                                  | <i class="fa-circle-half-stroke" style="color:$warning;">:circle-half-stroke:</i> **Partly** Answers save per screen; a half-finished screen is lost          |
| Randomise answer options                    | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes**                                                                                | <i class="fa-circle-half-stroke" style="color:$warning;">:circle-half-stroke:</i> **Partly** On single-form Flow surveys                                      |
| Piping an earlier answer into question text | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes**                                                                                | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes**                                                                                 |
| Piping answer options or matrix rows        | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes**                                                                                | <i class="fa-circle-xmark" style="color:$danger;">:circle-xmark:</i> **No**                                                                                   |
| WhatsApp Web and desktop                    | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes**                                                                                | <i class="fa-circle-xmark" style="color:$danger;">:circle-xmark:</i> **No** Phones only                                                                       |
| Any connected WhatsApp number               | <i class="fa-circle-check" style="color:$success;">:circle-check:</i> **Yes**                                                                                | <i class="fa-circle-xmark" style="color:$danger;">:circle-xmark:</i> **No** Needs a number verified and approved by Meta                                      |
| Message cost                                | Usually higher                                                                                                                                               | Usually lower. The cost estimate before publishing shows the difference                                                                                       |

## Decision guide

Use **in-chat** when:

* you need voice notes, video or location answers;
* the study is an AI interview, a diary or anything qualitative;
* participants may answer over several sittings;
* your WhatsApp number is new or not yet verified by Meta;
* you rely on piping answer options or matrix questions.

Use a **Flow** when:

* the survey is mostly closed questions and you want it fast and tidy;
* your number is verified and Flow-eligible;
* your participants use WhatsApp on their phones;
* you want the lower message cost the estimate shows.

Mix both when a study needs some of each. In a multi-activity study each activity has its own format: for example a Flow screener and baseline survey, then an in-chat activity for voice notes and an AI interview. When you add an AI interview activity, you can also pick whether the short survey before the interview runs in-chat or as a Flow. See [Multi-activity studies](https://docs.askyazi.com/study-types/multi-activity-studies.md).

## How Flows group questions: blocks

In a Flow, each **block** is one screen. Create blocks in **Study configuration > Blocks** and drag questions into them. Questions not in a block get a screen each.

* The block name becomes the screen title, up to 30 characters.
* Each block can show all its questions at once or reveal them one after another as the participant answers.
* Click the eye icon on a block to preview it as a real Flow screen.
* Routing sits on the block: after this screen, if the answer is X, skip ahead, screen the participant out, or end the survey. Routing only moves forward, because that is all WhatsApp allows.

Per-question skip logic cannot fire between two questions on the same screen, because the participant sees them together. Use **Only show if** for questions that should only appear for some people, or put the follow-up on the next screen. See [Logic and routing](https://docs.askyazi.com/build-a-study/logic-and-routing.md).

If a Flow survey is too complex to build (for example a very long chain of follow-up questions), the builder names the questions causing the problem rather than failing silently.

## Cost

Before you publish or update a study, Yazi shows what Meta will charge for the WhatsApp messages, split into the broadcast invite and the survey questions. Where the study could run as a Flow, the estimate offers a one-click switch to the Flow format and shows the saving. Questions that cannot use a Flow are called out. Estimates use real rates for a growing list of markets and say clearly when they are approximate. See [WhatsApp costs and the 24-hour window](https://docs.askyazi.com/reach-participants/whatsapp-costs-and-the-24-hour-window.md).

## Testing each format

The Test Simulator shows the real Flow screens for a Flow survey, and in-chat questions as chat bubbles, so test the format your participants will get. **Run Simulation** also walks Flow screens the way a phone does. Always do a final check on a real phone. See [Test your study](https://docs.askyazi.com/study-types/test-your-study.md).

## Limits and things to know

{% hint style="warning" %}
**Do not switch a live study between in-chat and Flow.** Participants partway through can be left on the wrong format or receive nothing. Decide the format before you go live. If you must change it, pause the study, change it, test it, then resume.
{% endhint %}

* **Converting in-chat to Flow can lose question-level logic** between questions that end up on the same screen. Recheck the **Logic Map** after any change.
* **Flows need a verified, eligible number.** A brand-new number may only support in-chat at first. See [Business verification](https://docs.askyazi.com/set-up-whatsapp/business-verification.md).
* **Flows show on phones only.** Participants on WhatsApp Web or desktop cannot open them.
* **No partial save inside a screen.** Long blocks risk losing answers if someone closes the form halfway. Keep blocks short.
* **Voice notes, video and location are in-chat only.**

## Related

* [Question types](https://docs.askyazi.com/build-a-study/question-types.md)
* [WhatsApp limits](https://docs.askyazi.com/build-a-study/whatsapp-limits.md)
* [Logic and routing](https://docs.askyazi.com/build-a-study/logic-and-routing.md)
* [Surveys](https://docs.askyazi.com/study-types/surveys.md)
* [Publish and go live](https://docs.askyazi.com/study-types/publish-and-go-live.md)
