Inbox & follow-ups·Beginner5 min read

Get notified about new messages

Four ways Yesoma can tell you a new customer message landed — browser tab badge (automatic), Web Push (one-click), opt-in email, opt-in audio chime.

In this guide

1. The four signals
2. Browser tab badge (no setup)
3. Web Push (one-click enable)
4. Email notifications (opt in)
5. Audio chime (opt in)
6. Common questions

Yesoma sends four kinds of new-message notification, all triggered on every inbound message (email, WhatsApp, website form, customer portal reply). One is automatic, three are opt-in. This guide covers what each one is and how to turn them on.

1. The four signals

| Signal | Where | Default | |---|---|---| | Browser tab badge | Your browser's tab title becomes "(N) Yesoma" and the favicon gets a coral dot, only while the tab is hidden and the inbox has unread cases | On (no setup) | | Web Push notification | A native OS notification (top-right on Mac, bottom-right on Windows, the lock screen on iOS PWAs) | Needs one click to enable | | Email | A transactional email to your account, with the message preview + a deep link into the case | Off — opt in | | Audio chime | A gentle two-note sound in the browser when a new message arrives | Off — opt in |

2. Browser tab badge (no setup)

The simplest signal. If you keep Yesoma open in a background tab and a customer message lands, the tab title changes from "Yesoma" to "(3) Yesoma" — the number being how many cases still need a reply. The favicon also gets a small coral dot.

When you come back to the tab (focus returns), the title and favicon snap back to their original state. The badge only fires while the tab is hidden, so it never distracts you while you're actively working in Yesoma.

You don't have to enable anything for this; it's on by default.

3. Web Push (one-click enable)

Web Push is the most reliable signal — it works even if Yesoma isn't open in any tab. Notifications appear in your OS notification tray and persist there until dismissed.

To turn it on:

Go to Settings → Notifications.
Find the Push notifications card.
Click Enable and approve the browser permission prompt.

That's it. You'll see "Notifications are on for this device" once the subscription is registered. The Test button right next to it sends a one-shot ping you can use to confirm the wiring works.

For iPhone: Web Push works on iOS, but only inside an installed PWA — not in a regular Safari tab. The Yesoma card on iOS Safari will tell you exactly what to do: tap Share → Add to Home Screen, then open Yesoma from the new home-screen icon and enable from Settings → Notifications.

One device per browser. If you sign in on a laptop AND your phone, you can enable push separately on each — both get notified. The test button pings all your devices at once.

To turn it off: same card, click Turn off. We immediately drop your device from the recipient list and your browser stops asking.

4. Email notifications (opt in)

For owners who don't want to leave a tab open AND don't want OS push, email is the fallback.

To turn it on:

Go to Settings → Notifications.
Toggle on Email me when a new message comes in.

Each new inbound message sends one email to your account email — preview text, customer name, deep link to the case in Yesoma. Tagged in your inbox provider as alert so you can filter/route them.

We deliberately default this OFF because for a busy workspace it can be noisy — push and the tab badge usually cover the urgent cases.

5. Audio chime (opt in)

A gentle two-note sound when the inbox needs-reply count goes up. Two design choices worth knowing about:

It only fires while the tab is visible (browsers block audio in hidden tabs anyway). So it's not a "wake me up" signal — it's a "you're already working in Yesoma, here's a soft confirmation that another message landed" signal.
It never fires on initial page load. Only on actual count increases.

To turn it on: Settings → Notifications → toggle on Play a sound when a new message arrives.

6. Common questions

Push isn't firing — what's wrong? Three layers to check, top down:

OS permission. On Mac: System Settings → Notifications → find your browser → confirm it's allowed to send notifications. On Windows: Settings → System → Notifications → same. On iOS PWA: Settings → Yesoma → Notifications.
Browser permission. Click the lock/info icon in the URL bar → confirm Notifications is "Allow" for Yesoma.
Yesoma subscription. Settings → Notifications → confirm "Notifications are on for this device." If it says "Notifications are off," click Enable.

The Test button on the same card sends a real push — if you see the test ping but not real messages, that points at the message-processing path; otherwise it's one of the layers above.

Can I get push on a teammate's behalf? Push subscriptions are per-user per-device. Each teammate enables their own. The system automatically pings the workspace owner AND the case assignee (if different) on every inbound message, but only the people who've actually enabled push.

Do I get notified if the customer replies to a case I'm not assigned to? The workspace owner gets pinged on every inbound message regardless. Assignees get pinged on cases they own. Other team members get pinged based on workspace rules — if your team uses round-robin or manual assignment, only the owner + assignee get personal notifications by default.

What about teammate notifications (assignments, mentions, etc.)? Those use the same Web Push channel but a different opt-in toggle ("Notify me about team events" in Settings → Notifications). Same enable button, same test ping.