A team rule can match the end of an email address instead of the whole of it, so one rule covers a domain and every subdomain beneath it. That is how you keep an OTA's messages out of a team that collects all your email, without writing a separate rule for every address it sends from.
This applies to the Sender Email Address rule on a team. If you have not built a team before, start with Teams in Unified Inbox, which covers creating a team, the eleven rule types, and the order that decides which team wins.
The four match options
Choose the rule type Sender Email Address and the second control offers four ways to match.
Is. The address is exactly what you type.
Is not. Everything except that address.
Ends with. The address ends with what you type.
Does not end with. Everything whose address does not end with what you type.
Why one rule covers every subdomain
Because the match runs on the end of the address, a single value covers a domain and everything beneath it. A rule reading Sender Email Address ends with booking.com picks up guest.booking.com, mchat.booking.com and property.booking.com, with no separate rule for each.
Keep the value as specific as the domain you mean. A short value matches far more than you intend.
How to set this up
Booking.com is the case most properties meet first. Booking.com guest messages reach you as email notifications, so a team filtering on the Email channel collects them alongside ordinary email. There are two ways to separate them, and you only need one.
Give them their own team.
Go to Inbox Settings > Teams and click New Team.
Name the team, for example Booking.com.
Under What to show in the team? choose Select rule.
Add a rule, set the type to Sender Email Address, set the match to Ends with, and enter
booking.com.Save, then drag the team above your general email team in the overview. The list is read from the top down and the first match wins, so it has to sit higher to claim those conversations.
Or exclude them from the team you already have.
Open your general email team and choose Edit.
Add a rule of type Sender Email Address, set the match to Does not end with, and enter
booking.com.Put it in the same inner group as your existing channel rule and set that group to AND, so both conditions have to hold.
Save.
The same pattern works for any partner or OTA that sends from more than one subdomain.
What this does not do
It does not apply to other rules. Only Sender Email Address matches on part of an address. Every other rule that takes an address matches the whole address.
It does not re-sort what is already in your Inbox. Rules are applied as conversations arrive, so anything routed under your previous rules stays where it is until you move it by hand.
It does not override list order. A team still only receives a conversation if no team above it matched first.
It does not change how a message is parsed. Routing decides which team a Booking.com notification reaches, not how it is displayed once it arrives.
Common questions
We already have the Booking.com parser. Do we still need this?
Yes, if Booking.com messages are landing in a team you did not intend. The parser turns a Booking.com notification into a readable guest message. It does not decide which team picks that message up. See What is the Booking.com email parser?.
Can I use Ends with on the Recipient Email Address rule?
No. The match options are on Sender Email Address only.
Will this move the Booking.com conversations already sitting in my email team?
No. Reassign those by hand from the ticket details panel.
A message matches both my Booking.com team and my general email team. Which gets it?
Whichever sits higher in the Teams overview.
Getting help
Open Talk to Us in the left menu of the platform, or email support@bookboost.io.