OwnerRez Guest Screening: 11 Integrations

Leave OwnerRez on its defaults and a door code exists before any screen has run, as the door lock help article spells out:

By default, it is set to "at booking time" which means the code is assigned and sent to the lock as soon as the booking occurs, even if the booking is 6 months in the future.

In September 2026 a host on the OwnerRez forum asked which OwnerRez guest screening tool to pick: Trustd.ai, Authenticate or Truvi. They wanted "just a little peace of mind with direct bookings where I don't have airbnb providing any vetting." By October 18, nobody had replied.

OwnerRez checks no guest IDs itself. None of the 11 integrations it lists for screening mentions canceling a booking or stopping OwnerRez from creating the door code. So a screen decides only whether the guest receives that code, through a vendor portal that keeps access details hidden or through a Trigger that waits for a pass tag.

Either gate fails the moment any other message sends the code without waiting. Before you compare a single vendor, find every message that does.

Can a failed screen stop the door code in OwnerRez?

A failed screen can't stop the door code itself, because OwnerRez's door code settings never read a screening result. What it can stop is the arrival message, through a Trigger, OwnerRez's rule for sending a message template once its conditions are met, set to wait for a pass tag on the booking or guest record.

Say a direct booking lands on your OwnerRez site late on a weeknight, for a weekend months away. By default, the lock already has its code. Your screen starts only now, because every OwnerRez article that names a start point begins screening once the booking exists. If your confirmation template carries {BDOORCODE}, that guest already has the code, and nothing the screen finds later takes it back.

Now move {BDOORCODE} out of the confirmation and into an arrival message that waits for a pass tag. With a tag integration, that weeknight guest's code sits unsent until the tag appears, and a guest who fails or never finishes gets no arrival message, and so no code. A portal vendor such as ChargeAutomation can hide access details in its own portal instead. That works only if no OwnerRez template sent the code first.

The arrival message has to wait on a tag because of one line in OwnerRez's triggers article: "The Condition > Applicability section only has three choices: Source, Property, and Tag." The status conditions and the Tag Automation conditions OwnerRez lists leave custom fields out too. So when a vendor's result lands only in a custom field, as SafeGuest's Red rating does, the one way in that OwnerRez spells out is a tag someone adds manually.

In November 2020 an OwnerRez alum gave a host that workaround, a tag "that you manually add to a booking once the guest has done whatever it is that you want them to do, and then set having that tag as a criteria on the trigger." It is still the method for SafeGuest, and for ChargeAutomation if you gate on a Trigger rather than its portal: read each result, then tag the booking that passed.

The door code settings offer three Generate When choices: at booking, a set number of days before arrival, or manual entry. A pending booking gets no code, since "Code generation will not occur until pending bookings are confirmed". That would make pending status the natural gate, but no vendor mentions setting a booking back to pending.

Channel bookings add a timing problem, because an Instant Book guest is confirmed before any check runs. OwnerRez's Zapier article says about 6 in 10 channel bookings first arrive as a pending block, titled "Hold for" on Airbnb, that usually becomes the booking within minutes. Ask your vendor whether its screen starts on the hold or on the confirmed booking.

Which OwnerRez integrations can hold back access?

Five of OwnerRez's 11 screening integrations say their own portal or app can hold back access: ChargeAutomation, Chekin, Enso Connect, Linkbase and SuiteOp. Three show pass tags a Trigger can wait on: Authenticate, Guest Ranger and Trustd.ai (for a first-time guest). SafeGuest, Safely and Truvi claim neither gate, so with those three you build the hold yourself.

Authenticate publishes this page and is one of the 11. Every vendor fact here comes from that vendor's own pages, or OwnerRez's article or announcement for it, as read in October 2026. Prices are what each vendor's page showed on October 19, 2026, and where a page shows none, the table gives OwnerRez's dated announcement or says the price is quoted. Where sources disagree, the entry names its source. A gap means those pages are silent, and nothing was tested on a live account. Rows run alphabetically inside each group, so order ranks nothing.

Seven other OwnerRez listings stay out, mostly because they do something else: Check-in Scan registers guests, InsuraGuest sells insurance, Hello Guest Screen and WelcomeScreen are smart-TV welcome screens, and Alertify and PetScreening cover noise and pets. Happy Guest's pages contradict themselves on identity checks.

The same comparison exists for Guesty guest screening integrations and Hostaway guest screening platforms.

How do you set up guest screening in OwnerRez?

For OwnerRez guest screening with Authenticate, Guest Ranger or Trustd.ai (for a first-time guest), the gate is one arrival message carrying the door code and waiting for the pass tag. The rest keeps the code from arriving early: strip it from every other template, send the link if the vendor doesn't, and keep a plain, Source-limited one for unscreened channels.

In July 2023 a host asked for door-code generation to wait for a deposit and a signed agreement. The same OwnerRez alum replied that "what matters is if or when they are sent to the guest". OwnerRez also warns that "you won't be able to use Tags as a Condition unless you already have some tags set up", so start with a test booking.

1. Strip the code from every other template first: one confirmation email with the code in it undoes everything else, so do this before you pick a vendor. Any confirmation, agreement reminder or channel template carrying {BDOORCODE}, {BDOORCODETABLE} or {BDOORCODELIST} without the tag condition sends the code no matter what the screen says. You end up with two arrival messages: the gated one in step 3 for the channels you screen, and a plain one limited by Source to the channels you don't, so those guests still get their code. While you build, let the plain one carry the code for every guest, and add its Source limit once the gated one is live.
2. Send the link with a scheduled, retrying Trigger: for Authenticate, use the scheduled event "Minutes After > Booking is created", which appears in OwnerRez's SafeGuest article. Because Authenticate's link takes minutes to appear, add a Tag condition for verificationLinkReady, a Source condition for the channels you screen (say, your website and Vrbo), and the Retry "For a number of days". For Trustd.ai, send its Guest Form link, {CXGUESTFORM}, with the same Source condition and the Guest Form selected in the Trigger's Action, since screening runs once the guest completes that form. That link has no ready tag to wait on, so check on a test booking that it is filled in by the Trigger's scheduled time. Guest Ranger texts its own link, so skip this step for it.
3. Hold the arrival message on the pass tag: put {BDOORCODE} only in a Guest Arrival template sent by a Scheduled Trigger, with a Tag condition for identityProofValid (Authenticate) or Identity Verified (Guest Ranger). For Trustd.ai, add TRUSTD SCREENING: CLEAR as one Tag condition and, if you have its ID check enabled, TRUSTD ID VERIFICATION: PASS as a second, because every condition must match while one condition listing both tags would send on either. Pick the tags from your tag list. Add the same Source condition, "Pending Status is > No", and the Retry "Every day until arrival".
4. Catch repeat Trustd.ai guests yourself: Trustd.ai's tags sit on the guest record, and OwnerRez reads booking, property and guest tags as one list, so a returning guest's old pass satisfies step 3 at its scheduled time. Add a Trigger addressed to you with the condition "Guest Type is > Repeat Guest", then Skip that booking's arrival message and Send Now once the new report, linked in the "Link to the Report" custom field, shows a pass. The tag can't tell you, because a repeat CLEAR looks like the old one. A repeat guest who books inside the arrival message's window can also get it before you Skip.
5. Don't gate on a missing fail tag: a "Tag is > None Of" rule on identityProofInvalid (Authenticate) or Identity Not Verified (Guest Ranger) would also send the code to a guest who never opened the link, since that guest carries no fail tag. To hold the code for a criminal record too, add Authenticate's criminalRecordClear as a second Tag condition, but only if your Authenticate workflow runs the criminal check on every screened guest; otherwise the code waits for your arrival-day check.
6. Send each fail to yourself: add a Scheduled Trigger with a Retry, addressed to you, for identityProofInvalid, US_authDBCheckFailed and criminalRecordFound (Authenticate) or Identity Not Verified (Guest Ranger), so you can act in time. Trustd.ai shows no fail value, so its fails surface only in its report or at your arrival-day check.
7. If you narrow Generate When, wait for the code: with "A number of days before arrival" or manual generation, add "Door Code Status is > One Of" Code Generated Successfully, because OwnerRez links late generation to blank door code fields reaching guests.

Retries and arrival day

Without a Retry, a scheduled OwnerRez Trigger checks its conditions once, when the pass tag may not exist yet, and never sends. Retry is off by default and offered only on Scheduled Time triggers. "Every day until arrival" keeps checking and still sends once. Adding a Retry to an existing rule can catch past bookings, so OwnerRez suggests the condition "Arrival Date > On or After" the date you added it.

OwnerRez's own articles disagree on when those retries stop. The common-issues article says "until the day after arrival", while the triggers article stops a Saturday-arrival example at 11:00 PM on Friday. So on arrival day, open each screened booking and check its tags. If the pass tag is there but the arrival message hasn't gone, Skip that message, then Send Now. The Skip matters because OwnerRez sends a template again once its conditions match, even after you've sent it yourself.

An Authenticate or Guest Ranger guest with no pass or fail tag never finished (Guest Ranger's stays at "Identity Pending", Authenticate's at verificationLinkReady). A Trustd.ai fail leaves no tag either, so open its report before you decide. Before you act on a criminal or watchlist record, confirm it belongs to your guest, and decide in advance what each fail result means for the stay.

Vrbo and direct bookings, where you take the payment, need one more guard against last-minute pending bookings. For them, OwnerRez's triggers FAQ pairs "Pending Status is > No" with "Payment Status is > One of > Paid in Full", and that condition can sit beside the tag.

Two ways the code leaves without the gate

Airbnb's "Seamless Entry" can pass door codes to Airbnb outside your OwnerRez gate. Since OwnerRez's August 26, 2026 release, ticking "Show Door Code on Airbnb" lets Airbnb share two backup codes with a guest whose original code fails. Once the box is saved, OwnerRez "is sending door codes to Airbnb" with no Trigger in between. Its guest instructions article doesn't say whether the booking's own code goes too. On any listing where you screen Airbnb bookings under a disclosed requirement, leave the box unticked.

A lock integration that messages guests itself sits outside the gate too. An OwnerRez team member gave a RemoteLock user this advice in July 2023: "Do not set up remote lock to send the code to guests. Instead set up a template & trigger on OwnerRez, using whatever criteria you need, to allow it to be sent." Turn off any code notice your lock vendor sends guests directly.

Which booking channels can you screen in OwnerRez?

Direct, Vrbo and Booking.com bookings can all carry a screening link from OwnerRez. Airbnb bookings can't, unless a legal or compliance requirement applies and the listing discloses it. Vrbo requires no identity verification of its own, Booking.com messages reach guests through an alias, and direct bookings arrive with no channel vetting at all.

Airbnb's Off-Platform and Fee Transparency Policy prohibits "Asking guests for contact information after a booking in order to run credit checks or background checks". The exception reads: "You may require additional contact/identity information if it is required for legal or compliance reasons and can be verified by a host upon request by Airbnb (such as local laws, HOA rules, building security rules)." If you rely on it, your listing must explain what is required and why.

Airbnb's policy also bears on the five portal and app gates. It prohibits "Asking guests to create a separate account or register on another website besides Airbnb.com for purposes of gaining entry to a listing". It also prohibits "Asking guests to install a third-party app to access a listing; all listings on Airbnb must be accessible to a guest without requiring they have another app or account". Keyless entry and in-stay apps are exempt as long as they are optional. So are registrations or apps that a disclosed legal or compliance reason requires.

Unless your listing discloses such a requirement, keep the link off Airbnb bookings on purpose. Your Source conditions won't do that alone, because they limit only your own Triggers. Authenticate's Manage Booking Channels starts with every channel selected, so Airbnb bookings get its link until you untick that channel. OwnerRez's Truvi setup has a box to "Exclude AirBnB bookings", SafeGuest can exclude a channel, and ChargeAutomation, Enso Connect, Linkbase and SuiteOp set their requirements by booking source.

Three vendors reach guests outside your Triggers altogether. Guest Ranger texts each booking it can reach, Chekin's integration doesn't pass its check-in link back to OwnerRez, and Safely emails guests itself from Concierge@Safely.com. None of the three names a channel setting, so ask each how it leaves Airbnb bookings out before you connect it.

Airbnb's own checks, covered in Airbnb guest screening, run before a booking reaches OwnerRez. Vrbo's identity verification page describes an optional check of name, email, phone, address and date of birth with no photo ID. That is why a requirement in your house rules carries weight there.

Booking.com's problem is delivery. A texted link may never arrive, because Booking.com no longer shares phone numbers with connectivity providers. A link in a template has its own hazard, since your property's link-blocking setting can stop it. No Booking.com partner article found either permits or prohibits third-party ID checks.

Direct bookings, the forum host's worry, have no channel check upstream. Two OwnerRez settings let you screen them before they confirm. In "inquiry only" mode a guest books only after you reply with a quote, which OwnerRez says lets you "ensure they're qualified first". A booking taken without charging the card stays pending, which OwnerRez also presents as a way to vet the guest. No integration article says whether its link goes out for a pending booking, so check that on your test booking.

What to tell guests before the link arrives

Name the screening vendor in your listing on the channels you screen, because the request comes from a company guests may not know. Most of the 11 want a photo ID and a selfie. Trustd.ai also asks for a date of birth, Truvi's criminal add-on for a US address and consent, and SuiteOp's Authenticate route for "the last four digits of their Social Security Number". With Truvi the listing note is a requirement, since its terms say hosts must "prominently display the details of the ID Verification Service to Guests".

Tell guests about the selfie as well. Under OwnerRez's September 2025 Authenticate announcement, one host wrote "Big NO! to facial recognition." while another favored it "in an effort to prevent chargebacks".

Screening guests from outside the US

Most of the 11 still run an identity check on a guest from abroad, but Authenticate's OwnerRez integration and Truvi won't run a criminal one. Authenticate's OwnerRez criminal field carries "us_only" in its name, and Truvi runs its criminal check only for guests with a US address. Passports travel better. Truvi accepts any government ID with a full name, photo, date of birth and issuer, and Chekin reads a passport's machine-readable strip. For watchlists, Authenticate searches the EU Consolidated list, HM Treasury Sanctions and the UN Consolidated list, and Safely names Europol and Interpol. Authenticate's guide to verifying international guests goes further.

What each integration keeps after a check

Some hosts would rather not hold guests' IDs at all, which rules out OwnerRez's own ID upload, a booking custom field set to File. In October 2019 one host wrote that they would rather a trusted third party "verify the ID and just tell me pass/fail anyway than have to worry about handling guests' PII myself." Five vendors' pages address the images:

ChargeAutomation, Enso Connect, Linkbase, Safely, SuiteOp and Trustd.ai say nothing about how long ID images are kept, so get that answer in writing before you connect one.

Which OwnerRez guest screening integration fits your bookings?

Decide first who holds the gate: you, with a Trigger on a pass tag, or the vendor, in its portal or app. Damage cover, price and portfolio size then pick the OwnerRez guest screening integration. With mixed bookings you'll mostly screen direct and Vrbo guests, since Airbnb allows post-booking ID requests only for disclosed legal or compliance reasons.

If you're happy building Triggers, the three tag integrations keep the whole gate inside OwnerRez, limited by Source to the channels you screen, although Guest Ranger texts its link outside Source. Authenticate reports a US criminal result and separate fail tags, so a fail can reach you by Trigger, but every attempt costs you, pass or fail. Trustd.ai's support article lists criminal background checks, yet it shows no fail value, and a repeat guest needs the extra step in the setup. Guest Ranger names no criminal records check. It does flag bookings under your age minimum.

If you'd rather the vendor held the door, ChargeAutomation, Chekin, Enso Connect, Linkbase and SuiteOp keep access details in their own portal or app. On Airbnb, a gate that needs another app or account fits only the disclosed exceptions.

If most of your bookings come through Airbnb, Airbnb's own verification is the check they get. Truvi's base screening also runs on Airbnb bookings with "no guest interaction required". Its cheapest published plan is a different one that needs a guest journey. If you must register guests with the authorities in Spain, Italy, Greece or Portugal, Chekin's check-in flow is built around it. ChargeAutomation also files with authorities in 15+ countries, and Enso Connect lists Chekin among the partners behind its Authority Reporting.

On a small portfolio, the minimums weigh most. SuiteOp's plans start at a $3,000-a-year minimum, and OwnerRez's July 2024 announcement put Guest Ranger at a $250 monthly minimum, while pointing hosts under 10 properties to a Lite plan. Authenticate charges by the check after a $100 activation deposit credited toward usage, Safely prices screening per screening or per night with its policy, and SafeGuest's screening is free. Chekin's monthly plan needs three units, although its annual plan prices one or two properties.

For damage, Safely's cover is "primary insurance", available to OwnerRez clients with 10 or more properties, while smaller hosts can request a quote directly. Truvi's protection is not insurance by its own account, nor is SafeGuest's Protect, and Guest Ranger sells Protect separately. The five portal and app vendors work through guest deposits, waivers, their own protection or partners. Authenticate offers no damage cover and Trustd.ai names none, so with either you'd look elsewhere, such as OwnerRez's own Damage Protection, resold through RentalGuardian and priced per coverage tier. Once turned on, it must cover every booking, and it excludes intentional damage.

What each OwnerRez guest screening integration does

ChargeAutomation

Deposit, e-signed agreement and ID check all sit in ChargeAutomation's one guest portal, and ChargeAutomation sends the portal's pre-check-in link itself, by email, SMS, WhatsApp or QR code. The portal shows the door code once check-in, payment or ID approval is complete, or at a set time before arrival, so tie it to ID approval. In OwnerRez the only screening trace is a custom field, caPreCheckinComplete, set to "Completed" and pushed "to trigger an automation" that ChargeAutomation doesn't name.

Chekin

Chekin files a guest's details with the authorities in Spain, Italy, Greece or Portugal through the same flow that checks their ID. Guests scan the ID on a phone without an app, and you can override a flagged result or re-run the check. Nothing comes back to OwnerRez, so any hold lives in Chekin's app. Bookings reach Chekin every 3 hours, which can delay the check on a same-day booking.

Enso Connect

In Enso Connect, "Guests flagged for review don't receive check-in instructions until you approve them", and its guest app can keep smart lock codes hidden too. Enso mentions booking tags pushed into OwnerRez without naming one, so ask what it writes before you build a Trigger on it. Of the paid Screen, Verify and Safeguard tiers, only Screen names a source: Autohost's risk models, from a screening company with no OwnerRez listing of its own.

Linkbase

Linkbase sizes screening to the stay, with waiver-level screening for short stays and a fuller tier for longer ones, and it names Truvi for background screening and Autohost for ID checks. What you see is "a clear approved, flagged or rejected signal, not raw data". That signal stays in Linkbase, because nothing on either side says a screening result comes back to OwnerRez. It reaches OwnerRez through Calry, an aggregator, and writes the guest app link into each reservation.

SuiteOp

Connecting SuiteOp to OwnerRez takes a premium feature first, the WordPress Plugin + Integrated Websites. SuiteOp's help article says it "may require a fee", and OwnerRez's Costs & Fees article lists it at $10 a month for the first property as of October 2026. SuiteVerify then runs "AI-powered ID checks, document scanning, and biometric matching on every OwnerRez guest before access codes are issued". Criminal and global watchlist checks run through your own Authenticate account. Its verification page says it is built for portfolios of five units or more, while its OwnerRez page scales down to single-property owner-operators.

Authenticate

Authenticate, which publishes this page, has no guest portal, so the gate is a Trigger you build on its tags. Its OwnerRez messaging guide lists a link-ready tag and six result tags that report identity, a US database check and criminal records separately. OwnerRez's own Authenticate article shows six custom fields and no tags, so let your test booking show you which arrive. The watchlist result comes only as a Yes/No custom field. On forged documents, its homepage promises "Instant forensic analysis" of government IDs, and its privacy policy says it "may automatically fail your identity verification" on "anomalies or suspicious activity".

The OwnerRez criminal field, us_only_seven_year_criminal_record_found, carries the result of a seven-year national database search, and a national search is a first pass that a county courthouse search confirms. Authenticate's pricing lists a US Criminal Database Search, free once a paid ID, knowledge-based or SSN check has verified the same person, and a 7 Year Criminal Activity Verification at $5. No Authenticate page says which of the two fills the OwnerRez field. The face match and database search come free on the same terms, the activation deposit is credited toward usage but non-refundable, and bookings made before you connect are not synced.

Guest Ranger

Guest Ranger texts its own verification link at booking, so a direct guest who gives you a number needs no link Trigger from you. Credit card and other checks are optional. Its verification page says Guest Ranger verifies the ID and matches it to the person booking, yet the section headed "Fake ID Check" describes a "property-management-side user review database". Its FAQ tells uneasy guests "there may be alternate means to complete ID verification", so decide what yours are before a guest asks.

Trustd.ai

The Trustd Score is Trustd.ai's read of a guest's booking-related digital footprint across platforms. Its pre-filled Guest Form link can be created as early as the inquiry or quote stage. OwnerRez's 2024 announcement said "No ID or selfie is collected from the Guests", while its current article, which says the result is "registered in the TAG field," lists ID verification "(if enabled)" and selfie authentication.

SafeGuest

Check first that SafeGuest's OwnerRez integration is live for your account, because an October 9, 2026 SafeGuest blog still lists OwnerRez as "coming soon" while the homepage lists it as live. Once connected, it rates every booking it screens Green, Yellow or Red, and in its own words, "We don't block bookings". The rating lands in three custom fields, "Verification Link", "Risk Level Safe" and "Risk Level". OwnerRez's email template tells guests their host "verifies every guest before sharing check-in details", although neither OwnerRez page says those details are held back. Protect, the optional add-on, is one flat fee however long the stay.

Safely

Each booking gets its own Safely policy. OwnerRez says guest screening comes with every policy, while Safely's own page prices it at $0.50 per night with the policy. OwnerRez also explains passing the Safely Trust & Safety Fee to guests as a surcharge, categorized on Airbnb as a Resort, Management or Community/Property Association fee. OwnerRez mentions nothing written back to the booking, which leaves a Trigger nothing to wait on. If you turn a guest away on Safely's findings, Safely handles the notice: "we follow the Fair Credit Reporting Act (FCRA) to inform them."

Truvi (formerly Superhog)

Truvi's base screening runs with "no guest interaction required" on every booking, checking its own watchlist of problem guests plus email and phone. Add-ons cover ID, a US sex offender check and a US criminal search of the lead guest across "2400+ national and federal criminal databases". The criminal fee isn't charged for a non-US guest it can't check. Its help center says the ID add-on "does not include a check for the validity of the ID itself", while the pricing page promises to "Confirm IDs are genuine with a biometric check".

In OwnerRez, TruviScreeningComplete indicates "whether all required screening steps are completed", and TruviProtected "whether protection is active for the booking". Neither carries the Approved, Flagged or Rejected status on Truvi's screening page, and Truvi says a flagged criminal result "will not affect your protection". So a guest who finished every step and was flagged may carry the same tags as an approved one, leaving a Trigger waiting on completion while the verdict stays in Truvi. On the protection itself, Truvi's line is "We are not insurance – but we are insurance-backed".

Frequently asked questions

Does OwnerRez do ID verification or background checks itself?

OwnerRez does not verify IDs or run background checks itself. A booking custom field set to File adds an upload box at checkout or agreement signing, capped at 8 MB, but an OwnerRez team member wrote in October 2024 that "OwnerRez itself can't do anything with that ID." Checking an ID takes a listed integration, although for direct bookings paid through Lynnbrook Group, OwnerRez also supports that processor's Guest ID, which it describes as "two-factor authentication".

How much does guest screening cost in OwnerRez?

Guest screening in OwnerRez costs the vendor's price, usually host-paid; SuiteOp also needs a $10-a-month OwnerRez premium feature for the first property. As of October 19, 2026, vendors' pages list SafeGuest's screening at $0 per booking, Authenticate's Government ID Verification at $2 from a $100 activation deposit, Safely from $5 per screening and Truvi at $12.60 to $28.75 USD per booking, the lowest with a guest journey. Enso Connect and Linkbase quote; Guest Ranger and Trustd.ai list none.

Does a failed screen cancel an OwnerRez booking?

A failed screen leaves an OwnerRez booking in place, and none of the 11 integrations describes canceling one for you. SafeGuest's own summary is "It informs the call. You still make it." For Airbnb bookings, OwnerRez's August 19, 2026 release added in-app cancellation with reasons such as "Unauthorized party", so the decision stays yours but the step takes less time.

Can OwnerRez hosts ask Airbnb guests for ID?

OwnerRez hosts can ask Airbnb guests for ID only when a legal or compliance reason requires it, such as local laws, HOA rules or building security rules, and the listing explains what is needed and why. Airbnb's policy bars asking guests for contact information after booking to run background checks, so those bookings get Airbnb's own guest identity verification, plus any screen that asks nothing of the guest, such as Truvi's base screening.

Does OwnerRez integrate with Autohost or Superhog?

OwnerRez integrates with Superhog under its current name, Truvi, having announced the SUPERHOG integration in October 2021. Autohost had no listing in OwnerRez's integrations directory as of October 18, 2026, but two listed integrations reach it: Linkbase names Autohost for ID checks, and Enso Connect's Screen tier evaluates bookings against Autohost's risk models.

What to tell the forum host

This comparison found no independent study showing vacation rental guest screening reduces damage or parties, and OwnerRez never says outright whether a Trigger can read a custom field or which codes "Seamless Entry" sends. Two of the forum host's three picks show a pass tag that can hold a direct booking's code: Authenticate, whose tags OwnerRez's article doesn't list, and Trustd.ai for a first-time guest. Guest Ranger, which the host didn't name, shows one too. Truvi's tags may not carry its verdict. Whichever you choose, a screen keeps the code from a guest only when every message carrying it waits.

Related resources

• Top guest screening platforms for short-term rentals
• Does Airbnb run background checks on guests?
• What an Airbnb chargeback costs a host
• National vs county and federal criminal background check levels