%202.png)
TL;DR
The WhatsApp Business API lets researchers run surveys, diary studies, and AI-moderated interviews at scale through WhatsApp, but setup involves specific infrastructure, messaging rules, and compliance requirements that differ from typical marketing use cases. This guide defines every key concept through a research lens, explains the constraints that shape study design (like the 24-hour messaging window and template approvals), and covers the build-versus-buy decision most research teams face. If you want to skip the technical overhead entirely, purpose-built platforms handle the API layer so you can focus on research design.
Why Researchers Need a Different API Guide
Every existing guide on how to set up WhatsApp Business API for research is, frankly, not about research at all. The top-ranking pages cover customer support chatbots, marketing automations, and e-commerce notifications. They explain templates in terms of order confirmations and promotional blasts, not survey invitations or diary study prompts.
Researchers face different questions. Which template category should a study participation request fall under? How does the 24-hour messaging window affect a seven-day diary study? Can your ethics board approve Cloud API data handling, or do you need on-premises hosting with EU data residency?
This glossary answers those questions. Every term is defined through the lens of surveys, qualitative interviews, and longitudinal research, not marketing campaigns.
The evidence for WhatsApp as a research channel is strong. A randomized experiment by the Immigration Policy Lab and Innovations for Poverty Action in Colombia found that WhatsApp surveys achieved a 55% response rate, outperforming IVR by 12 percentage points and SMS by 27 percentage points. WhatsApp messages carry open rates near 98%, compared to the roughly 10% response rates many teams get from email surveys.
But capturing those gains requires understanding the API infrastructure underneath. Here’s every concept you need to know.
Core Infrastructure Terms
WhatsApp Business API
The WhatsApp Business API is a programmatic interface that lets organizations send and receive WhatsApp messages at scale through software rather than manual typing. Introduced by Meta in August 2018, it was built for medium and large businesses, but its capabilities map perfectly to research operations: automated question delivery, response collection, media capture, and integration with data processing tools.
The API differs from the free WhatsApp Business App in fundamental ways. The app is designed for a single person managing a small business from their phone. The API has no front-end interface of its own. Instead, it connects to external systems (survey platforms, CRM tools, custom-built pipelines) that handle the logic of what gets sent and when.
For research, this means you can programmatically send survey questions one at a time, collect voice notes and images as responses, trigger follow-up prompts based on answers, and export structured data, all within WhatsApp’s familiar chat interface. You can learn more about designing chat-friendly questions that work well in this format.
WhatsApp Business Account (WABA)
A WABA is the container that holds your phone number(s), message templates, and messaging settings within Meta’s infrastructure. Think of it as your organization’s identity on WhatsApp’s business platform.
You need at least one WABA to use the API. Within it, you can register phone numbers, submit message templates for approval, and configure messaging limits. For research organizations running studies across multiple countries, it’s possible to manage several phone numbers under a single WABA.
Cloud API vs. On-Premises API
Meta offers two hosting options for the WhatsApp Business API. The choice between them matters more for researchers than for most commercial users, because ethics boards care about where participant data lives.
Cloud API is hosted on Meta’s servers. Setup is dramatically faster (minutes instead of weeks, according to Meta). It has achieved SOC 2 Type II and ISO 27001 certifications. The tradeoff: message data passes through Meta’s infrastructure, which means you need Standard Contractual Clauses (SCCs) for cross-border data transfers under GDPR.
On-Premises API runs on your own servers or those of your hosting provider. It gives you direct control over data residency, making it easier to satisfy ethics boards that require data to stay within the EU or South Africa. The cost is higher technical complexity and ongoing maintenance.
For most research teams, the practical choice is to use a Business Solution Provider or research platform that handles this decision for you, offering configurable data residency without requiring you to manage server infrastructure.
Meta Business Portfolio (Business Manager)
This is the admin hub where all your business assets live: your WABA, ad accounts, pages, and user permissions. You need a Meta Business Portfolio before you can access the WhatsApp Business API. It’s also where you initiate Meta Business Verification (covered below).
If your university or research agency already runs Facebook ads or manages a Facebook Page, you likely have a Business Portfolio already. If not, creating one is free but requires a Facebook account with admin access.
Business Solution Provider (BSP)
A BSP is a company that Meta has authorized to provide access to the WhatsApp Business API. BSPs handle the technical infrastructure: webhook servers, message routing, template management, and policy compliance.
Using a BSP means you don’t have to build and maintain the plumbing yourself. This matters because the bare API requires you to manage webhook servers for incoming messages, submit and track template approvals, handle rate limiting, and stay current with Meta’s evolving policy requirements.
Practitioners on Reddit’s r/WhatsappBusinessAPI frequently discuss BSP selection, and the recurring theme is that going direct (without a BSP) only makes sense if you have a dedicated engineering team. For research organizations, the question is really whether to use a general-purpose BSP or a platform purpose-built for research that includes BSP functionality alongside survey logic, data analysis, and compliance features. You can see how Yazi’s setup works as an example of the latter approach.
Webhook
A webhook is a mechanism that pushes data from one system to another in real time. In the context of WhatsApp Business API, webhooks deliver incoming messages (participant responses) to your server or platform the moment they arrive.
When a participant answers a survey question or sends a voice note, the WhatsApp API fires a webhook containing that message data to your configured endpoint. Your system then processes the response, stores it, and triggers the next question if applicable.
If you’re building a DIY setup, configuring webhooks correctly is critical and error-prone. If you’re using a research platform, this is handled automatically.
Setup and Verification Terms
Meta Business Verification
Meta Business Verification confirms that your organization is a real, legally registered entity. It’s required to unlock higher messaging limits and is a prerequisite for applying for the green tick (Official Business Account status).
The process requires submitting legal documentation: business registration certificates, utility bills, or tax documents that match your organization’s name and address. The key practical insight is that Meta’s reviewer needs to see the exact same legal business name across your website, your submitted documents, and your Meta Business Portfolio.
What researchers need to know: You can start sending messages while unverified, but you’re capped at 250 business-initiated conversations per rolling 24-hour period. For a pilot study with a small sample, that might be fine. For anything larger, complete verification first.
One common blocker: Meta requires a business website with live terms and conditions and privacy policy pages on your domain. Academic departments and research labs sometimes lack these. Get them published before you apply.
Phone Number Registration
To use the WhatsApp Business API, you need a dedicated phone number. This number becomes your research project’s identity in participants’ WhatsApp chats.
A critical constraint that trips up many first-time users: you cannot use the same phone number on both the WhatsApp Business App and the API simultaneously. Registering a number for the API disconnects it from the app. If your organization currently uses a WhatsApp Business App for other purposes, you’ll need a separate number for API-based research.
The number can be a mobile or landline number. It must be able to receive either an SMS or a voice call for verification during setup.
Coexistence Feature
As of 2026, Meta’s Coexistence feature allows eligible businesses to continue using the WhatsApp Business App while also connecting the same number to the Cloud API for automation. This is new and not widely discussed in setup guides.
For research teams, this could be valuable: a project coordinator could use the app for ad-hoc participant communication while the API handles automated survey delivery on the same number. Check current eligibility requirements with your BSP, as Meta is rolling this out gradually.
Display Name Approval
Your display name is what participants see in the chat header when they receive messages from your research project. Meta must approve it, and it needs to match your verified business name or be a clear derivative of it.
For research credibility, this matters. Participants are more likely to engage with a recognizable institution name than a generic label. If your research lab operates under a university, use a name that makes that affiliation clear.
Official Business Account (Green Tick)
The green tick badge next to your display name signals to participants that Meta has verified your business identity. It’s a trust signal, and in research contexts, trust directly affects response rates.
Getting the green tick requires completed Meta Business Verification, at least 30 days of active API use, and a track record of quality messaging. It’s not guaranteed, but it’s worth pursuing for any ongoing research program.
Messaging Rules That Shape Research Design
This section covers the API constraints that most directly affect how you design and run studies. Understanding these rules before you build your research protocol will save significant time and budget.
Message Template
A message template is a pre-approved message format required by WhatsApp to initiate any conversation with a user. You cannot send the first message to a participant in free-form text. It must be a template that Meta has reviewed and approved.
Templates can include variables (like a participant’s name or a study title) and can contain text, images, documents, or interactive buttons. For research, your survey invitation, diary study prompt, or interview scheduling message will all be templates.
The practical challenge: templates cannot look promotional. Survey invitations that read like marketing (“Complete our exciting survey!”) risk rejection. Frame them as utility messages: “You’re invited to participate in [Study Name]. Reply YES to begin.” This improves approval odds significantly. Browse survey template examples for inspiration.
Template Categories
Meta classifies templates into four categories, and the category determines both the approval criteria and the per-message cost:
Marketing: Promotional content, offers, upsells. These are the most expensive. Research invitations should generally not fall here.
Utility: Transactional or informational messages related to an existing relationship. Study participation confirmations, appointment reminders, and survey status updates fit naturally. This is the sweet spot for most research templates.
Authentication: One-time passwords and verification codes. Rarely relevant for research unless you’re verifying participant identity.
Service: Responses within the 24-hour window (see below). These are free. This is where your actual survey questions, follow-ups, and conversational exchanges happen.
Choosing the right category is not just a compliance issue. It’s a cost issue. A 500-person study where every invitation is classified as marketing instead of utility could cost significantly more.
Template Approval Process
After you submit a template, WhatsApp typically reviews and approves it within minutes, though it can take up to 24 hours. Templates may be rejected if they violate WhatsApp’s policies, contain improper formatting, or include restricted content.
For research teams, common rejection reasons include: language that sounds promotional, missing opt-out instructions, or vague purpose descriptions. The fix is straightforward. Be specific about what the message is for, include a way for recipients to decline, and avoid exclamation marks or sales language.
Each WABA can hold up to 250 templates across all languages. For most research projects, you’ll need far fewer, but multi-country studies with multiple language versions can approach this limit. Learn more about setting up templates for studies.
24-Hour Messaging Window
This is the single most important API constraint for anyone figuring out how to set up WhatsApp Business API for research.
When a participant sends you a message, it opens a 24-hour window during which you can respond with free-form messages (no templates required, no per-message charges from Meta). Once that window closes, you can only re-initiate contact using an approved template message, which costs money.
What this means for survey design: If your survey has 20 questions delivered one at a time, and a participant stops responding after question 5, you have 24 hours from their last message to send the next prompt for free. After that, you need a paid template to pull them back in.
What this means for diary studies: A seven-day diary study requires keeping participants engaged within rolling 24-hour cycles. If a participant skips a day, you’ll need to send a template message (at cost) to re-initiate. Smart study design uses automated reminders within the window to keep it open.
What this means for budgeting: Studies with high dropout or slow responders will cost more because of repeated template re-initiations. Design your flow to encourage prompt responses.
Session Message
A session message is any free-form message sent within the 24-hour window. These can be text, images, videos, documents, or interactive elements. No template approval needed, no per-message charge from Meta.
For research, session messages are where the actual study happens. Your survey questions, probing follow-ups, diary prompts, and multimedia requests all flow as session messages, as long as the participant keeps responding within 24-hour intervals.
Business-Initiated Conversation
Any time you send a template message to start or restart a conversation (outside the 24-hour window), that counts as a business-initiated conversation. This is the action that triggers billing.
For research, every survey invitation, every reminder to a lapsed participant, and every new diary day prompt (if the window has closed) is a business-initiated conversation.
Compliance and Ethics Terms
Setting up WhatsApp Business API for research carries compliance requirements from two directions: WhatsApp’s own policies and data protection regulations like GDPR and POPIA. For academic researchers, there’s a third layer: institutional ethics board (IRB) approval.
Opt-In and Consent
WhatsApp requires documented consent from every recipient before you send any business message. This isn’t optional, and it applies regardless of whether the conversation is business-initiated or user-initiated.
For researchers, this is actually good news. WhatsApp’s opt-in requirement aligns naturally with informed consent, which ethics boards already require. The difference is that you need to document the opt-in mechanism in a way that satisfies both WhatsApp and your IRB.
Via the API, consent collection is fully automatable. A participant can tap a button or reply “YES” to confirm participation, and that interaction is logged with a timestamp. This creates a more robust consent record than most paper-based processes. For guidance on structuring this, see our article on pre-survey consent and screening.
GDPR Compliance
GDPR-compliant use of WhatsApp is possible exclusively through the WhatsApp Business API. The personal WhatsApp app and the free WhatsApp Business App violate GDPR due to metadata processing and automatic contact list uploads. This is not a gray area.
Compliance rests on five elements:
- A valid legal basis. For research, this is typically explicit consent (Article 6(1)(a)) or legitimate interest with a balancing test.
- A Data Processing Agreement (DPA) signed with Meta and with your BSP.
- An updated privacy notice that tells participants what data you collect, why, how long you keep it, and their rights.
- Procedures to answer data subject requests (access, deletion, portability) within 30 days.
- Appropriate security measures for data in transit and at rest.
Meta’s Cloud API holds SOC 2 Type II and ISO 27001 certifications, which helps when presenting your compliance case to an ethics board. For a deeper comparison between the two frameworks most relevant to African research, read our GDPR and POPIA comparison guide.
POPIA Compliance
South Africa’s Protection of Personal Information Act (POPIA) is the primary data protection framework for research conducted in or involving South African participants. Its requirements parallel GDPR in many ways: lawful basis for processing, purpose limitation, data minimization, and participant rights.
For WhatsApp-based research in Africa, POPIA compliance often requires South African data residency, which means your data must be stored on servers physically located in South Africa. This is where the choice between Cloud API and on-premises (or a platform with SA data residency) becomes critical.
Data Processing Agreement (DPA)
A DPA is a legally binding contract between your organization, your BSP, and Meta that governs how participant data is processed. It specifies what data is collected, how it’s used, retention periods, and security obligations.
You need DPAs in place before collecting any research data. Most BSPs and research platforms have standard DPAs ready for signing. If you’re building a DIY setup, you’ll need to negotiate these separately with Meta and any other service providers in your data chain.
Data Residency
Data residency refers to the physical location where your data is stored. For the Cloud API, data passes through Meta’s global infrastructure. For on-premises setups, data stays on servers you control.
Ethics boards at European and African universities increasingly require specific data residency guarantees. If your IRB needs data stored exclusively in the EU or South Africa, confirm this capability with your BSP or platform before committing to a setup approach. Yazi, for example, offers configurable EU or SA residency.
Encryption
Personal WhatsApp uses end-to-end encryption, meaning only the sender and recipient can read messages. The Business API works differently: Meta (for Cloud API) or your BSP (for on-premises) manages encryption keys on behalf of the business.
Messages are encrypted in transit and at rest, but they are accessible to the systems processing them (which is necessary for features like automated survey logic and response analysis). This is a point you’ll need to explain to your ethics board clearly: the encryption model is different from personal WhatsApp, but it meets enterprise security standards.
Pricing and Cost Terms
Understanding pricing is essential for budgeting research projects. The WhatsApp Business API pricing model changed significantly in mid-2025, and the new structure affects how to set up WhatsApp Business API for research cost-effectively.
Per-Message Pricing (2026 Model)
On July 1, 2025, Meta switched from per-conversation billing to per-message billing. Every template message you send is now billed individually. The rate depends on the recipient’s country and the template category.
This change matters for research because it makes cost modeling more predictable. You can calculate costs based on the number of template messages you expect to send (invitations, re-engagement prompts, reminders) rather than estimating conversation counts.
Message Category Rates
Rates vary significantly by country and category. In the US, marketing messages cost approximately $0.025 per delivered message as of Meta’s January 2026 rate card. Utility messages are cheaper. Service messages (within the 24-hour window) carry no Meta charge.
For research, the goal is to minimize the number of template messages by keeping participants engaged within the free service window, and to classify your templates as utility rather than marketing wherever possible.
BSP Markup
On top of Meta’s per-message rates, your BSP charges its own fee, typically $0.003 to $0.010 per message. This adds up across large studies.
When comparing BSPs or research platforms, ask for the all-in per-message cost, not just Meta’s base rate. Some platforms bundle BSP fees into a subscription, which can be more economical for high-volume research.
Yazi’s pricing structure bundles API costs into monthly plans, making it easier to budget without tracking individual message fees.
Free Service Window
When a participant messages you (for any reason), it opens a 24-hour window during which your responses are free. This is the service window, and it’s the foundation of cost-efficient WhatsApp research.
A well-designed study keeps participants responding regularly, which means most of your actual research communication happens for free. The paid template messages are just the entry points: the initial invitation and any re-engagement after a lapse.
Cost Per Completed Survey
The most useful benchmark for researchers comes from the Immigration Policy Lab, which demonstrated that a 19-question WhatsApp survey can cost as little as $0.32 USD per completed response. Costs vary by country (rates in African and South Asian markets are generally lower than in North America or Europe).
Compare that to the cost of phone interviews (CATI), in-person fieldwork, or even web panel incentives, and WhatsApp surveys look extremely cost-effective. For a detailed cost comparison, see our fieldwork vs. WhatsApp cost framework.
Research-Specific Concepts
This section covers terms that don’t appear in standard WhatsApp Business API guides because they’re specific to using the API for data collection rather than customer communication.
WhatsApp-Native Survey
A WhatsApp-native survey is conducted entirely inside the WhatsApp chat interface. Participants never click an external link or open a separate browser. Questions arrive as messages, and participants respond by typing, tapping buttons, or sending media.
This approach drives higher response rates because it eliminates friction. Participants don’t need to download an app, create an account, or navigate an unfamiliar interface. The Immigration Policy Lab’s work in Colombia, Senegal, Guinea, and Lebanon has repeatedly demonstrated this advantage.
Research platforms like Yazi’s WhatsApp survey tool build this natively, handling question sequencing, skip logic, and response validation within the chat.
Conversational Survey Flow
Rather than presenting all questions on a single page, a conversational flow delivers one question at a time, mimicking a natural chat exchange. The participant answers, and the next question appears.
This format works because it matches how people already use WhatsApp. It also allows for branching and skip logic: different follow-up questions based on previous answers, creating a personalized experience that feels more like a conversation than an interrogation.
Multimedia Capture
The WhatsApp Business API supports receiving voice notes, images, and videos from participants. For qualitative research, this is transformative. Instead of asking participants to describe a product in text, you can ask them to photograph it. Instead of typing long responses, they can send a 30-second voice note.
This capability enables ethnographic-style data collection at scale: shelf photos from retail stores, video walkthroughs of daily routines, or audio diaries recorded in a participant’s own language.
Automated Survey Bot
An automated survey bot is the software layer that manages the flow of questions and responses through the WhatsApp Business API. It sends the next question when a response comes in, applies skip logic, validates answers (checking that a rating is between 1 and 5, for example), and stores structured data.
Building this from scratch is where most DIY projects stall. The Immigration Policy Lab’s approach required WhatsApp Business API access, a Twilio account, Google Sheets integration, command-line familiarity, and statistical software. Most research teams don’t have that skill set in-house.
Diary Study on WhatsApp
A diary study uses scheduled prompts over multiple days to capture participants’ experiences, behaviors, or emotions in context. On WhatsApp, this means sending daily (or more frequent) prompts and collecting responses that include text, photos, voice notes, or video.
The 24-hour messaging window is the key technical constraint. Each day’s prompt needs to either fall within the window opened by the previous day’s response, or be sent as a new template message (at cost). Well-timed reminders and engaging prompts keep participants responding and the window open. Platforms built for this, like Yazi’s diary study tool, automate the timing and re-engagement logic.
AI-Moderated Interview
An AI-moderated interview uses artificial intelligence to conduct adaptive, in-depth interviews through WhatsApp. The AI reads each participant response and generates contextually relevant follow-up probes, mimicking how a skilled human moderator would dig deeper on interesting answers.
This is different from a standard survey bot, which follows a fixed script. AI moderation can explore unexpected themes, ask clarifying questions, and adjust the conversation flow based on what the participant says. It produces interview-quality depth at survey-like scale.
Panel Recruitment via WhatsApp
Recruiting research participants through WhatsApp can use several mechanisms: Click-to-WhatsApp ads on Facebook and Instagram, QR codes placed in physical locations, referral links shared in community groups, or direct outreach to existing contact lists via template messages.
In markets across Africa, where WhatsApp penetration exceeds 90% in many countries, this channel reaches populations that web panels and email recruitment simply miss. WhatsApp supports multiple languages, consumes minimal data bandwidth, and runs efficiently on resource-constrained devices, making it the dominant communication tool in many developing regions. For researchers focused on these markets, our guide on why WhatsApp works for research in Africa provides deeper context.
Bulk Template Messaging
Bulk template messaging is the process of sending approved template messages to a large list of recipients simultaneously, typically from a CSV upload. This is how you launch a study: upload your participant list and send survey invitations at scale.
Your sending capacity depends on your messaging tier, which starts at 250 per day for unverified accounts and increases as you complete Meta Business Verification and build a quality messaging history. For a guide on the mechanics, see our article on bulk WhatsApp invitations.
The Build vs. Buy Decision
Researchers figuring out how to set up WhatsApp Business API for research face a fundamental choice: build the infrastructure yourself or use a platform that handles it.
The DIY path is documented. The Immigration Policy Lab published their methodology, which requires WhatsApp Business API access, a Twilio account with an active phone number, Google Sheets for data integration, command-line skills, and statistical software for analysis. It works. It also requires a developer on the team and ongoing maintenance as Meta’s API evolves.
The platform path means using a purpose-built research tool that abstracts the API layer, BSP management, template submissions, webhook configuration, and compliance documentation. You design your study, upload your questions, and the platform handles delivery, collection, and analysis.
For most research teams, the answer is clear. One practitioner on a Shopify review thread described struggling with “random WhatsApp Business bans” during setup before getting professional help, highlighting a real risk of DIY approaches: accounts can be suspended if templates are poorly managed or messaging policies are violated.
The WhatsApp Business API has strict rules, and developers consistently flag template rigidity and the 24-hour window as the biggest sources of friction. A platform that has already solved these problems lets researchers focus on what they’re actually good at: study design, analysis, and insight generation.
Request a demo to see how the setup process works in practice.
Quick Reference: What to Start With
| If you want to… | Start with these concepts |
|---|---|
| Send a survey to 500 participants | WABA, Meta Business Verification, Message Templates, Bulk Template Messaging |
| Run a 7-day diary study | 24-Hour Window, Automated Reminders, Template Re-engagement, Diary Study on WhatsApp |
| Conduct AI-moderated interviews | AI-Moderated Interview, Session Messages, Multimedia Capture |
| Get ethics board approval | GDPR/POPIA Compliance, DPA, Data Residency, Opt-In, Encryption |
| Budget your project | Per-Message Pricing, Template Categories, Free Service Window, Cost Per Completed Survey |
| Recruit participants in Africa | Panel Recruitment, Phone Number Registration, WhatsApp in Emerging Markets |
Frequently Asked Questions
Can I use the free WhatsApp Business App for research instead of the API?
You can for very small, informal studies (chatting with a handful of participants manually). But the Business App doesn’t support automation, bulk messaging, structured data collection, or integration with analysis tools. It also violates GDPR due to automatic contact list uploads. For any study that needs to scale beyond a dozen participants or satisfy an ethics board, the API is the only viable path.
How long does it take to set up the WhatsApp Business API for research?
With the Cloud API and a BSP or research platform, initial setup can take minutes for the technical connection. The bottleneck is Meta Business Verification, which typically takes a few days to two weeks depending on your documentation. Template approval adds minutes to 24 hours per template. End to end, plan for one to three weeks from start to first message sent.
How much does a WhatsApp research study cost?
Template messages cost fractions of a cent to $0.025+ depending on the country and category. The Immigration Policy Lab documented a cost of $0.32 per completed 19-question survey. Add BSP or platform fees on top. For a 500-person survey in an African market, total WhatsApp messaging costs might run $50 to $200, far below the cost of equivalent phone or in-person fieldwork.
Do I need a developer to set up WhatsApp Business API for research?
If you go the DIY route, yes. You’ll need someone comfortable with APIs, webhooks, and server management. If you use a research platform that includes BSP functionality, no. The platform handles the technical layer, and researchers interact through a web-based study builder.
Will my message templates get rejected if they mention research or surveys?
Not inherently. Templates get rejected for sounding promotional, having poor formatting, or lacking opt-out instructions. Frame your research invitations as utility messages: clear purpose, institutional identification, and an easy way to decline. Avoid exclamation marks, urgency language, or anything that reads like a marketing campaign.
Can participants respond in their own language?
The WhatsApp Business API supports messages in any language. What matters is whether your system can process multilingual responses. Purpose-built research platforms often include translation and consolidation features, converting responses in 100+ languages back to English for analysis.
Is WhatsApp research only useful in emerging markets?
WhatsApp research originated in emerging markets (where WhatsApp is dominant), but the methodology works anywhere WhatsApp has significant penetration. That includes most of Europe, Latin America, South and Southeast Asia, and the Middle East. In markets where WhatsApp usage is lower (like the US, where it’s growing but not dominant), response rates will depend on your target population’s WhatsApp adoption.
What happens if a participant stops responding mid-survey?
If they stop but the 24-hour window is still open, you can send automated reminders as free session messages. Once the window closes, you need a paid template message to re-engage. The participant’s partial data is still captured and available for analysis. Designing studies with shorter question sets and timely reminders reduces this risk.
