The Notifications Bell and the Morning Digest

The bell in the header is the platform’s way of saying something happened while you were doing something else. A new offer in a deal room. An ITAD partner bidding on your pickup request. A support ticket that just breached its SLA. The bell counts them, the notifications center lets you find them again, and e-mail exists for the hours you are not in the app at all.

The bell

The bell shows an unread count and opens a panel of your recent notifications, each linking to the record it is about. Mark all read clears the count in one click. The count itself updates over a live channel on the notifications table, so something that happens while you are staring at the screen arrives without a refresh.

The notifications center

/notifications is the full list. Search and the domain filters — Market, Auction, Pickups, Support and Account — are applied to all of your notifications before the current page is chosen, and the footer shows the visible range, the total number of matches, and a jump to any page or page size. A notification is meant to take you to a record and then get out of the way. It is the doorbell, not the meeting.

What actually fires one

Market: new matches against your intent criteria, offers received, accepted, rejected, countered or expired, deal status changes and deal-room messages. Auction: bids, outbid alerts, an auction ending, a lot settling, a scheduled lot going live, plus the two watchlist events — a bid on something you watch and something you watch about to end. Pickups: a request published, a new match in your coverage, bids received, updated, retracted, accepted or rejected, a request awarded, a pickup scheduled or completed, a certificate ready, and the three approval events. Support: a ticket created, an operator or tenant reply, a status change, a rating request and an SLA breach. Billing: an invoice issued and a storage-quota warning. Then system messages. That is the list — an asset moving to the next stage does not ring a bell.

The morning digest

Users on the daily-digest cadence get one e-mail from a cron at 06:00 UTC covering everything since their last digest. Each notification is its own row in it — type, title, the opening of the body, and an Open link back to the record — because a summary that folds five events into one sentence hides which of the five mattered. Users on the immediate cadence are served by a separate job that runs every 15 minutes, so an urgent thing is a quarter of an hour away at worst.

Language, and the plumbing behind it

Notification e-mails are written in the language of the person receiving them — their account preference, otherwise their browser language, otherwise English — never the language of whoever triggered the event. The provider that actually delivers them is configured by the platform team under /admin/email-provider. That is delivery plumbing; it has no opinion about what a notification means.