The bell icon in the top-right of your provider dashboard is your real-time feed of activity on your listings. This article explains what each notification means, how the bell behaves, and which events also reach you by email.
There are eleven kinds of notifications today:
| Notification | When you get it | Where it takes you |
|---|---|---|
| New registration | A customer completes a session registration | Session roster, with the participant's drawer open |
| Drop-in registration | A customer completes a drop-in date purchase | That drop-in date's roster |
| Cancellation request | A customer asks to cancel a registration or be refunded | Session roster, with the participant's drawer open |
| Transfer request | A customer asks to move a registration to another session of the listing | Session roster, with the participant's drawer open |
| Waitlist signup | Someone joins the waitlist on a full session | Session waitlist tab |
| Scholarship application | A customer submits a scholarship application | Scholarships page, with that application open |
| Message not sent | A scheduled message could not go out when its time came | The message, whose page gives the reason |
| Payment past due | A payment plan or monthly payment could not be collected, even after trying again. Nothing is cancelled; you decide what happens next | Session roster, with the participant's drawer open |
| Enrollment cancelled | A customer cancels a monthly enrollment. It ends on the last day of the month | Session roster, with the participant's drawer open |
| Charge disputed or Charge questioned | A customer's bank disputes a charge, or asks about it first | Session roster, with the participant's drawer open |
| Dispute lost | The bank decides a dispute in the customer's favor | Session roster, with the participant's drawer open |
Each notification carries the relevant context inline, such as the participant's name and the session, so most of the time you can decide whether to act without leaving the bell dropdown. A scholarship application names the participant and the listing only; the applicant's answers stay on the Scholarships page.
To answer a transfer request, see Transferring Registrations and Answering Transfer Requests. To answer a cancellation request, see Processing Refunds & Cancellations.
The red badge on the bell shows your unread count. If you have more than 99 unread notifications, it shows "99+" rather than the exact number.
Click the bell to open the dropdown. The most recent 20 notifications appear first, and more load as you scroll back. Unread notifications have a subtle blue background; read notifications are white.
You can mark a single notification as read by clicking it (which also navigates you to the relevant page), or mark everything as read at once with the Mark all as read button at the top of the dropdown.
On your listing, roster and form-editing pages, the unread count refreshes about once a minute while the tab is open and active. When you switch away from the tab the refresh pauses; when you come back it resumes immediately. On other dashboard pages, the count updates when the page loads.
If you need to be certain you're seeing the latest state, reload the page. It forces a fresh read.
The bell itself sends no email. Most of the same events also send an email, separately:
| Event | |
|---|---|
| New registrations, waitlist signups and scholarship applications | Sent to your organization's email address, with a copy to every team member who has email notifications turned on in their account settings |
| Cancellation requests and transfer requests | Sent to your organization's email address |
| Payments past due, cancelled monthly enrollments and disputed charges | Sent to your organization's email address, with a copy to every team member who has email notifications turned on in their account settings |
| A message that could not be sent | None. The bell and the message's page are the record |
If your organization has no email address on its profile, registration, waitlist and scholarship emails go to the first team member on the account instead, and transfer request emails are not sent. Keep the organization email current so requests reach you.
Your customers receive their own emails for registrations, cancellations, refunds, transfers and invitations. Those are listed in Emails Your Customers Receive.
If your organization has more than one user on the account, each user has their own bell. Every event creates a separate notification for every user in the org. Reading one user's notification doesn't mark it read for the others.
This is intentional. It means your front-desk staff and your director can each manage their own notification queue without stepping on each other. A practical implication: if you're trying to confirm whether a teammate has handled a cancellation or transfer request, look at the relevant roster page rather than the bell. The bell only tells you about your read state.
I didn't get a notification for a sale that happened. Where is it?
First check whether the badge count is up to date. If your tab was inactive for a while, the count refreshes when you return to it. If the sale appears in your Sales Report but no notification ever appeared in the bell, contact [email protected] with the order number and we'll investigate.
Can I turn off certain notification types?
Not currently. Every notification type is always on for every provider user. If you don't want to act on a particular notification, you can mark it read and move on. Email copies of registrations, waitlist signups and scholarship applications follow the email notifications setting on your account.
Can I get notifications by text instead?
Not at this time. If this would be useful for your operation, let us know. We track requests for additions to the notification system.
My teammate marked something as read, but it's still unread for me. Is that a bug?
No. Each user in an organization has their own independent read state. See Multi-user organizations above.
How far back does my notification history go?
Notifications are kept indefinitely. Scroll the dropdown to view the full history.
A cancellation or transfer request notification disappeared. What happened?
The customer withdrew the request before you answered it. When that happens, the notification is removed, because there is nothing left to answer.
The bell shows a notification but the page it links to doesn't show what I expected. What happened?
Most often the situation changed after the notification was created, for example a teammate already answered the request. The linked page always reflects the current state. Contact support if this happens unexpectedly and we can confirm what occurred.