- Google Messages tap to draft puts Smart Reply suggestions into your compose box instead of sending them immediately.
- The Google Messages tap to draft feature is rolling out in stable version 20260522_00_RC00 for Android.
- Users must manually enable tap to draft in Settings under Suggestions and Actions — the default remains tap to send.
- The change addresses a long-standing complaint that one accidental tap could fire off an unwanted message.
- Google Messages tap to draft puts Smart Reply suggestions into your compose box instead of sending them immediately.
- The Google Messages tap to draft feature is rolling out in stable version 20260522_00_RC00 for Android.
- Users must manually enable tap to draft in Settings under Suggestions and Actions — the default remains tap to send.
- The change addresses a long-standing complaint that one accidental tap could fire off an unwanted message.
Table of Contents
Google Messages Tap to Draft Fixes a Real Annoyance
If you’ve ever sent a half-baked Smart Reply to the wrong person — or worse, watched a snarky one-liner fly out to your boss — you’ll appreciate what Google has quietly pushed to Google Messages tap to draft. The feature, now rolling out to Android users in stable version 20260522_00_RC00, does something deceptively simple: instead of firing your Smart Reply the moment you tap it, it drops the text into the compose field and waits. You decide when — or whether — to actually send it.
It sounds like a small thing. It isn’t. For a lot of users, this was the difference between Smart Replies being useful and Smart Replies being a liability.
What Smart Replies Were Doing Wrong
Google’s Smart Reply feature has been baked into Messages for years, using on-device AI to surface contextual quick responses above the text compose bar. Tap one, and it sends. That was the entire interaction — no confirmation, no buffer, no chance to change your mind.
The speed was the point. Quick acknowledgments like “On my way,
Source: 9to5Google
