Notifications and the bell
The bell in the top navigation is where 1pm tells you something has happened that you might want to act on: a new lead, a signed confirmation, a payment landing, a bounced email. It updates live, so you do not have to go looking. A small number on the bell tells you how many items are waiting, counting up to "9+" and no further.
What the bell tells you about
Notifications come from across 1pm. The ones you will see are:
New lead. A fresh lead arrived through one of your forms.
Lead reply. A lead replied on their thread, or acted on a quote you sent (accepted it, asked for changes, or asked a question).
Confirmation signed. A client signed off an event confirmation. A booking won.
Confirmation declined. A client declined a confirmation. Worth a look, because the booking may be at risk.
Payment received. A client paid an invoice online. The item names who paid (the name and business the invoice is billed to) and the event date. 1pm also emails you, with who paid, the amount, the invoice or confirmation number, the event date and what is still owing.
Payment declared. A client said they will pay by bank transfer from the public confirmation page. A promise, not money, which is why it is a separate item from Payment received: it tells you to expect a transfer rather than chase an apparently dead booking.
Payment overdue. A signed confirmation's deposit, progress payment or balance has passed its due date. The bell names which payment, how much, and who owes it. This one is a nudge to you. To email the client as well, turn on the Booking payment overdue automation.
Email bounced. An email you sent a lead did not get through, so they never received it. Check the address or reach out another way.
Requests complete. A crew member finished everything you asked them for. Fired once, the first time they go from outstanding to complete, so someone who edits an answer afterwards does not notify you again.
Guest numbers or hours changed. A client with a signed booking changed their guest count or their hours before your final numbers date. The bell says from what to what, and the new total.
Auto Reply quoted a lead. An automatic reply went out carrying a quote. The bell names the lead, the quote number and the total, so you see the price a stranger was sent the same day.
Auto Reply didn't send. Auto Reply stood down on a new lead, for example because you already have a booking on that date. The lead needs an answer from you.
Couldn't email the client. An automation was due to email a booking's client, but the booking has no client contact, or the contact has no email address. Click through to the event to set one. You also get this when the email itself was not sent, for example because an email limit was reached. The notification gives the reason, and the email is not sent again by itself: send it with Send automation on the client contact's Bookings tab, or for a lead, open the lead and press Retry on the message.
An automation didn't send. A dated reminder (an invoice or quote reminder, a lead chase, a document or crew reminder) failed three times and stopped. The bell names the automation, what it was for and why, and nothing will try again, so follow it up yourself.
Couldn't email someone their link. A person registered themselves through your sign-up link, but the email carrying their private link didn't send. Press Email link on their row to send it again.
Card on file added. A client added a card on file through a link you sent.
Account share accepted. Someone accepted your invitation to share your account.
Event rescheduled. A confirmed or completed event had its date moved. Because that shifts the whole run of show and the client is holding that date, everyone on the account is told in case it was a mistake. Moving the date of a lead or a tentative booking is routine, so those stay silent.
Event deleted. A confirmed or completed event was deleted. Irreversible and high-consequence for the same reason, so everyone on the account is told and the message names who did it. Deleting a lead or a tentative booking is routine cleanup and stays silent.
Both of these use your account's own word for an event and for the run of show, if you have renamed them. Moving or deleting a sample booking never notifies anyone.
Appointment booked. A client booked a slot through your public booking page.
Appointment needs a video link. A client booked a video appointment on a Space that holds the confirmation back until you supply the meeting link. This one is actionable: adding the link is what releases their confirmation email.
Appointment cancelled and Appointment rescheduled. A client managed their own booking through the link in their confirmation. Cancelled frees the slot; rescheduled means they took a new one and released the old.
Sending domain verified, or a problem with it. Your sending domain finished verifying, its DNS records can no longer be found, or it was removed because it wasn't verified in time. The last two tell you which address your email is sending from instead.
Calendar sync failed. An external calendar feed on one of your Spaces stopped syncing, usually a moved or expired URL. Fired once when it starts failing rather than on every scan, so a broken feed does not nag.
Reading and acting on them
Click the bell to open the tray. Each item shows an icon for the kind of thing it is, a short headline, sometimes a line of detail, and how long ago it happened (shown as "now", "5m", "3h", "2d", then a date once it is more than a week old).
Click a notification to jump straight to whatever it is about: the lead, the invoice, the event, the contact. When the tray is empty, it simply says you are all caught up.
If you delete an event, the notifications that link to it are cleared from the bell at the same time, so the bell never sends you to an event that is no longer there.
The tray shows the 12 most recent items that have not been cleared. The number on the bell counts everything still active, not just the twelve on screen, so a bell reading "9+" against a short tray means there are older items behind it. That is a sign to clear as you go rather than let them bank up.
You do not need to refresh for any of this. Notifications arrive live, and there are two safety nets behind that: the bell re-checks whenever its live connection comes back after a drop, and it re-checks the moment you come back to the tab. On a flaky connection you may wait a moment, but you do not sit on a stale bell all afternoon.
Clearing notifications
An item stays on the bell until it is cleared. You can:
- Clear one with the small x beside it. The tray stays open so you can work through several in a row.
- Clear all from the link at the top of the tray. This clears everything up to the newest item the tray showed you. Anything that arrived after that stays on the bell, so you never clear a notification you have not seen.
Clearing is not the same as reading. There is no per-person read state. The bell is one shared feed for the whole account, so clearing an item removes it for everyone.
The bell when you share your account
If you share your account with a colleague, you both look at the same bell. A new lead shows for both of you, and when either of you clears it, it clears for both. That keeps a small team from each chasing the same notification, and it means nothing gets actioned twice. Behind the scenes 1pm records who cleared what, but that is for the audit trail, not something the bell shows.