If you are receiving email or in-app notifications for conversations that don't belong to your property, this article will help you understand why it's happening and how to fix it. This is a common question in multi-property accounts and is related to how team membership and notification settings work together in Bookboost.
Main Concept: Teams and Notifications Are Linked
In Bookboost, notifications are triggered based on two factors working together: your personal notification settings and the teams you belong to.
When you enable a notification such as "Conversation Assigned to Team" (see Inbox Settings for full details on notification types), you will be notified every time a conversation is assigned to any team you are a member of — not just your property's team.
This means that if you are part of a shared or catch-all team that receives conversations from multiple properties or unrouted guest messages, you will receive notifications for those conversations too, even if they are not relevant to your hotel. This is expected system behaviour, not a bug. 💡
Use Cases
You belong to a multi-property account and are receiving notifications for conversations from other hotels or properties.
You have "Conversation Assigned to Team" notifications enabled and are part of a shared team alongside operators from different properties.
Conversations already assigned to another property team still trigger notifications because you share a common team with those operators.
Configuration and Setup
Step 1 — Identify which teams you belong to 🔍
Log in to the Bookboost platform.
Go to Inbox → Inbox Settings → Teams.
Review the list of teams and check which ones include your operator profile.
Step 2 — Remove yourself from teams that are not relevant to your property
Open the team you want to leave.
Find your operator in the member list.
If you are an admin remove yourself (if not ask an admin to do so, as this requires admin access).
Save the changes.
⚠️ Important: Before removing yourself from a team, make sure you understand its purpose. If the team is a shared fallback for unrouted guest conversations, leaving it means you will no longer see or be notified about conversations that land there — even if one of your own guests is occasionally routed there. Discuss this with your account admin before making changes.
Step 3 — Review your notification settings
If you'd prefer to stay in all your current teams but reduce notification noise, you can also adjust which notification types are active for you. See the Inbox Settings article for a full guide on customising your notification preferences.
Conclusion
Receiving notifications for conversations from other properties is almost always caused by being a member of a shared team with that notification type enabled. The solution is straightforward: review your team memberships and remove yourself from any teams that are not relevant to your property. For more control over what you're notified about, visit the Inbox Settings article. ✅
Support
Please contact us through the 'Talk to Us' option on the left menu in the platform, or through the Bookboost Support email at support@bookboost.io if you have questions or need additional support.