The Guesty notification center is your central hub for all important account updates and actionable alerts. It is designed to help you quickly understand what is happening in your account and take action when necessary.
This article guides you through the Notification Center, its different types of messages, and how to customize your preferences.
Access the notification center
Click 
in the top-right corner to access the notification center side panel. The icon's appearance updates in real-time to reflect the status and severity of any unseen notifications.
The state of the bell icon helps you quickly identify new information:
- No badge or dot: All notifications have been seen.
- Blue dot: You have new, unseen "Updates".
- Yellow badge with a number: You have new, unseen "Alerts". The most severe alert is "Important".
- Red badge with a number: You have new, unseen "Alerts". The most severe alert is "Critical".
Navigate the notification tabs
The notification center is organized into two tabs. A number next to the tab name shows how many unread notifications are within that section.
-
Alerts: This is the default tab. It holds actionable items that may require your attention. Alerts are categorized by severity:
- Important: An issue that requires action from you or your team.
- Critical: An issue that is severely disrupting the operation of your Guesty account.
- Updates: Contains informational messages and general confirmations that do not require immediate action.
Track notifications: seen, read, and archived
The system uses two key statuses—seen and read—to help you track what you have reviewed.
Seen or unseen
The bell icon displays a badge or dot only if you have notifications you have not yet seen (you haven't opened the notification center since they arrived).
When you open the center, all items in the currently active tab ("Alerts" or "Updates") are marked as seen.
Read or unread
Unread notifications are marked with a blue dot in the list.
Mark notifications as read:
- For the Alerts tab, click the notification. This takes you to the target page to address the issue.
- For the Updates tab, click the notification or hover over it and click
to mark as read.
Mark notifications as unread:
For both "Alerts" and "Updates", hover over the notification and click 
to mark as unread.
Archive or unarchive
To archive: Hover over any notification in the "Alerts" or "Updates" tab and click 
.
To unarchive: Click 
in the pop-up menu, select View archived, hover over the item, and click 
to restore it to its original tab.
Filter your notifications
The notification center provides filters to help you efficiently sort your messages in both the "Alerts" and "Updates" tabs. Click the filter at the top of the list to narrow your view.
In the "Updates" tab, you can filter by category and toggle on "Unread only" to focus on new updates.
Perform actions in bulk
In the top-right corner, click to perform bulk actions:
- Mark all updates as read: Marks all notifications in the "Updates" tab as read.
- Archive all: Archives all current notifications in both the "Alerts" and "Updates" tabs.
- Archive all read: Archives only the notifications you have already marked as read.
- View archived: Shows all archived notifications.
- Preferences: Opens the notification preferences page, where you can customize delivery channels.
Customize your notification preferences
You can control how and where you receive notifications from your notification settings. Access this page by clicking Preferences in the notification center or by navigating to My profile > Notification settings.
Manage critical alerts
At the top of the page, you'll find the Receive all critical alerts toggle. This allows you to opt out of most system-level critical alerts. Hover over the info icon to see which alerts are included, such as "Stripe connection error" or "iCal disconnected".
When you turn this toggle off and click Save changes, a confirmation pop-up appears. Click Disable alerts to confirm. A banner will show that you have critical alerts disabled.
Important:
Turning off Receive all critical alerts only affects your personal user profile. It does not impact other users on your account. Six workflows remain active even if you opt out—task assignments, reservation comment mentions, and replies are always delivered so you never miss direct actions involving you.
Manage individual notifications
For other notifications, such as those marked "Important" or general updates, you can choose your preferred delivery channel by selecting the relevant checkboxes:
- In Guesty: See notifications via the bell icon (desktop and mobile app).
- Push: Get push alerts on your mobile device if you have the Guesty mobile app installed.
- Email: Receive notifications in your inbox.
Not every notification type supports all channels. You may only see checkboxes for the options available for each notification type.
Note:
- Certain personal and system-critical notifications are mandatory and cannot be disabled, even if you turn off the Receive all critical alerts toggle. This ensures you're always aware of direct actions involving you (e.g., "Task assigned to me", "I was mentioned") and severe account issues.
- The notification settings you see depend on your user role and permissions. If you don't see a specific notification, you are not eligible to receive it.
- Users assigned a "Cleaner/operations" role will only get notifications for tasks they are assigned to via push or in the Guesty app.
Available notifications
Payments
Important:
Failed $0 card verifications or tokenization attempts aren't categorized as actual payment transaction failures. These card-validation errors occur during pre-payment checks because of missing or incorrect details, such as a CVC, name, expiration date, or zip code. While these errors trigger "Invalid Payment Method" or "Reservation Payment Failed" notifications, they aren't processed charges and won't appear as line items in the "Payment" section.
Notification name |
Description |
Severity |
|---|---|---|
| ACH transfer on hold | One of your ACH transfers is on hold. To unblock it, you need to supply a few more details. | Important |
| ACH transfer failed | One or more of your ACH transfers failed | Important |
| ACH rfi required | We need a few more details about your business. This is a standard step to ensure your account is secure and fully compliant. | Important |
| ACH microdeposit failed | The micro-deposits that we sent to verify your bank account didn’t go through. |
Important |
| ACH business verification suceeded | Your business has been verifed successfully. Next, connect your bank account. | Important |
| Payment refunded | A payment was refunded. Enable this notification to be informed about refunds handled by a booking channel. |
Update |
| payment Bank transfer received | Update | |
| Payment overcharged | The amount collected exceeds the reservation amount. Use this notification to track errors or cancellations, and to refund the guest in time to avoid chargebacks. |
Important |
| payment authentication failed | Guest authentication for a payment has failed | Important |
| B.com invalid cc expired | Important | |
| Invalid credit card | A guest used an invalid payment method. If you receive this notification, collect a new payment method from the guest or cancel the reservation if you suspect fraud. | Important |
| Authentication required | A payment needs guest authentication. Learn how to authenticate guest payments. |
Important |
| Booking.com invalid credit card | A second invalid payment method was received for a Booking.com reservation. | Important |
| Auto authorization hold failed | An authorization hold (created manually or with an auto-payment) has failed. | Important |
| Payment overdue | A payment that was scheduled to be charged was overdue. | Important |
| Payment received | A new payment was successfully processed and funds have been received. | Update |
| Payment failed | A reservation payment has failed. Use this notification to ensure payments aren't missed. If you receive this notification, retry charging the guest's payment method again or collect a new payment method from the guest. This notification will continue to appear until the reservation is fully paid. |
Important |
| Payment dispute | Important |
Reservation
Notification name |
Description |
Severity |
|---|---|---|
| Request to book | A request to book has been created by a third party source (e.g., booking channel, API). | Important |
| Guest faield screening | A guest for a specific reservation has failed to pass the screening process | Important |
| Upsell Sold | An upsell was purchased | Update |
| Upsell requested | An upsell was requested in the guest app | Important |
| Airbnb alteration declined | The reservation alteration request you sent was declined by the guest or Airbnb. | Update |
| Airbnb alteration approved | The reservation alteration request you sent was approved by the guest. | Update |
| Airbnb alteration received | A guest sent you an alteration request for their reservation. If you receive this notification, approve or decline the guest’s alteration request. | Important |
| Cancellation request declined | A cancellation request made by a third party (e.g., booking channel, API) was declined | Update |
| Double booking | A reservation was received for dates already booked. | Important |
| Reservation inquiry | A reservation inquiry was created by a third-party source (e.g., API, Guesty booking engine). | Important |
| Reservation alteration | A reservation was updated by you or a third party (e.g., booking channel, API). | Important |
| reservation cancelled | A reservation was canceled by you or a third-party source (e.g., booking channel, API). | Update |
| Reservation confirmed | A reservation changed to "confirmed" status by you or a third party (e.g., booking channel, API). | Update |
| Reservation declined | A reservation was declined by you or a third party (e.g., booking channel, API). | Update |
| New guest message | A new message from a guest recieved | Update |
Tasks
Notification name |
Description |
Severity |
|---|---|---|
| New comment on a task | A comment was added to an existing task. | Update |
| New attachment on a task | An attachment was added to an existing task. | Update |
| Guest complaint detected | A guest complaint requiring a follow up task was detected | Alert - AI insight |
Calendar
Notification name |
Description |
Severity |
|---|---|---|
| Calendar is blocked | A calendar block was created | Update |
| Calendar is open | A listing’s calendar is now available for booking | Update |
Channels
Notification name |
Description |
Severity |
|---|---|---|
| Request to book | A request to book has been created by a third party source (e.g., booking channel, API). | Important |
| Guest faield screening | A guest for a specific reservation has failed to pass the screening process | Important |
| Upsell Sold | An upsell was purchased | Update |
| Upsell requested | An upsell was requested in the guest app | Important |
| Airbnb alteration declined | The reservation alteration request you sent was declined by the guest or Airbnb. | Update |
| Airbnb alteration approved | The reservation alteration request you sent was approved by the guest. | Update |
| Airbnb alteration received | A guest sent you an alteration request for their reservation. If you receive this notification, approve or decline the guest’s alteration request. | Important |
| Cancellation request declined | A cancellation request made by a third party (e.g., booking channel, API) was declined | Update |
| Double booking | A reservation was received for dates already booked. | Important |
| Reservation inquiry | A reservation inquiry was created by a third-party source (e.g., API, Guesty booking engine). | Important |
| Reservation alteration | A reservation was updated by you or a third party (e.g., booking channel, API). | Important |
| Reservation cancelled | A reservation was canceled by you or a third-party source (e.g., booking channel, API). | Update |
| Reservation confirmed | A reservation changed to "confirmed" status by you or a third party (e.g., booking channel, API). | Update |
| Reservation declined | A reservation was declined by you or a third party (e.g., booking channel, API). | Update |
| New guest message | You received a new message from a guest. | Update |
| Request to book | A request to book has been created by a third party source (e.g., booking channel, API). | Important |
| Guest faild screening | A guest for a specific reservation has failed to pass the screening process | Important |
| Upsell Sold | An upsell was purchased | Update |
| Upsell requested | An upsell was requested in the guest app | Important |
| Airbnb alteration declined | The reservation alteration request you sent was declined by the guest or Airbnb. | Update |
| Airbnb alteration approved | The reservation alteration request you sent was approved by the guest. | Update |
| Airbnb alteration received | A guest sent you an alteration request for their reservation. If you receive this notification, approve or decline the guest’s alteration request. | Important |
| Cancellation request declined | A cancellation request made by a third party (e.g., booking channel, API) was declined | Update |
| Double booking | A reservation was received for dates already booked. | Important |
| Reservation inquiry | A reservation inquiry was created by a third-party source (e.g., API, Guesty booking engine). | Important |
| Reservation alteration | A reservation was updated by you or a third party (e.g., booking channel, API). | Important |
| Reservation cancelled | A reservation was canceled by you or a third-party source (e.g., booking channel, API). | Update |
| Reservation confirmed | A reservation changed to "confirmed" status by you or a third party (e.g., booking channel, API). | Update |
| Reservation declined | A reservation was declined by you or a third party (e.g., booking channel, API). | Update |
| New guest message | A new message from a guest recieved | Update |