At Google I/O this week, one of the most discussed demos was Gemini surfacing inside Google Messages — offering smart replies, surfacing information, and hinting at scheduling suggestions directly inside the conversation thread.

The response was predictably enthusiastic. AI is coming to chat. The interface is finally changing. The era of leaving your messaging app to do useful things is ending.

All of this is true. And also: some of us have been doing it for a while.

What Google announced

The headline capability from Google I/O's messaging demos was Gemini acting as an ambient assistant inside your chat thread — able to answer questions, draft replies, and surface scheduling context without requiring you to open a separate app or switch interfaces.

It's early-stage. The scheduling suggestions in particular felt more like prompts ("looks like you're trying to arrange a meeting — want me to help?") than fully resolved booking flows. But the direction is clear: Google is building toward AI that lives where the conversation lives.

This is the right direction.

The product that already does this

Wenya launched a scheduling keyboard in 2025. It lives inside WhatsApp, iMessage, and Telegram — not as a chatbot, but as a keyboard extension. When you want to propose a meeting, you tap Wenya inside your keyboard tray, pick a time, and a structured scheduling proposal appears inside your message thread.

No app switch. No link to click. The recipient confirms in one tap, inside the same thread.

Wenya has 25,000 users from its beta launch through Hey Famm and is backed by a US Utility Patent application on the keyboard scheduling mechanic itself. It is, as far as we know, the only product that has actually shipped in-chat scheduling as a keyboard layer — not a bot, not a link, not a redirect.

Why the keyboard layer matters

There are several ways AI could theoretically help with scheduling inside chat:

The chatbot approach. A bot inside the thread that you message. Problem: bots break the conversational flow. You're now texting a robot instead of a person, and the other party sees a bot reply in your name.

The link approach. The AI generates a Calendly-style link for you. Problem: this is just the same link problem with extra steps. The recipient still has to leave the chat.

The keyboard approach. The scheduling tool lives inside the keyboard, generates a native message, and the interaction happens inside the thread on both sides. This is Wenya.

Google's direction — Gemini inside Google Messages — is closest to the keyboard model. The AI is ambient, living in the interface, not something you switch to. That's the right architecture. The question is whether it will produce a fully resolved scheduling outcome (time confirmed, both parties aligned, timezone-aware) or whether it will remain in the "helpful suggestion" territory for now.

What this moment tells us

Google's investment in this direction is a strong signal that the market has confirmed what the problem is: AI value is maximised when it lives inside the tools people already use, not when it asks them to go somewhere new.

This is the same insight that led us to build a keyboard, not a booking page.

Scheduling is one of the clearest use cases because the pain is immediate, frequent, and well-understood. Everyone who uses WhatsApp has had a conversation stall at the "let's find a time" moment. The solution isn't a better link. It's scheduling that never requires a link at all.

The race to solve this in chat is real. We're glad it's become obvious.

Wenya is the in-chat scheduling keyboard — available now inside WhatsApp, iMessage, and Telegram. US Utility Patent pending. Try it at wenyawanna.ai