For the complete documentation index, see llms.txt. This page is also available as Markdown.

Diary and recurring studies

Run a diary or recurring study on WhatsApp, choose between a logging menu and scheduled daily activities, and avoid the common traps.

A diary study asks participants to report on the same behaviour or experience repeatedly over days or weeks, inside their WhatsApp chat. Use it to capture behaviour close to the moment it happens: meals, shopping trips, media use, product trials, commutes or moods.

In short:

  • There are two ways to build a diary. A Recurring Survey lets participants log an entry whenever something happens, from a menu. A multi-activity study sends a different activity each day on a schedule.

  • For day-by-day diaries, one activity per day gives the cleanest data and reporting.

  • Participants cannot catch up on a missed day by doing two the next day. Plan reminders and your qualifying rule around that.

Choose your structure

Recurring Survey (logging menu)
Multi-activity study (one activity per day)

Who starts each entry

The participant, whenever the behaviour happens

Yazi, at the time you schedule

Questions

The same short set each time

Can change day to day, and mix methods

Best for

Event-based logging ("every time you see an ad")

Structured journeys ("Day 1 baseline, Days 2 to 6 diary, Day 7 interview")

Results

One row per entry, many per participant

One set of results per activity, linked by participant

Analysis

Simple to build, harder to analyse over time

More set-up, easier to segment and compare by day

You can combine both: for example, a multi-activity study where one activity is a recurring logging survey and a later activity is an AI interview. For how scheduling, invites and progression work, see Multi-activity studies.

Recurring Survey: the logging menu

In a Recurring Survey the first question works as a home screen: a menu of the things a participant can log. Each menu option routes to its own short set of questions (a "journey"), and each journey ends by returning the participant to the menu, ready for the next entry.

Example: a social media diary

  • Menu question: "What would you like to log?" with options Scrolling session and End of day reflection.

  • Scrolling session routes to four questions: which apps, what they did, how long, and whether anything made them stop.

  • End of day reflection routes to three slightly longer questions.

  • The last question of each journey routes back to the menu.

Every completed journey is recorded as a separate entry (one row) with its own timestamp, linked to the participant. One person can produce dozens of entries over a study.

1

Create the study

Click + New Research, choose Build manually and pick Recurring as the research method. You can also add a Recurring Survey as an activity inside a multi-activity study.

2

Build the menu

Make the first question a single-select listing the activities to log. Keep it to 3 to 6 clearly different options in the participant's own words.

3

Build each journey and route it

Add each journey's questions. Use routing on the menu so each option goes to the first question of its journey, and on the last question of each journey route back to the menu. See Logic and routing.

4

Set the recurring options and test the loop

Open Study configuration > Recurring survey. Set the maximum number of entries (leave it empty for unlimited), whether the survey restarts automatically after each entry, the cooldown in minutes before the next entry, and the message sent when an entry is complete. Then run through the menu and every journey in the Test Simulator to make sure each journey returns to the menu.

Study configuration > Recurring survey: maximum entries, auto-restart after each entry, the cooldown between entries and custom messages

Multi-activity diary: one activity per day

For a diary that runs Day 1, Day 2, Day 3 and so on, create a multi-activity study with one activity per day (or per task within a day). Each day can have different questions, and each activity opens on the schedule you set, for example 9am the next day.

Compared with one recurring activity that loops, separate daily activities are easier to segment, track and report on per day, which makes longitudinal analysis cleaner. The trade-off is more set-up.

Each scheduled day arrives as a WhatsApp invite (an approved template with a Continue button). The day's first question is sent when the participant taps Continue. If a participant finishes a day late at night, the next day still opens at its scheduled time.

A diary study check-in on WhatsApp, answered with a voice note

See Multi-activity studies for the full set-up and progression rules.

Catch-up rules

On a scheduled diary:

  • One activity per day. A participant gets each day's activity in turn.

  • No doubling up. A participant who misses a day cannot complete two days' activities the next day.

  • Waiting, not skipping. Someone who has not finished the current day is not skipped ahead. When they finish, the next activity opens at its scheduled time, or straight away if that time has already passed.

This is the single biggest factor in how a long diary needs to be run. Expect to send reminders through the week, and set your qualifying rule (how many days count as a complete diary) around what your audience can realistically do.

Help participants keep going

  • Label every activity by day and position, for example "Day 1, activity 2 of 3", so participants know what is still outstanding. Without this, people do not realise there is more than one task per day and miss answers that cannot be repeated.

  • Ask participants to pin the chat in your opening message, so the study stays at the top of their WhatsApp list.

  • Keep each entry short: 3 to 6 questions, 2 to 5 minutes. Put the most important question first in every journey.

  • Use photos and voice notes instead of long typed answers. They are richer and quicker for the participant. Ask for one message per answer, and tell participants how to send several photos.

  • Keep the completion message on. Participants get a short confirmation at the end of each activity before the next one begins, which reassures them the entry counted.

  • Set reminders for people who have not logged or finished. See Reminders.

  • Probe sparingly. Daily AI follow-ups on top of a daily task cause fatigue. A weekly reflection with AI probing usually works better than probing every day.

Setting a qualifying rule

How many entries or days count as a complete diary is a study design decision, not a platform setting. Base it on what your audience can do. On a 21-day diary, a rule such as "at least 4 activities a week, including at least one weekday and one weekend day" may be more realistic than 21 out of 21, especially for audiences who cannot afford data every day. Paying incentives in weekly batches, rather than one payment at the end, also helps retention.

Results

  • Table Data shows one row per completed entry or activity, with a timestamp. Frequent loggers produce many rows, so plan your analysis structure before fieldwork.

  • Graph Data charts every question type for recurring studies.

  • The Share tab shows where each participant is in the study, with a per-activity progress bar.

  • On a multi-activity diary, open any participant on the Share tab and use View transcript to read each activity they took part in.

See Results overview.

Limits and things to know

  • WhatsApp's 24-hour window. If a participant has not messaged in the last 24 hours, Yazi can only reach them with an approved template. Scheduled days always start with an approved invite for this reason. See WhatsApp costs and the 24-hour window.

  • Testing single days. Links to an individual activity only work once the study is live, so testers must start at Day 1. See Test your study.

  • Messages between days are kept. If a participant sends something between two activities, Yazi stores it and tells them they are still taking part and will hear when the next activity is ready.

  • Menu labels must be short. The menu shows as a WhatsApp list, so long labels are cut off. See WhatsApp limits.

  • Billing counts rounds, not days. How long a diary runs does not by itself change what it costs. See Plans, billing and usage.

Last updated