The short answer: The ringtone you set in the Contacts app only plays for calls to your SIM. WhatsApp has its own per-contact ringtone; Telegram sets one globally; Instagram and most other apps offer nothing at all. App calls are notifications, not telephony, which is why they follow different rules.

You set a distinctive ringtone for someone in Contacts, then their WhatsApp call comes through sounding exactly like everybody else’s. Nothing is broken — the two things were never connected.

Why app calls ignore your contact ringtone

A call to your phone number goes through the telephony stack. The dialler looks up the caller, finds the ringtone attached to that contact, and plays it. That lookup is the whole feature.

A WhatsApp or Instagram call never touches telephony. It arrives over the internet, and the app announces it with a notification flagged as a call — which is what makes it full-screen and persistent. The sound comes from that app’s notification channel, so the contact record is never consulted. No amount of editing a contact will change it.

That single distinction explains every quirk below.

Calls to your phone number

Open Contacts → the contact → ⋮ → Set ringtone, and pick any tone on the device. Some builds also offer a per-contact vibration pattern on the same screen.

This is the oldest and most reliable per-person setting on Android. It just has a narrow scope: SIM calls only, nothing else.

WhatsApp: a proper per-contact ringtone

WhatsApp is the one app that does this thoroughly. Open the chat → tap the contact’s name at the top → Custom notifications → tick Use custom notifications. You get two independent controls:

• Notification tone — for their messages
• Ringtone — for their calls

Set both and that person is fully distinct in WhatsApp, in each direction. Group chats have the same screen if you want a busy group to sound different.

Telegram, Signal and Instagram

• Telegram lets you set a call ringtone, but under Notifications and Sounds — it applies to all Telegram calls rather than per contact. Per-chat customisation covers message sounds.
• Signal similarly gives you a global call ringtone, with per-conversation message sounds.
• Instagram has no ringtone setting of any kind. Calls and missed calls arrive as ordinary Instagram notifications, with one sound for the whole app.

So the practical state of things: one app does it properly, two do it globally, and the rest don’t do it at all.

Getting a per-caller ringtone in the apps that lack one

Since app calls announce themselves through notifications, an app that reads notifications can respond to them — including by playing a ringtone of your choosing.

That’s how NotiWeave handles it. For calling apps like WhatsApp and Instagram, it loops your chosen ringtone while the incoming-call notification is showing, and you can set a different one per caller. The same screen that assigns a person’s message sound assigns their call ringtone, so one place covers both.

Setting it up:

1. Grant Notification Access on first launch — the one permission needed to read notifications, revocable at any time.
2. Allow background running (plus Autostart on Xiaomi-style builds) so an incoming call is never missed while the phone is idle.
3. On the Apps screen, enable call ringtones for the calling apps you care about. Each app is opt-in, and you choose per app whether NotiWeave handles threads, message sounds, call ringtones, or any combination.
4. In Rules, set a default ringtone per app; in a sender’s thread, tap the bell to give that caller their own.
5. Silence the app’s own call sound in its system notification settings, or you’ll hear both at once. The support page covers this.

Worth being clear about the boundaries: this covers calls that arrive as app notifications, not calls to your phone number — those stay with the Contacts ringtone, which already works well. It’s Android-only, since iOS has no API for reading other apps’ notifications. And it runs entirely on the device, with no account and no server; see the privacy policy.

Common questions

Will this change the ringtone for normal phone calls? No, and it doesn’t need to. Set those in Contacts → Set ringtone.

Can I get a different ringtone for each person on Instagram? Not from within Instagram. It takes a notification-level approach like the one above.

Why do I hear two ringtones? The source app is still ringing alongside your custom tone. Silence the app’s own call sound in its system notification settings.

Does the custom ringtone loop like a real call? It loops while the incoming-call notification is up, which is what makes it usable as a ringtone rather than a one-shot alert.

Does a per-contact ringtone survive a new phone? Contact ringtones usually travel with a full device backup. Per-chat settings inside apps generally do not, and typically need setting up again after a reinstall.

Two systems, two sets of rules. Contacts handles your phone number, each app handles its own calls to whatever extent its developers bothered — and where they didn’t bother, the notification is still there to work from.

The short answer: Android has no system-wide “sound per person” setting. A handful of messaging apps build their own — Google Messages, WhatsApp, Telegram and Signal all let you give one chat its own tone. For every other app, including Instagram, you need something that sits on top of your notifications and applies the rule itself.

If you have ever wanted your partner’s message to sound different from a delivery update, you have run into one of Android’s odder gaps. The platform is generous about notification control in some directions and completely silent in others. This guide covers exactly where the line falls, so you don’t spend an evening hunting for a setting that was never there.

Why Android can’t do this on its own

Since Android 8.0, every notification an app posts belongs to a notification channel — “Messages”, “Calls”, “Group chats”, “Promotions”, and so on. The sound is a property of the channel, and that is the unit you get to control. Open Settings → Apps → the app → Notifications and you can give each of those categories its own tone, turn off the ones you don’t care about, or make them silent.

What you cannot do is create a channel. Only the app can. So unless the developer decided to make a channel per conversation, there is no hook for “this person, specifically” — the system has nowhere to hang the setting.

Android 11 improved this with conversation notifications: apps can mark a notification as belonging to a person, which is what puts those chats in the Conversations section at the top of your notification shade. Apps that adopt it effectively get a channel per conversation, and that is why the apps below can offer per-chat sounds while most others can’t.

Apps that let you do it natively

Exact menu wording shifts between app versions and between Samsung, Xiaomi and Pixel builds, but the path is stable.

Google Messages (SMS/RCS)

Open the conversation → the ⋮ menu → Details (or Notifications) → Sound. Pick any tone on the device. Google Messages creates a per-conversation channel behind the scenes, so the choice also shows up under Settings → Notifications → Conversations.

WhatsApp

Open the chat → tap the contact’s name at the top → Custom notifications → tick Use custom notifications. You get two separate controls here: Notification tone for messages and Ringtone for calls. This is the most complete per-contact implementation of the four.

Telegram

Open the chat → tap the name → Notifications → Sound. Telegram also lets you set a different tone for a group than for a private chat, which is handy if you’re in a few busy groups.

Signal

Open the conversation → ⋮ → Settings → Sounds & notifications → Message sound. Signal keeps the per-chat setting local to the device, like everything else it does.

Per-contact ringtones for phone calls

This one is separate, and often what people actually mean. Open the Contacts app → the contact → ⋮ → Set ringtone. That gives you a distinct ringtone when that person rings your phone number.

Two things it does not do: it has no effect on messages, and it has no effect on calls placed through WhatsApp, Instagram, Telegram or any other app — those arrive as app notifications, not as calls to your SIM, so the Contacts ringtone never enters the picture.

Where the native approach runs out

If your messaging life fits inside those four apps, you’re done — no extra software needed. In practice it usually doesn’t, and the gaps look like this:

• Most apps never built the feature. Instagram DMs, LinkedIn, Discord, Slack, Gmail, food delivery apps, banking apps: one sound for everything the app sends, no matter who sent it.
• The settings live in a dozen places. Four apps means four different menus with four different names, and nothing that shows you the whole picture at once.
• It doesn’t survive cleanly. Reinstall an app, or move to a new phone, and the per-chat tones generally do not come with you.
• There’s no consistency. You can’t say “family always sounds like this, in every app” — each app only knows about its own chats.

Doing it in one place, across every app

The alternative is to let one app read your notifications and apply your own rules. That’s what NotiWeave does: it groups notifications into a thread per sender, and each sender can have its own message sound and its own call ringtone — regardless of which app the message came through.

Because it works from the notification itself rather than from inside each app, the same rule covers Instagram, LinkedIn or anything else that has no per-contact setting of its own.

Setting it up:

1. Grant Notification Access when NotiWeave asks on first launch. That’s the one permission it needs to read notifications, and you can revoke it at any time.
2. Allow it to keep running in the background, so capture continues while your phone is idle. On Xiaomi and similar builds that also means enabling Autostart — the app walks you through it.
3. Open the Apps screen and pick which apps to include, and what NotiWeave may do with each: save messages as threads, play your own notification sounds, ring a custom tone for its calls. Anything you don’t tick stays invisible to it.
4. In Rules, set a default sound per app. Then in any sender’s thread, tap the bell to give that person their own message sound or call ringtone — from the built-in libraries or your own audio file.
5. Silence the original app’s own notification sound in its system settings. Otherwise both sounds play and you hear a double alert. The support page covers this step in more detail.

Worth knowing before you start: it’s Android-only — iOS gives apps no way to read other apps’ notifications, so no equivalent exists there — and it runs entirely on the device. There’s no account and no server, which you can verify in the privacy policy.

Common questions

Do I need an extra app if I only care about WhatsApp? No. WhatsApp’s own Custom notifications feature is complete — message tone and call ringtone, per contact. Use it.

Can I get a per-person sound for Instagram DMs? Not from inside Instagram; it has no such setting. It takes a notification-level approach like the one above.

Why do I hear two sounds? Because the source app is still playing its own tone alongside your custom one. Silence the app’s notification sound in system settings and only your chosen tone remains.

Do custom tones survive a restart? Yes, in both approaches. What tends not to survive is reinstalling the source app, which resets its channels and any per-chat sounds you set inside it.

Will this drain my battery? Reading notifications you already receive costs very little — nothing is being polled. The one thing to watch is aggressive battery optimisation cutting the listener off, which is why the background-running step above matters.

Android’s notification system is better than its reputation, but it was designed around apps, not people. Until that changes, per-contact sound means either using the few apps that built it themselves, or putting one layer above all of them.

The short answer: Android 11 and newer include Notification history under Settings → Notifications. It is switched off by default, it only records from the moment you enable it, and it holds roughly the last 24 hours. Turn it on now and it will be there the next time you swipe something away by accident.

Almost everyone has done it: a notification arrives, your thumb clears the shade, and half a second later you realise you never read it. Whether you can get it back depends entirely on one toggle — and on whether you flipped it before the mistake, not after.

Turn on Notification history

On a Pixel or most stock-ish Android builds:

Settings → Notifications → Notification history → turn on Use notification history.

Manufacturer skins move it a level or two:

• Samsung (One UI): Settings → Notifications → Advanced settings → Notification history
• Xiaomi / HyperOS, OnePlus, Oppo: usually Settings → Notifications & Control Center → Notification history, though some builds omit the feature entirely
• Nothing, Motorola, Sony: generally follow the stock path above

Once it’s on, the same screen becomes the log. It lists recent notifications and, below them, the ones you snoozed or dismissed in roughly the last day — app by app, with a timestamp.

If you can’t find it anywhere in Settings, try searching Settings for “history”. If nothing comes up, your build doesn’t ship it, and the longer-term option further down is the only route.

What it does not do

This is where most people get caught out. Notification history is genuinely useful, but it’s a short-term safety net rather than an archive:

• It records nothing from before you turned it on. There is no hidden backlog waiting to be revealed — enabling it after losing a notification will not bring that one back.
• It keeps about 24 hours. Anything older is gone. There is no setting to extend the window.
• It logs text, not media. Photos, stickers and other attachments that arrived with a notification generally aren’t preserved.
• Apps can remove their own notifications. Read a WhatsApp message on your laptop and the phone notification is withdrawn by the app itself.
• It’s a flat list. One long chronological log across every app, with no grouping by who the message was from.

On Android 10 and older

Older versions had no user-facing history screen, but there was a well-known trick: add a Settings shortcut widget to the home screen and pick Notification log from the list of targets. That opened a raw system log of recent notifications.

It disappeared with Android 11, replaced by the proper Notification history feature. If you’re on an older phone, the widget route is worth trying; on anything current, it’s gone.

Why notifications disappear in the first place

Worth separating the causes, because two of them are fixable:

• You or the app cleared it. Normal, and what history is for.
• Do Not Disturb was on. The notification arrived silently. It’s in the shade, not lost.
• The app was killed in the background. Aggressive battery optimisation on Xiaomi, Samsung and similar builds can stop an app being able to deliver at all. That’s a settings problem, not a history problem.
• A message was deleted for everyone. In WhatsApp and Telegram, the notification is often the only remaining copy of what was said — and that’s precisely the case where a 24-hour window is not much comfort.

Keeping notifications for longer than a day

If a day isn’t enough, the mechanism you need is a notification listener: an app that receives each notification as it arrives and writes it down.

That’s the basis of NotiWeave. It saves the notifications from the apps you choose and groups them into a thread per sender, so a week of messages from one person reads as one conversation rather than scattered log entries. Photos, stickers and shared reels land in the thread alongside the text. Nothing expires on a timer — entries stay until you delete them.

Getting there:

1. Grant Notification Access on first launch. It’s the one permission needed to read notifications, and it can be revoked at any time.
2. Allow background running so capture keeps working while the phone is idle — on Xiaomi-style builds, that includes Autostart. The app walks you through it.
3. On the Apps screen, tick the apps whose messages you want saved as threads. Everything you don’t tick stays invisible to it.

Two honest limits: it can only save what arrives after you’ve set it up — there’s no way for any app to reach back in time — and it’s Android-only, because iOS gives apps no mechanism to read other apps’ notifications at all.

Everything stays on the device. There’s no account and no server, which is spelled out in the privacy policy.

Common questions

Can I recover a notification I cleared before enabling history? No. Nothing was being recorded, so there’s nothing to recover. This is the one case where no app or setting can help.

Does notification history show deleted WhatsApp messages? If the notification arrived within the window history covers, the text will usually still be listed there — the notification is a separate copy from the message in the chat.

Does it cost battery? Negligibly. Both the system feature and a listener app react to notifications you already receive; nothing is being polled.

Can I see notification history for one specific person? Not with the built-in feature — it’s a single flat list. Grouping by sender is exactly what a per-sender threading app adds, and it pairs well with giving each person their own notification sound.

Turn the system toggle on today regardless of anything else you do — it costs nothing and it’s the difference between “gone” and “annoying” the next time your thumb is faster than your eyes.