Property-level automatic ID verification settings

Problem statement

• Hosts cannot automatically trigger Hospitable ID verification for bookings on a per-property basis
• Manual verification requests are required for each booking, creating repetitive administrative work
• This prevents hosts from leveraging Hospitable's delayed messaging feature (which holds messages until verification is complete)

Current workaround

Hosts continue using third-party services like Truvi, which automatically request ID verification for new bookings and send follow-up messages once completed.

Impact

• Unable to consolidate guest verification workflow within Hospitable
• Missing out on Hospitable's delayed messaging capabilities that depend on verification status
• Increased operational complexity by managing verification across multiple platforms
• Additional time spent on manual verification requests or reliance on external tools

Proposed solution

Add a property-level setting that allows hosts to enable automatic ID verification requests for bookings — similar to how Truvi handles automated verification. This would let hosts choose which properties should automatically request Hospitable ID verification when a new booking is received.

Unlock

• Fully consolidate guest verification workflow within Hospitable
• Use delayed messaging to improve guest communication based on verification status
• Reduce the number of tools needed to manage properties
• Eliminate manual verification request workload
• Streamline operations with a unified platform for verification and messaging