Engineering Journal
What I Learned at AiSensy Evolve: WhatsApp Automation, Meta Partnerships, and Where We Are Building
The Event: AiSensy Evolve
Earlier this week I attended AiSensy Evolve — billed as India's largest WhatsApp Business event and run in direct collaboration with Meta. It brought together developers, product builders, growth teams, and partnership stakeholders all operating within the WhatsApp Business Platform ecosystem.
The atmosphere was different from a typical tech conference. Everyone in the room was building on WhatsApp — chatbots, marketing automation, transactional notifications, customer support flows, and in our case, something a bit more niche: structured data collection via WhatsApp forms.
Meeting Ekta Agarwal — Strategic Partnership Manager, Meta
One of the most valuable conversations I had was with Ekta Agarwal, Strategic Partnership Manager at Meta (previously at Zomato and Uber). She manages the Meta Business Partner program specifically for the WhatsApp ecosystem in India.
Ekta was exactly who you want to talk to if you are seriously thinking about building a compliant, scalable WhatsApp product and understanding where the Meta partnership pathways actually lead.
What We Are Building: WhatsApp Form Automation
I shared with Ekta what our team has actually shipped:
Users can fill out structured forms entirely inside WhatsApp. The responses are captured in real time on our backend server — without any external app, link, or browser.
Here is how it works technically:
Flow Overview
- User initiates a conversation on a WhatsApp Business number
- Our system sends a templated interactive message with structured input prompts (using the WhatsApp Flows API or sequential message logic)
- User responds step by step — name, quantity, date, product type, or any domain field
- Our backend webhook listener (built in NestJS) captures each response, validates it, and writes it to the database in real time
- Business teams see the data live in dashboards — no manual re-entry, no spreadsheets, no email chains
What Makes This Valuable
In manufacturing, logistics, and field operations, workers rarely sit at a computer. They are on the factory floor, at a warehouse gate, or on a delivery route. WhatsApp is the one interface they all already use fluently.
By collecting structured data through WhatsApp conversations:
- Attendance and shift records can be submitted from the shop floor
- Material inspection results can be entered by quality officers
- Delivery confirmations and PODs can be captured in real time
- Maintenance requests can be raised directly from the machine operator's phone
No app install. No training overhead. No login friction. Just a WhatsApp message.
The Meta Partnership Question
This was the conversation I genuinely wanted to have. How exactly does one become a Meta Business Partner — specifically in the WhatsApp vertical?
Ekta broke it down clearly.
What Meta Actually Looks For
Meta evaluates partners primarily on three dimensions:
| Dimension | What It Means |
|---|---|
| Volume and Scale | Monthly Active Users on your WhatsApp integration, message throughput, and conversation volume across your client base |
| Technical Certification | Demonstrated compliance with WhatsApp Business API standards, security practices, webhook reliability, and data handling policies |
| Business Impact | Measurable outcomes delivered for businesses using your tooling — automation rates, cost savings, conversion improvements |
The Tiered Partnership Path
Meta's partner program is not a single badge. It is a tiered ecosystem:
1. WhatsApp Business Solution Provider (BSP) This is the foundational tier. You apply directly through Meta, demonstrate technical readiness, agree to API usage policies, and get access to a dedicated Tier 1 phone number registry. This is where most serious operators should be aiming first.
2. Meta Business Partner — Growth Tier Awarded to BSPs who demonstrate consistent client growth and message volume. Meta provides priority support, co-marketing opportunities, and early access to new API features.
3. Meta Business Partner — Recognised/Premier Tier Reserved for partners managing significant enterprise accounts, high message volumes (hundreds of thousands of conversations per month), and proven ROI delivery for clients.
The Revenue and Volume Reality
Here is the honest picture Ekta shared:
- There is no single fixed revenue number that unlocks partnership
- What matters more is scale trajectory: are your active numbers, monthly conversation volume, and client count growing consistently?
- Meta looks at ecosystem contribution: are you building workflows that bring new businesses onto the WhatsApp Business platform, not just adding features on top of existing accounts?
- Technical reliability is gate-keeping: frequent webhook failures, policy violations, or spam complaints from end users will block any partnership track regardless of revenue
The practical starting benchmark for meaningful partnership conversations:
- 500+ active WhatsApp numbers managed through your integration
- 50,000+ conversations per month across your client base
- At least 10 business clients live with measurable outcomes
These are not hard thresholds — they are conversation-worthiness markers.
Key Takeaways for Builders in This Space
1. Compliance is the moat
The WhatsApp Business API has strict policies around consent, message templates, conversation windows, and opt-in handling. Teams that build with compliance from day one are far harder to disrupt than teams that bolt it on later. Meta partners earn trust because their clients rarely receive policy violations.
2. The form-in-WhatsApp niche is still underbuilt
Most WhatsApp tools focus on marketing broadcasts and support chatbots. Structured data collection — fieldwork forms, inspection checklists, operational logs — is significantly underserved. The UX barrier to adoption is near zero in field-heavy industries.
3. BSP registration is worth pursuing earlier than you think
You do not need enterprise scale to apply for BSP status. A well-documented integration, a few live clients, and a clear compliance posture is enough to begin the conversation. Getting into the BSP ecosystem gives you access to Meta's business team directly, better rate limits, and a legitimate signal for enterprise clients.
4. Partnership is more about relationships than revenue thresholds
Ekta's point that stuck with me: Meta partners are ecosystem builders, not just high-volume API consumers. If your tool is helping businesses use WhatsApp more effectively — and you can demonstrate that systematically — Meta wants that association.
What We Are Doing Next
This event clarified our direction. The WhatsApp form automation tooling we have built for internal operations is production-proven. The next step is productizing it for external verticals — starting with manufacturing and field operations companies where data collection friction is the highest.
Short-term priorities:
- Apply for BSP status with our current integration credentials
- Document the form automation tool as a formal product offering
- Onboard 3 to 5 pilot clients in manufacturing or logistics to generate the conversation volume for the initial Meta partnership milestone
- Connect back with Ekta's team once we have 3 months of active volume data
Final Thought
Events like Evolve are underrated as a product and engineering input. Not because of the keynotes — but because one conversation with the right person compresses months of guesswork into a clear, actionable direction.
If you are building on WhatsApp and not yet in the BSP conversation, start there. The partnership path is real, the access it provides is meaningful, and the compliance foundation it forces you to build makes your product genuinely better.
Attended AiSensy Evolve, in collaboration with Meta. Views and conversation summaries are my own.