Messages waiting and the notification bell

The messages icon and the bell sit together in the top bar, but their numbers mean different things. Messages counts conversations the shop still owes a human answer. Notifications counts feed items this signed-in person has not seen. Neither number is a count of rows in the small drawer.

What waiting means in Messages

A conversation is waiting when its latest real message came from the customer, or when the only answer after it was automatic. An after-hours or other automatic reply acknowledges the message but does not pretend a person handled it. The conversation stays waiting until a human shop reply becomes the latest message.

The badge is a full-shop count over every live, unarchived conversation you may open. The drawer is only an eight-thread peek at the same inbox. When twelve conversations need answers and eight waiting rows fit in the peek, it says 12 waiting · showing 8. Open Messages to work the whole inbox; the summary never turns eight displayed rows into a false total of eight.

Use All to see the newest peek whether answered or not, or Unresponded to keep only its waiting rows. Both chips read the one stored classification the badge counts, so a chip and the number above it cannot disagree. Internal notes do not count as a customer or automatic reply. Demo and test threads are excluded from a live shop's count, and another organization cannot contribute to it.

Reading a row in the messages panel

Each row is the customer's initials, their name, how long ago the last line landed, that line itself, and who is looking after the conversation — a person's name, or Unassigned.

The preview is prefixed with whoever said it: You when the shop spoke last, the customer's own first name when they did, Auto-reply when the only thing after them was automatic, and Note when the last line was internal. It comes from the same stored classification the chips and the badge use, so a row cannot read You while the count above it treats that conversation as waiting.

A number on the corner of the initials is that thread's unread count, which is a third question again: how many inbound messages nobody at the shop has opened.

In the panel's header, the magnifier opens a search box that hands the question to the whole inbox rather than filtering the eight rows in front of you — a real name that happens to be the ninth conversation must not come back as nothing. The plus beside it starts a new message, and because a conversation here is one per customer it goes to the customer list to ask which one. It is only drawn for roles that may open that list.

At the foot, Open Messages is always drawn. When nothing matches, the panel says No conversations yet. under All and Everybody has been answered. under Unresponded, because those are different facts and deserve different sentences.

The bell and what it reports

The bell opens a separate feed for selected events: customer authorizations, payments and refunds, bookings, completed inspections, received parts, QC bypasses, discount decisions, closed disputes, new work requests, mentions and support replies. It is deliberately not every audit event and it omits your own routine actions. Each row links only to a screen your role may open.

A row is the kind of event in small capitals, the sentence, when it happened, and the car or person it is about. A payment against an invoice the shop has marked settled also carries a Fully Paid pill, because a deposit and a final settlement otherwise read identically and only one of them means the car can go. The pill follows the invoice as it stands now, so a refund that reopens the invoice takes the pill with it, and it never appears beside a refund.

A finished chargeback appears as Dispute won, Dispute lost or Dispute withdrawn, naming who recorded the outcome, and it opens the dispute rather than the order — a dispute may name no order at all. Withdrawn is drawn as neither good news nor bad, because nobody won it; the processor simply stopped asking.

A Work request row means somebody wrote in through your public form and nobody has answered yet. It leaves the feed as soon as the enquiry is moved out of the new state, and no score ever hides one: the lead queue sorts on its spam score and never filters, and a bell that quietly dropped an enquiry would lose exactly the work the queue exists to catch.

Both new rows are gated on the doors they open. A closed dispute is shown only to somebody who may take payments, which is the key the dispute screen itself asks for, and its figure is printed only for somebody who may see revenue — the row still arrives either way, with Amount hidden — money visibility is off for your account where the money would be. A work request needs the customers key, which is the front desk as well as the advisor.

A disputed amount is shown in the dispute's own currency rather than the shop's. The figure is frozen from the payment that was charged back, and a cross-border charge must not be relabelled by the surface reporting it.

Seen, read, and the full page

Opening the bell marks the newest feed item as seen for your membership, clears the badge optimistically and leaves the new markers visible in the open drawer so you can still tell what just arrived. Mark all read in the panel clears those markers on the copy you are looking at. It is not a second write — opening the bell already did the writing — and it disappears once there is nothing left to clear.

The same list has a no-JavaScript page at /notifications, reachable from Open Notifications at the foot of the panel and by following the bell itself. There, use Mark all seen when unread items remain; that one does advance the watermark on the server.

Beside that door, Notification settings opens the Notifications card of Your profile — the same screen the account menu reaches as Your notifications, where you choose which kinds count against your own badge. It is a separate control with a separate name because it settles a different question from the list beside it, and switching a kind off there stops it counting rather than stopping it arriving.

The full page is headed Notifications and says What happened while you were working — not the audit trail. With nothing in it, the page and the panel say the same sentence: Nothing yet. Approvals, payments, bookings, work requests, finished inspections and anyone naming you land here.