Notifications.
Notifications are how Booth Studio tells you that something needs you. This guide covers what Booth Studio tells you about, who hears it, and how to choose what reaches you.
The bell
Notifications are how Booth Studio tells you that something needs you: a lead handed to you, a contract signed, a follow-up due this morning. They collect behind the bell, one list per person, so what reaches you is yours and nobody else’s.
Two things live at the bell, and they are different. The number on it says how many notifications you have not read yet. The list inside it is what is waiting for you, read or not. Reading a notification takes it off the number but leaves it in the list; only dismissing it, or the problem it is about being resolved, takes it out of the list.
- On a laptop or desktop. The bell sits in the header of every page, beside Help. Click it to open your notifications; View all notifications at the foot opens the Notifications page, with your history.
- On a phone. The bell sits in the header at the top of the screen, with the same number on it, and tapping it opens the Notifications page - a full page of its own rather than a small panel.
- The number. It counts up to 9 and then shows 9+; a screen reader hears the exact number. With nothing unread there is no number at all. It goes up by one when a notification arrives and down by one when you open or dismiss an unread one.
- One list per business. If you belong to more than one business, each has its own notifications and its own settings. The bell shows the business you are working in, and switching business switches it too.
Opening the bell changes nothing. Nothing is marked read and nothing disappears because you looked: you might open it, glance at one notification and close it without having dealt with the others.
If the person a notification is meant for has left the business, or their role no longer lets them receive that kind of notification, it goes to someone who can act on it instead - in the end, every Owner and Admin. Someone accountable is always told. The sections below say who hears each kind first.
You are never notified about something you did yourself. Making yourself the owner of a lead tells nobody, because you already know.
Needs attention and Recent updates
Inside the bell your notifications are in two groups. Needs attention comes first: alerts that wait on someone, such as Submission waiting for review, Submission needs attention, Task overdue and New lead with no owner. Recent updates follows: news, such as a new inquiry, a lead assigned to you or a contract signed. A group with nothing in it is not shown, and when both are empty the bell says you are all caught up.
- Needs attention. An alert stays here until the problem it is about is resolved, or until you dismiss it. Reading it clears its highlight and takes it off the number, but it stays under Needs attention - reading about a problem does not solve it - and time does not clear it either.
- Recent updates. An update you have not read stays until you read it, however old it is. Once you have read it, it stays for 7 days - so you can open again something you checked yesterday - and then moves to History. Dismiss it if you want it gone sooner.
- Unread stands out. An unread notification has a tinted background, a dot and a bolder title. One you have read is plain, wherever it is.
Reading a New inquiry notification does not mean the lead has been followed up. That lives on the lead itself - its stage and its follow-up date - not in the bell.
Reading, dismissing and resolving
Three different things can happen to a notification, and each does exactly one job.
- Read. Click a notification, in the bell or on the Notifications page, and it opens the lead, event or document it is about and is marked read: its highlight goes and the number drops by one. It stays where it was. One with nothing to open is marked read where it stands.
- Dismiss. The X beside a notification dismisses it: it moves to History, and if it was unread the number drops by one. Where it was, you see Dismissed and an Undo button, and nothing else in the list moves. The line names the notification - its title, with its details underneath - so two with the same title can be told apart. Press Undo to put that notification straight back in its place. A double-click counts as one press, so it never undoes the dismiss it just made.
- Resolved. When the work behind an alert has been done - a held submission accepted or discarded, a failed submission filed by Retry, an overdue task marked done or deleted - the alert leaves Needs attention on its own, for everyone who received it, and moves to History marked Resolved. What ends each alert is listed below.
Dismissed several by mistake? Each one keeps its own Dismissed and Undo, so you can put back any of them, one at a time and in any order, for as long as the bell stays open. On the Notifications page they stay until you switch tab or leave the page. Once you close the bell they are simply in History, and Move to inbox there brings one back.
Read and dismissed are yours alone. Reading an alert does not clear a teammate’s number, and dismissing it hides your copy only - it does not complete the task, accept the submission or fix the error, and everyone else still sees theirs. Read is read everywhere you are signed in: one opened on your phone is read on your laptop too.
Mark all as read clears the number for everything in front of you. Nothing moves and nothing is dismissed, and anything that arrives while you are looking stays unread, so nothing is cleared before you have seen it. A notification you have dismissed is not in front of you, so it keeps its unread: moved back to your inbox, it counts again.
- With a keyboard. Tab to a notification’s Dismiss button and press Enter. The keyboard moves to that notification’s Undo, in the same place, and back to its Dismiss if you undo. A screen reader hears each Undo named for its notification - its title and its details - so two with the same title are told apart, and hears every dismiss and every Undo, even two alike in a row.
- If it cannot be saved. If a notification cannot be marked read, dismissed or moved back - you have lost your connection, say - it goes back to how it was and the bell or the page says so. An Undo that does not go through says so on its own line and keeps its Undo button. Try again in a moment.
The number counts notifications only. Leads, Messages, Tasks and Crew keep their own counts beside their names in the navigation.
- When the record is gone. If a lead, event or document is deleted after you were told about it, the notification stays so your history still reads, but it no longer opens anything.
- Cleared 90 days after it is dealt with. A notification is cleared away 90 days after it was last read, dismissed or resolved. One still waiting for you - an alert whose work is not done, an update you have not read - is never cleared by time. The records they pointed at are untouched.
What ends each alert
An alert stays under Needs attention until the work behind it is done. Then it leaves on its own, for everyone it was sent to, and waits in History marked Resolved. Reading it never ends it, and neither does time passing. Dismissing it only hides your own copy: the work is still there, and so is everyone else’s alert.
- Submission waiting for review. It leaves once someone accepts or discards the submission.
- Submission needs attention. It leaves once Retry files the submission, or someone discards it.
- New lead with no owner. It leaves once the lead has an owner on the team, or is won, lost, archived, deleted or turned into an event.
- New event with no owner. It leaves once the event has an owner on the team, or is cancelled, archived or deleted.
- Booked from an accepted proposal. It leaves once every unit the event needs has been assigned, or the event is cancelled, archived or deleted.
- Invoice not sent. It leaves once the invoice is sent - by hand from the event’s Financials tab - or is paid, voided or deleted, or its event is cancelled or deleted.
- Follow-up due today. It leaves once the follow-up date is cleared or moved to another day, or the lead is won, lost, archived, deleted or turned into an event.
- Task overdue. It leaves once the task is marked done or deleted, its due date is cleared or moved, or - for a task on an event - its event is cancelled or deleted.
- Invoice overdue. It leaves once the invoice is paid, voided or deleted, its due date is cleared or moved, or its event is cancelled or deleted.
- Texting registration decisions. Only a request for a change is an alert; an approval arrives as an update. A request for a change leaves once the carriers approve the business, the change goes back to them for review, or the number is released.
- Calendar needs reconnecting. It leaves once Google Calendar is signed in again, or the connection is removed.
- Billing problems. It leaves once the subscription is back in good standing, or once the problem changes - a failed payment turning into an ended subscription, say - and the new problem arrives as a notice of its own.
- Automation waiting for review. It leaves once the run is out of review - someone retries, skips or cancels it - or, for a send it left in doubt, once someone records what they found or the provider settles it.
- Reply needs a person. It leaves once someone on the team picks up the conversation and resolves the hand-over, or the hand-over lapses by itself.
- Automated messages cannot send. It leaves once the business can send on that channel again: an email connection that works, or texting that is approved and live.
An alert about something that has since been deleted - a lead, an event, a task, an invoice, a form submission - ends too, because there is nothing left to do. Booth Studio checks whenever your bell or the Notifications page refreshes, so an alert leaves shortly after the work is done, even if a teammate did it.
History
The Notifications page has two tabs. Inbox is the bell in full: Needs attention, then Recent updates, with older updates behind Load more updates. History is everything that has left the inbox, newest first, each one labelled with why:
- Dismissed. You dismissed it. Move to inbox puts it back - and back on the number if you had not read it. An update you read more than 7 days ago would only come straight back here, so it has no Move to inbox.
- Resolved. The problem it was about has been dealt with, so there is nothing left to do and nothing to move back.
- Read. An update you read more than 7 days ago. Updates move here by themselves 7 days after you read them; one you have not read stays in your inbox until you do.
A notification in History still opens its record, as long as the record is still there. On a phone, the bell in the header opens the Notifications page, and History is the second tab.
Pop-ups
While Booth Studio is open, something new does not only wait in the bell: it pops up. A small card appears in the bottom-right corner of the screen on a laptop or desktop - above the reply box in Messages, or a step’s Continue, when one of those is down in that corner. On a phone the bottom of the screen is the navigation bar, so it comes down from the top instead, just under the header.
- What pops up. Every new notification that reaches your bell - the kinds switched on for the app in Settings › Notifications - and every new email, text or call to the business that you have not read yet. Never something you did yourself, and never anything that was already there when you opened Booth Studio, so refreshing the page brings nothing back.
- About 10 seconds. Each pop-up goes by itself after about 10 seconds. It waits while your pointer is over the pop-ups or your keyboard is in them, and while Booth Studio is in a tab you are not looking at, then carries on from where it was. Up to 3 show at once, the newest on top; any more wait their turn.
- Click to open. Click a pop-up to open what it is about. A notification opens its lead, event or document and is marked read, as it is from the bell; one with nothing to open takes you to the Notifications page. An email, text or call opens that contact’s Messages tab, or Messages when it came from someone who is not a contact yet.
- The X only hides the pop-up. Its X, or Escape, takes the pop-up away and nothing else. The notification stays unread in the bell and the message stays unread in Messages until you open them.
When a lot arrives at once - the morning reminders, say, or the last few minutes after Booth Studio has been in a tab you were not looking at - only the newest few pop up, and the rest are waiting in the bell and in Messages rather than arriving as a pile of pop-ups. After a longer gap, a sleeping computer for instance, nothing older than 10 minutes pops up at all.
- Turning them off. Settings › Notifications has one switch at the top, Show pop-ups while I’m using Booth Studio. It applies to the device you are using, and to the business you are in, so you can quieten your phone and keep them on your laptop. With it off nothing pops up; notifications and messages still arrive in the bell and in Messages as before.
- With a keyboard. Press F8 to jump to the newest pop-up - it waits while you are in it. Enter opens the one you are on; Escape or its X dismisses it and moves you to the next pop-up, or back to where you were when none are left. Pop-ups also come after the page in the Tab order. A screen reader hears the title of each pop-up as it appears.
Assigned to you
When a lead or an event becomes yours because somebody else made it so, you hear about it straight away.
A new lead or event that arrives with no owner is a different problem: nobody is going to pick it up by accident. Those go to every Owner and Admin in the business, so one of them can give it an owner. Members do not receive them.
Leads, events and contacts can only be given to someone on the team now. A new lead whose default owner has since left the business, or an event made from a lead whose owner has left, arrives with no owner - and the Owners and Admins hear about it like any other.
When a teammate leaves - removed in Settings › Team & Crew, or deleting their own account - the person doing it first chooses a teammate to take over. Everything the leaver owned in the business moves to that teammate in the same step: their leads, events and contacts, archived ones included, the open tasks assigned to them, and new leads too if new leads were routed to them. The person taking over gets one Records handed to you notification that counts what arrived and from whom, rather than one for every record. Records still owned by someone who left before this was in place are handed to an Owner of the business, who is told the same way.
- Lead assigned to you. Someone else makes you the owner of a lead, or a new lead is routed to you. Arrives under Recent updates. In the bell and by email.
- Event assigned to you. Someone else makes you the owner of an event. Arrives under Recent updates. In the bell and by email.
- Task assigned to you. An Owner or Admin gives you a task, on an event or a general one. Arrives under Recent updates. In the bell and by email.
- New lead with no owner. Owners and Admins hear about new leads nobody owns yet. Waits under Needs attention. It leaves once the lead has an owner on the team, or is won, lost, archived, deleted or turned into an event. In the bell and by email.
- New event with no owner. Owners and Admins hear about new events nobody owns yet. Waits under Needs attention. It leaves once the event has an owner on the team, or is cancelled, archived or deleted. In the bell. Its email starts switched off.
- Records handed to you. Someone leaves the business and their leads, events or contacts are handed to you. Arrives under Recent updates. In the bell and by email.
Client activity
When a client acts on a document you sent them - accepts it, signs it or submits their answers - you hear about it as it happens, without having to open the document to check. It goes to the teammate who sent the link. If they have left the business, every Owner and Admin hears instead, and whoever made the document hears with them if they are still on the team.
The page a client is sent offers a single Accept button, and signing waits until they press it, so a client accepts rather than declines. A document comes back declined only from a page the client opened before the Decline choice was taken away, and that is announced too.
A client accepting a proposal written for a lead also books the event: the lead is won and its event is created on your Confirmed stage, with no units chosen. Whoever runs the event is asked to assign them - every Owner and Admin when nobody runs it - and the alert stays until every unit is picked.
A client opening or reading a document does not ring the bell. The document’s audit trail records every opening; the bell is kept for the moments that need a reply.
Emails are the exception you can choose. When your business tracks email opens - an Owner or Admin turns it on in Settings › Email - the first time an email you sent a client is opened, you get Email opened. It comes once per email; how many times it was opened since, and when, is on the email in the conversation. It says the email was opened, not who opened it: everyone copied on an email shares one tracking image, and Apple Mail can hide opens altogether.
- Client signed or submitted. A client signs, accepts or submits a document you sent. Arrives under Recent updates. In the bell and by email.
- Client declined. A client declines a proposal you sent. Arrives under Recent updates. In the bell and by email.
- Booked from an accepted proposal. A client accepts a proposal, the event is booked, and its units need assigning. Waits under Needs attention. It leaves once every unit the event needs has been assigned, or the event is cancelled, archived or deleted. In the bell and by email.
- Invoice not sent. An invoice Booth Studio was sending on its own - when a client accepted, or a balance invoice on its day - could not go out. Waits under Needs attention. It leaves once the invoice is sent - by hand from the event’s Financials tab - or is paid, voided or deleted, or its event is cancelled or deleted. In the bell and by email.
- Email opened. The first time an email you sent a client is opened - once per email. Emails Booth Studio sends by itself go to the event’s owner, or to Owners and Admins. Arrives under Recent updates. In the bell. Its email starts switched off.
Reminders
Every morning Booth Studio looks at what is yours and due, and leaves a reminder for each item. Reminders go to whoever owns the lead or the event. When nobody owns it, or its owner has left the business, they go to every Owner and Admin instead, so nothing falls due for nobody.
- Follow-up due today. The morning a lead you own is due for a follow-up. Waits under Needs attention. It leaves once the follow-up date is cleared or moved to another day, or the lead is won, lost, archived, deleted or turned into an event. In the bell, and counted in your morning summary email.
- Task overdue. Once a task passes its due time - the next morning for a task due on a day with no time. Goes to the person it is assigned to, else the event’s owner, else whoever added it. Waits under Needs attention. It leaves once the task is marked done or deleted, its due date is cleared or moved, or - for a task on an event - its event is cancelled or deleted. In the bell, and counted in your morning summary email.
- Event tomorrow. The morning before an event day you own. Arrives under Recent updates. In the bell, and counted in your morning summary email.
- Invoice overdue. The morning after an invoice on an event you own passes its due date unpaid. Waits under Needs attention. It leaves once the invoice is paid, voided or deleted, its due date is cleared or moved, or its event is cancelled or deleted. In the bell, and counted in your morning summary email.
Reminders are written from 7am in your business’s time zone - the one set in Settings › Contact & location - so they are waiting at the start of the working day rather than arriving at midnight. A follow-up moved to today after the morning’s reminders were written still reaches the bell later that day, and so does a task due at a time once that time has passed.
By email, reminders never arrive one at a time. You get at most one summary per business each morning, and only when something is due: a count of each kind, such as “2 follow-ups due today” or “1 invoice overdue”, with a link to the Notifications page. The summary is only sent between 7am and 11am in your business’s time zone. A reminder that first turns up after that is in the bell only, never an email of its own, and a summary that has not gone out by the end of its day is not sent at all - yesterday’s reminders never arrive dressed as today’s.
Overdue reminders are news, not history. Booth Studio reminds you about tasks and invoices that fell overdue in the last 3 days; anything older is not announced again, and it stays where it always was - on the Tasks page and on the event.
Business health
Some things concern the whole business rather than one lead or event, and only an Owner or an Admin can put them right. Texting, calendar and billing notices go to every Owner and Admin. Members never see any of these, and if someone’s role changes to Member, the ones already in their bell disappear.
Invitation accepted goes to the person who sent the invitation, and opens Settings › Team & Crew, where the newcomer now appears. If the sender has since left the business or become a Member, every Owner and Admin hears instead.
- Texting registration decisions. The carriers approve your business for texting, or need something changed. An approval arrives as an update; a request for a change waits under Needs attention. A request for a change leaves once the carriers approve the business, the change goes back to them for review, or the number is released. In the bell only.
- Calendar needs reconnecting. Google Calendar asks the business to sign in again before events can sync. Waits under Needs attention. It leaves once Google Calendar is signed in again, or the connection is removed. In the bell and by email.
- Billing problems. A subscription payment fails or the subscription ends. Waits under Needs attention. It leaves once the subscription is back in good standing, or once the problem changes - a failed payment turning into an ended subscription, say - and the new problem arrives as a notice of its own. In the bell and by email.
- Invitation accepted. Someone you invited joins the business. Arrives under Recent updates. In the bell. Its email starts switched off.
Texting registration decisions has no email switch. Owners are already emailed about every carrier decision by the texting setup itself, and a second email would only say the same thing.
Forms
A published form announces what it files, as New form submission. A new inquiry goes to the owner of the lead it created, or to every Owner and Admin when that lead has no owner. A client’s booking details go to the owner of the event they updated, or to every Owner and Admin when the event has no owner. A contact sign-up goes to every Owner and Admin - or, when the person is already a contact, to that contact’s owner. A submission held for review, or one that could not be filed, goes to every Owner and Admin, and only to them: Members are not sent those two and have no switch for them.
- New form submission. Someone sends one of your forms: a new inquiry, a contact sign-up or a client’s booking details. Goes to the owner of the lead or event, or to Owners and Admins. Arrives under Recent updates. In the bell, and by email when the form’s settings send one.
- Submission waiting for review. A submission looked automated and is held until someone checks it. Waits under Needs attention. It leaves once someone accepts or discards the submission. In the bell, and by email when the form’s settings send one.
- Submission needs attention. A submission could not be saved into the CRM and needs a retry. Waits under Needs attention. It leaves once Retry files the submission, or someone discards it. In the bell, and by email when the form’s settings send one.
The new form submission email is the one notification email that names the person: it says who sent it and through which form, and links to the lead, event or contact it filed. It never carries the answers themselves. A form’s own settings decide whether it sends emails at all, and each person can also switch them off for themselves in Settings › Notifications. The Forms guide covers the rest.
Automations
Your automations speak through the bell too. An alert step in an automation sends Automation alerts to whoever it names, with the words the step was given. The other three are about automations that need a person: a run that stopped at a step it could not finish, a client reply nobody could match to one automation, and messages that cannot send because the business’s email or texting is not working. Automation waiting for review and Automated messages cannot send go to Owners and Admins only, because retrying a run and fixing a connection are theirs to do.
- Automation alerts. One of your automations has something to tell you about a lead, an event, a contact or a task. Arrives under Recent updates. In the bell and by email.
- Automation waiting for review. An automation stopped at a step it could not finish on its own - a send it could not confirm, or retries that ran out - and waits for someone to retry, skip or cancel it. Waits under Needs attention. It leaves once the run is out of review - someone retries, skips or cancels it - or, for a send it left in doubt, once someone records what they found or the provider settles it. In the bell and by email.
- Reply needs a person. A client replied and more than one automation was following up with them, so nobody could tell which one the reply answers. Their follow-ups wait until someone on the team picks it up. Waits under Needs attention. It leaves once someone on the team picks up the conversation and resolves the hand-over, or the hand-over lapses by itself. In the bell and by email.
- Automated messages cannot send. Your email or texting is not working, or is not set up, so automated messages are waiting or were skipped. Arrives at most once a day per channel. Waits under Needs attention. It leaves once the business can send on that channel again: an email connection that works, or texting that is approved and live. In the bell and by email.
The Automations guide covers runs, review and stopping everything.
Notification settings
Settings › Notifications is where you choose what reaches you. The gear at the top of the bell and of the Notifications page opens it too, and so does the link at the foot of each alert and morning summary email. The choices are yours alone and belong to the business you are in: changing them changes nothing for your teammates, or for you in another business.
- Find the notification. Every kind you can receive is listed, grouped the way this guide is. A Member does not see Business health, the no-owner notifications, held and failed form submissions or the Automations notifications only Owners and Admins receive, because they never receive them.
- Switch In app on or off. Off, and that kind stops appearing in your bell, and so stops popping up. Switched back on, it shows new ones from then on; the ones raised while it was off stay hidden.
- Switch Email on or off. Off, and that kind is not emailed to you. Reminders are never emailed one by one either way: switching one on adds it to your morning summary.
Out of the box everything shows in the bell. New event with no owner, Email opened and Invitation accepted start with email switched off; everything else is emailed until you say otherwise.
Above the list, Pop-ups has a switch of its own. Unlike the rest of the page it is kept on the device you are using rather than with your account - see Pop-ups above.
The list follows the role you hold now. If your role changes while the page is open and you switch a notification your new role no longer receives, the page says so and that notification leaves the list.
Email goes to the address you sign in with, and only once that address is verified. Until it is, the settings page says so and nothing is emailed, whatever the switches say.
Notification emails
Notification emails come from Booth Studio itself, not from your business’s email address, and they go to the address you sign in with.
- One line and a link. An alert says only what kind of thing happened - “A lead was assigned to you” - with the business’s name, a button that opens it in Booth Studio, and a link to your notification settings. It never names a client, an event or an amount: a mailbox is forwarded, shared and kept long after the work is done, so the details stay behind your sign-in.
- One morning summary. Reminders are counted rather than listed, in at most one email per business each morning - sent between 7am and 11am in your business’s time zone - and only when something is due.
- Checked just before it goes. Before any notification email is sent - an alert, a morning summary or a form’s email - Booth Studio checks that you are still on the team, may still receive it, still have that email switched on and still have a verified address - and, for an alert, that you have not already read or dismissed it in the app and that what it is about still needs someone. If not, the email is not sent. A morning summary counts only the reminders you have not dismissed and whose work is not yet done.
- The exception - new inquiries. The email a form sends for a new inquiry names who sent it and the form it came through, as the Forms guide describes.