top of page

Anjanesh Sharma

MESSAGING PLATFORM ADOPTION RESEARCH

Project Overview

Role

Lead UX Researcher

Timeline

August - September 2025

Methodology
In-depth Interviews, Daily Synthesis, Pattern Recognition

Scope
Multi-segment qualitative study across business types and use cases

Business Context

  • A major messaging platform had launched Click-to-Messaging ads (CTMA) designed to help businesses drive conversations directly from paid advertisements. The product offered a low-friction path for customers to initiate WhatsApp conversations with businesses they discovered through ads.

  • Early adoption signals were mixed. Some businesses adopted immediately and made it core to their lead generation strategy. Others were aware of the format but never launched campaigns. Still others tried it once and abandoned it entirely.

  • The product team needed to understand the adoption blockers and enablers across different business segments to inform roadmap prioritization, educational content strategy, and market expansion plans.

The Challenge

This wasn't a single-segment usability study. The messaging platform served businesses across:

  • Different maturity stages (startups to enterprises)

  • Different industries (events, education, travel, manufacturing, restaurants, healthcare)

  • Different technical capabilities (self-taught marketers to performance marketing experts)

  • Different resource constraints (solo operators to 25-person marketing teams)

The research challenge: Surface patterns that cut across this heterogeneity identify what drives adoption and abandonment regardless of business type—while still honoring the specific context each segment operates within.

Research Approach & Thought Process

I designed a multi-wave qualitative study with daily synthesis cycles. Rather than batching all interviews and analyzing at the end, I conducted daily debriefs after each set of interviews to surface emerging patterns early and adapt subsequent interview focus areas.

Study Design:

  • 12 participants across 6 business segments

  • Conducted over 3 weeks (Aug 28 - Sep, 2025)

  • Daily debrief documentation to track evolving patterns

  • Flexible interview protocol that deepened based on prior day's insights

Participant Segments:

  1. Events & Gaming (small business, self-taught marketer)

  2. Retail Pharmacy (established chain, awareness-focused)

  3. Education Services (multiple providers, lead generation focus)

  4. Travel & Tourism (B2C, conversion-driven)

  5. B2B Manufacturing (high-volume, low-touch business model)

  6. Performance Marketing Agency (expert user, managing multiple clients)

Key Research Questions:

  • How do businesses discover and evaluate the ad format?

  • What drives the decision to adopt or not adopt?

  • For adopters: what value do they extract and what pain points persist?

  • For non-adopters: what specific blockers prevent trial or sustained use?

  • How does WhatsApp API usage correlate with ad adoption decisions?

Methodological Decision: Daily Synthesis

Rather than waiting until all interviews were complete, I documented daily debriefs after each interview day.

This served three purposes:

  1. Pattern recognition velocity: Emerging themes became visible faster, allowing me to probe deeper in subsequent interviews

  2. Hypothesis refinement: Early signals could be pressure-tested across different business contexts

  3. Stakeholder communication: Product and design teams could follow the research in real-time through daily summaries

This approach turned research into an ongoing conversation rather than a final report drop.

Key Findings

Finding 1: Setup Complexity Is the Primary Adoption Blocker

Across non-adopters and past users who abandoned, setup complexity was the most cited barrier. Specifically:

  • Difficulty understanding template configuration

  • Confusion about linking WhatsApp Business API numbers to ad accounts

  • Lack of clear, accessible tutorials or step-by-step guidance from the platform

"We didn't get the exact templates for it... maybe we didn't get to know how to put the right filters. We got stuck there actually once we tried."
— Events company, tried twice and abandoned

Insight: Complexity wasn't just a UX friction point—it created financial risk anxiety. When users weren't confident in setup, spending money on ads felt like gambling. This fear pushed them back to more familiar, predictable ad formats.

"Initially if the amount would be less we will be more happy to use it... because then people are experimenting they feel I spent so much of money. So they are like just let's stick to Facebook ads only."
— Events company

Finding 2: Lead Quality vs. Lead Quantity Trade-Off Is Universal

For active adopters, the format generated significantly higher lead volume than traditional form ads or landing page clicks. However, lead quality was consistently lower.

This created a strategic tension: businesses had to choose between:

  • High volume, low quality (CTMA) → required more sales team filtering

  • Low volume, high quality (landing page ads) → fewer leads but better conversion rates

"In WhatsApp, I did more quantity but less quality. In landing page... the quantity is very less but the quality is more, much more."
— Travel company, active user

Implication: The format worked best for businesses with dedicated sales teams who could handle high conversation volume and filter leads manually. For businesses without this capacity, the volume became overwhelming rather than valuable.

Finding 3: Measurement and Attribution Are Manual, Time-Intensive Processes

For businesses using the messaging API with CTMA, attributing leads back to specific ad campaigns was highly manual and required 1.5-2 days of work each month.

Sales teams had to:

  • Manually review WhatsApp conversations

  • Match the pre-set message from the ad to identify which campaign generated the lead

  • Export and compile this data outside the ads platform

"When it comes to CTW... the salespeople need to map how many leads came from this ad, how many leads came from this ad... based on the pre-fixed message, so their one and a half day are wasted."
— Interior design materials company

Insight: The lack of integrated reporting between the ads platform and messaging API created a data visibility gap that made campaign optimization difficult and time-consuming.

Finding 4: Education and Support Gaps Drive Non-Adoption

Non-adopters consistently cited a lack of:

  • Proactive education from the platform (no emails, no in-platform tutorials, no notifications about the ad format)

  • Clear use case examples showing how businesses like theirs could benefit

  • Accessible troubleshooting resources when setup issues arose

"There should be little awareness that how it is to be used. Like, if the platform takes a small step and makes a small introductory video of how it is to be used... then we go to try."
— Pharmacy chain

"The help and support of the platform is really bad."
— Education services provider

Implication: Discovery was entirely passive. Businesses learned about the format by:

  • Seeing competitors use it

  • Manually exploring the ads platform

  • Asking peers in industry groups

There was no systematic onboarding or education pathway from the platform itself.

Finding 5: API Adoption Doesn't Guarantee Ad Adoption

Several businesses used the WhatsApp Business API extensively for customer communication, order updates, and support—but had never used CTMA or didn't see the connection.

Reasons:

  • The API and ads platform were managed by different teams internally

  • Businesses saw the API as a "support tool" and ads as a "marketing tool" siloed mental models

  • No clear messaging from the platform about how API capabilities enhanced ad performance

"The company uses the WhatsApp API for paid, outbound messaging campaigns... However, this is managed by a separate team. The participant is not directly involved with the WA API and does not have a role in its day-to-day use."
— Pharmacy chain

Segmentation Insight: Adoption Correlates with Resource Capacity

Screenshot 2026-03-04 022833.png

Pattern: Businesses with dedicated sales teams to handle conversation volume were far more likely to adopt and sustain use. Solo operators or small teams without filtering capacity either never tried or quickly abandoned due to overwhelm.

Strategic Recommendations

Based on the cross-segment findings, I recommended four intervention areas:

01  SIMPLIFY ONBOARDING WITH GUIDED SETUP
Create an in-platform, step-by-step setup flow with:

  • Template configuration wizard

  • Pre-populated examples for common industries

  • API number linking explained visually

  • Preview mode before launch

Rationale: Reducing setup complexity directly addresses the primary adoption blocker and reduces financial risk anxiety that prevents experimentation.

02  BUILD EDUCATIONAL CONTENT PATHWAYS
Develop:

  • Short video tutorials (2-3 minutes) embedded in ads manager

  • Industry-specific use case examples (e.g., "How restaurants use CTMA")

  • Email onboarding series for businesses who enable messaging API

  • In-platform tooltips and contextual help

Rationale: Non-adopters aren't discovering the format or understanding its value. Proactive education bridges this gap.

03  INTEGRATE CAMPAIGN ATTRIBUTION INTO API DASHBOARDS
Enable:

  • Automatic tagging of conversations by source campaign

  • Lead quality feedback loop (mark leads as qualified/unqualified in API dashboard)

  • Campaign performance data visible directly in messaging interface

Rationale: Eliminating the 1.5-2 day manual attribution process makes the format viable for businesses without dedicated analytics resources.

04  PROVIDE LEAD QUALITY CONTROLS AT CAMPAIGN LEVEL
Test:

  • Pre-qualification questions before chat initiation

  • Friction controls (e.g., require form field before opening chat)

  • Audience targeting recommendations based on business type (B2B vs. B2C)

Rationale: The volume/quality trade-off is universal. Giving businesses more control over lead filtering before conversations start reduces sales team burden and increases sustained adoption.

Impact & Outcomes

The research directly informed:

  • Product roadmap prioritization: Setup simplification and attribution integration moved to top-tier priorities

  • Educational content strategy: Marketing team launched industry-specific tutorial series

  • Segmentation strategy: Sales and growth teams adjusted targeting based on resource capacity patterns

  • Agency enablement: Performance marketing agencies received specific training materials to drive client adoption

Research Reflection: What Daily Synthesis Taught Me

The daily debrief approach fundamentally changed how I conducted synthesis.

Instead of drowning in 12 transcripts at the end, I was building the argument incrementally testing whether patterns held across different business contexts in real time.

This created two benefits:

  1. Faster time to insight: Key findings were clear by interview 8, allowing me to use interviews 9-12 to pressure-test rather than discover

  2. Richer probing: When a pattern emerged (e.g. setup complexity blocks adoption), I could explicitly probe that dimension in subsequent interviews across different segments to understand boundary conditions

The discipline of writing daily also forced precision in language. I couldn't hide behind vague synthesis later—I had to articulate what I was seeing clearly enough to communicate it the same day.

​

This is now my default approach for multi-week qualitative studies: synthesize as you go, don't batch at the end.

bottom of page