Bell notifications and how to mute them

The bell at the top right of every page tells you when something happens to your work that you did not do yourself, and when long jobs finish. While anything is unread the bell turns red and shows how many, and it gives a short shake each time a new notice arrives (not when the page loads, and not at all if your device is set to reduce motion). Point at it to see the count. A notice stays unread (bold, with a blue dot) until you open it, and each one that goes somewhere shows View: clicking it marks that one read and opens the view it is about. Mark all read clears the dot on everything, including today's reminders for follow-ups and tasks until you reload the page.

Clearing notices. Each notice has a Clear button, the X at its right: on a computer it shows when you point at the notice, and on a phone or tablet it is always there. Clear takes that notice out of your bell without opening it. Clear all, at the top of the panel, asks "Clear all notifications?" first: Yes clears every notice in your bell, Cancel keeps them. A notice that arrives while you are deciding is kept, and types you muted are left alone, so turning one back on still shows what came in. Clearing only changes your own bell, and a cleared notice does not come back. The reminders for follow-ups and tasks due today are not notices: they stay until the follow-up or task is done, so they have no Clear button and Clear all leaves them. Nothing can be marked read or cleared while a Super Admin is using View As.

Missed calls beside the softphone. In a workspace with calling, each unread missed call also shows as a card at the bottom left of the screen, just above the softphone: who called (the contact's name when the number matched one, otherwise the number), how long ago, and three buttons. Call back rings them from the softphone; it shows when you can make calls and the number is known, and you sign in to the softphone first. In a managed workspace, Call back shows only when the caller matched one of your contacts. While a call is ringing in, Call back waits: answer or decline that call first. View opens the call: your Call Log, or the caller's contact when the call rang a teammate on a number you share. Dismiss marks it read. Opening the call marks it read too, and so does Call back once the call is placed; a call that could not be placed keeps its card. A card stays until you act on it. Up to three show at once, newest first (one on a phone), and a line under them such as "2 more missed calls" opens the bell on your unread missed calls; Show all there goes back to every notice. Hide, above the cards, folds them into one button beside the softphone, such as "3 missed calls", which keeps the rest of the page clear; click it to see the cards again. They stay folded in that browser until a new missed call comes in, which opens them again. On a phone or a narrow window they start folded as that button, so they never cover the bars at the bottom of the screen: a new missed call only updates its count, and tapping it shows the newest card. When the softphone is open so tall that the button would reach the top of the screen, the button is left out and the bell's count shows the missed calls. A card usually appears a few seconds after a call stops ringing in your browser without being answered, and otherwise within 30 seconds. The same missed call is in the bell, so marking it read or clearing it there takes the card away too.

One notice per action. A batch is one notice, never one per record: assigning 50 contacts to someone sends them one notice, "Sarah Lim assigned you 50 contacts". You are never told about your own actions, except a long job you started finishing.

What you are told about: 1. Contacts assigned or shared with you, one at a time or in bulk (Assign to User, Move to). When your contacts are moved to someone else or unassigned, you are told too. 2. A task someone else gives you. 3. A deal won or lost: the deal's owner and every Super Admin. Deals have no separate assignee, so the person who logged a deal is its owner. 4. A reply to a campaign email: the person who sent it, the contact's owner and the campaign's creator (a paused or removed member's alert goes to the Super Admins instead). 5. A teammate booking a meeting with your contact (moving them to Appointment Scheduled) or marking your contact Do Not Call. 6. A teammate deleting contacts you own (one notice for the batch). 7. A teammate launching, pausing or resuming a campaign you created, in the app, through Copilot or through a connected app, a campaign of yours that was scheduled starting to send, and every campaign of yours finishing. 8. Long jobs you started finishing: adding a whole search to a company list, counting people across a company list, finding contact details in bulk, and building a list. A job that stops on its own (out of credits, the list full) says why. A CSV import and an export finish while you watch, so they do not send one. 9. A suggested email or Office Number you sent for approval being approved or rejected, and a suppression request being reviewed. 10. A teammate joining (an invited member signing in for the first time, or accepting an invitation): the Super Admins and whoever invited them. 11. A mailbox that needs reconnecting (its sign-in stopped working, or for a mailbox connected with an email server and password, the server stopped accepting its password) or that is paused for the day: the mailbox's owner and the Super Admins. Each is told once, when it breaks, not on every send that tries it, and about the same mailbox at most once a day. A single refused login is checked with a fresh login first, and a server that is only busy or briefly unreachable never counts. While a mailbox's password is refused, its campaign emails wait, without using up their tries. HuntSales tries the login again every 30 minutes and sends them once it works, and a Test that passes sends them straight away. A mailbox whose Test fails holds its emails the same way until its login works. An email still waiting once the mailbox has been held for 7 days fails, as one that runs out of tries does, and that step is sent again later or the contact stops. 12. Money: AI credits running low, credits for People Search, adds and email finds running low (when what a search, an add or an Add all finally costs, once it has handed back what it did not use, takes them down to the level where the low-credit banner appears; at most once a day, never once per search), a failed plan renewal payment, low calling credit and a failed calling top-up go to the Super Admins.

Muting. Open My Profile, Notifications to choose which types show in your own bell: turn a switch off and that type stops showing for you, and its count leaves the red badge. It only changes your bell, not anyone else's, and nothing is lost: turn it back on and what came in meanwhile is there. Alerts about money, mailboxes, tasks given to you, mentions, missed calls and support cannot be muted there. Admins can also mute some automatic alerts for the whole workspace on the Settings page (Notification preferences).