Technology

WhatsApp's New Development Lead Sets Out Plans for Simpler Chats, In-App Payments and a More Capable AI

Martin HollowayPublished 5m ago4 min readBased on 1 source
Reading level
WhatsApp's New Development Lead Sets Out Plans for Simpler Chats, In-App Payments and a More Capable AI
Image by LoboStudioHamburg from Pixabay

Kunal Shah, who took over WhatsApp's development from Will Cathcart earlier in 2026, has published a note setting out the app's priorities. TechCrunch reported on the note on 10 November 2026.

The note, titled "My Thoughts 5 Months In," centres on ease of use, expressive messaging and a broader role for AI inside the app. WhatsApp has more than 3 billion users, according to TechCrunch, so any change to its core messaging features reaches a very large installed base.

Shah's note cites the scale of existing messaging habits. People send over 10 billion voice messages on WhatsApp every day, along with over 4 billion stickers. Those two figures frame the first priority: making voice notes, groups, stickers and video simpler and more expressive. The note does not, as reported, describe the specific interface changes that will deliver this.

The more structural item concerns transactions. Shah said WhatsApp is working with financial services and telecom partners to make completing tasks as easy as sending a message. The note points to enabling bill payments, loans and eSIM purchases on WhatsApp through those partnerships. In each case, the partner institution would supply the underlying payment and account systems, often called the rails, while the transaction itself happens inside a chat thread.

On AI, Shah said WhatsApp wants its assistant to find what users need, get things done, and make sure users never miss a booking or appointment. The app already offers an AI assistant that can summarize messages and create drafts. The stated direction moves that assistant from summarizing and drafting toward acting on a user's behalf. That implies tool access, scheduling integration and a permissions model to govern them. The note does not spell out how those permissions would be scoped.

In my view, the sequence matters more than any single feature. Voice and sticker usage at this volume is a distribution asset, and payments and telecom services are a monetization path that depends on trust in the messaging layer. Pairing the two with an assistant that books, reminds and transacts would turn a consumer chat client into a transaction and scheduling layer. That shift raises questions about authentication, fraud handling, how data is separated between messaging and financial workflows, and how regulators in each market will treat a messaging platform acting as a payments intermediary. The stated plans do not answer any of them.

The broader context here is that these are announced intentions, not shipped products. The useful test over the coming months is whether the simplifications arrive as visible interface changes, whether the partner transactions launch in named markets, and whether the AI features ask for only the access they need. For users, the upside is clear: fewer apps for routine errands and fewer missed appointments. The cost of getting the trust model wrong would fall on the same people, which is why the implementation details will matter more than the ambition stated in the note.