Mews currently allows automatic or manual clearance of inactive guest profiles. However, if a blocklisted guest becomes “inactive,” their profile can be cleared as well. Because the blocklist flag is tied to the profile’s email, deleting the profile can remove the blocklist — allowing the guest to book again.

Problem

Hotels risk losing important safety and security protections if blocklisted guests are cleared along with inactive profiles.

Requested Enhancement

Please introduce a safeguard that ensures blocklisted guests remain blocked even when old or inactive profiles are cleared. This could be achieved by:

• Automatically skipping blocked profiles during clearance, or
• Preserving the blocklist flag in a separate “Blocked Identity” record so the guest remains blocked even if their profile is removed.

Why This Matters
* Hotels rely on blocklists for safety, fraud prevention, and staff protection.
* Inadvertently deleting a blocked profile currently removes the hotel’s protection.
* This enhancement would allow data cleanup without compromising security.

Expected Outcome

Hotels can confidently use inactive profile clearance without ever losing blocklist enforcement.