WhatsApp • Concept • 2026
Bringing reminders to WhatsApp

Role
Product designer
Timeline
October 2026
Scope
Product design
User research
Overview
Designing for the reply you meant to send on WhatsApp
WhatsApp is where billions of conversations happen, and plenty of them end with “I’ll reply later.”

User gets a text and thinks “I’ll reply later.”

Later never comes. New chats bury the old one.
Problem
WhatsApp has no way to help users act on an intention to reply later.
The issue isn’t simply forgetting. Users already know they want to reply. The problem is that once the chat gets buried, WhatsApp gives them no active way to follow through.
I do this myself; I open a message, decide I’ll reply later, and then forget. To check if this was just a me-problem, I ran a short survey with 8 friends and family.
Findings
01 They mean to reply
6 of 8 forget to reply multiple times a week. People know they want to reply. The chat just gets buried.
02 Memory is the only system
7 of 8 rely on memory alone. Nothing in WhatsApp reminds them.
03 “Mark as Unread” doesn’t work
3 of 8 used it. 2 found it useful. New messages still push the chat down.
Why “Mark as Unread” doesn’t fix it.
“Mark as Unread” keeps the chat marked, but you still have to remember to go back.
The reminder needed to do more than signal “come back.” It needed to actively bring the conversation back into the user’s attention.
Opportunity
How might we help people follow through on “I’ll reply later” without relying on memory or hoping they notice the chat again?
Solution
Reminder that helps users act on their intention
A reminder scheduled directly from a chat. When it triggers, WhatsApp notifies the user and moves the conversation back to the top of the inbox.
Instead of asking users to remember to return to a chat, I designed a reminder that brings the conversation back to them when they choose.

Lock screen notifies users with the contact name and reminder label.

Chat resurfaces to the top of the inbox when reminder is triggered with a ringing clock icon to mark the reminder chat.
Design process

Swipe, not long-press
Long-press can open the chat by accident and mark the message as read, so I made swipe the main way to set a reminder. It keeps the chat unread and uses a gesture people already know, and long-press stays as a backup.
Setting the reminder should take less time than texting back.
I used a bottom sheet instead of a full-screen flow, so setting a reminder never feels like leaving the chat list. My mid-fidelity version had its own visual style, but WhatsApp aims to feel native to whatever device it’s on. So I switched to iOS’s built-in components, including the native date and time picker, to make the reminder feel like part of the app. On Android, it would use Android’s picker instead.





Why I didn’t auto-cancel on reply
At first, I planned to cancel a reminder as soon as the user replied, since they wouldn’t need it anymore. But that breaks easily. Someone might set a reminder to wish a friend happy birthday while still chatting with them about something else. So a reminder only clears when the user cancels it or it goes off. That also means it works for any future task, like reminding a friend to book tickets before they sell out.
Once a reminder is set, a small clock icon shows next to the chat in the inbox. Tapping the reminder button again opens the same sheet with the details filled in, plus a red “Cancel reminder” button.
What if the reminder gets missed?
People miss notifications or swipe them away by accident, so the reminder can’t depend on the lock screen alone. Once it goes off, a banner also appears inside the chat, like “Reminder sent Sept 2, 2026 at 11:00 AM. Note: Ask to call tomorrow at 3:00 PM.” If there’s no note, it says “Send a message.” The banner stays until the user dismisses it.

Reflection
Small annoyances are worth investigating because they can reveal a larger product gap.
This started as something too minor to call a problem. Looking closer showed that everyday frustrations can reveal meaningful opportunities for better experiences.
Familiar isn’t always the way to go
Long-press felt like the obvious choice, since it’s what people already know. But it could accidentally open the chat, revealing to the other person that the user had already seen their message. Swipe solved this without that risk even though it’s less familiar.