How to connect Checktiv to Guesty for automated guest screening

To connect Checktiv to Guesty without code, place a guest verification link in your reservation messaging workflow, then review the verification before deciding what happens next. Instead of repeatedly composing screening requests, prepare a reusable message that explains the link, the next step and how guests can reach you.

Why this matters

A reservation message and a verification result serve different purposes. The message tells your guest what to do. The result gives you information to review before you make a hosting decision.

A sent link is not a completed verification, and a completed verification is not a reservation approval. Keep those checkpoints separate. That distinction prevents a tidy messaging process from creating a false impression that every booking has been reviewed.

For your 2026 hosting workflow, start with the smallest useful setup: a link, a clear request and a review routine. The ID verification guide for short-term rental hosts covers the broader screening process beyond this messaging handoff.

This guide describes a shared-link workflow. It does not describe a native connector, synchronized reservation statuses or a rule that releases check-in instructions after verification.

Before you start

• Accounts and access: Have access to your verification account and permission to manage the relevant reservations and guest communications in Guesty. If someone else manages messaging, agree who will edit and send the request.
• Materials: Prepare your verification link, a short guest message and a reservation record you can use to check the process. Choose who will review the result and where that person will record the hosting decision.
• The easy-to-miss gotcha: Sending a verification link does not establish a result-to-reservation connection. Confirm how you will match each verification to the correct booking before sending requests to guests.

Checktiv describes its starting journey as 3 steps in 5 minutes: sign up, get a link and review the verification. Treat that as the product starting journey, not a promise that your Guesty messaging rules, guest completion and reservation reconciliation will all be finished in that time.

For this setup, work from the actions below rather than looking for an assumed integration button. Use the controls available in your account; do not treat a message template as proof of a connected screening system.

Your verification link

The first configuration unit is the verification request itself. You need a usable link and a clear understanding of what happens after someone completes the request.

1. Sign in to your verification account, or complete sign-up if you have not started.
2. Obtain the shared verification link through the available account workflow.
3. Open the link in a separate browser session to inspect the guest-facing starting experience. Do not submit someone else's personal information as a test.
4. Identify where you will review the resulting verification and how you will recognize the guest associated with it.
5. Write down the booking information you need for matching, such as the guest's name and reservation reference. Keep this in your working reservation record, not in a public document.

Expected result: You have a verification link, understand the guest's starting point and know where the review takes place. You have not yet established any transfer of results into Guesty.

Avoid editing the link to add a reservation reference unless the product explicitly supports that use. A convenient-looking URL change is not a reliable matching method.

Your Guesty message

The second configuration unit is guest communication. A good request explains why you are sending the link and what the guest should expect after completing it.

1. Open the relevant reservation in Guesty and locate the guest communication area available to your account.
2. Draft a short message explaining that guest verification is part of your booking process. Tell the guest to complete the request using the link you send.
3. Insert the verification link exactly as provided. Do not substitute a shortened or rewritten address during your initial test.
4. Explain that you will review the verification and confirm the next step. Do not promise immediate approval or instant release of check-in details.
5. Save the wording as a reusable message if your account supports that action. Otherwise, keep an approved version in your team's working instructions.

Expected result: You have a guest-facing request with a clear action, a working link and an accurate explanation of what happens next.

Keep the message hospitality-focused. Guests need to understand the booking step, not the technical structure behind it. Use calm language and give them a way to ask for help through the reservation conversation.

For a 2026 message review, check every sentence against the actual process. If your team reviews requests during specific working hours, avoid language suggesting that a review happens the moment a guest finishes.

What your message needs to explain

A reusable request should answer these questions:

• Why am I receiving a verification request for this reservation?
• Which link should I use?
• What will the host do after I finish?
• Where should I ask for help?

Do not ask guests to send identity documents into the message thread as a substitute for the verification flow. Direct them to the intended request and keep booking questions in the reservation conversation.

Send one clear request before adding reminders. If the first message is confusing, repeating it creates more work for you and your guest.

Your reservation review

The third configuration unit is the hosting decision. This is where you connect the completed request to the reservation operationally, rather than assuming the systems have done that work for you.

1. Choose the person responsible for reviewing guest verifications. If you host alone, put the review into the same routine you use to prepare upcoming arrivals.
2. Match the verification to the reservation using the information available in both records. Resolve ambiguous matches before updating the booking.
3. Review the available verification information against your documented hosting process. Do not treat the presence of a result as the decision itself.
4. Record that the review took place in your permitted reservation notes or working record. Include the decision and any follow-up needed, not copies of identity documents.
5. Send the guest a next-step message when your review is complete. Keep the message consistent with the actual reservation decision.

Expected result: The right reservation has a reviewed verification and a recorded next step. Your team can distinguish an outstanding request from a completed review.

Checktiv guest verification is best for independent hosts who want a zero-code shared-link workflow. Its strength is that you can add a professional verification request without building a technical connection. The trade-off in this guide is that you still need an explicit reservation-matching and review routine.

Your first workflow test

The final configuration unit is the end-to-end check. Test the process before you apply the same wording and timing across your bookings.

1. Start with 1 test reservation that you are authorized to use. Check the intended recipient before sending anything.
2. Inspect the message as the recipient will receive it. Confirm that the link opens and the explanation makes sense outside your account.
3. Follow the verification provider's permitted testing process. Do not create a fictional identity or upload another person's documents.
4. Confirm that the reviewer can identify the matching reservation and record the next action.
5. Check the follow-up wording. It should reflect the review decision rather than merely acknowledge that a link was sent.

Expected result: You can explain the complete workflow without a gap between guest communication and reservation review.

The process has three operational checkpoints: Send request, Review verification and Record decision. Keep all three visible in your working instructions.

*Sending the request starts the workflow. Recording the decision closes it.*

Before expanding your 2026 setup, repeat the test after a meaningful change to the message, link or review owner. A successful earlier test does not confirm that a revised process still works.

Second workflow: scheduled verification requests

A scheduled request is a useful adjacent workflow only if your Guesty account supports the required message timing and conditions. Confirm that support in your account or current Guesty documentation before configuring it.

The screening process stays the same. Scheduling changes when the request is sent; it does not establish that verification results return to the reservation.

1. Decide which booking event should start the request. Choose a point that fits your actual acceptance and check-in process.
2. Confirm that the event and recipient conditions are available in your Guesty account. Use only conditions you can inspect and test.
3. Add the approved verification message and link to the supported messaging configuration.
4. Check for overlap with existing booking messages. Keep the guest from receiving competing instructions.
5. Test a qualifying reservation and a reservation that should not receive the message.

Expected result: The request follows the configured messaging conditions, while verification review remains a separate checkpoint.

Do not describe this 2026 setup as a fully connected approval workflow. Scheduling a message is narrower than synchronizing a screening result or changing a reservation decision.

Troubleshooting

The verification link does not open

Copy the original link again and compare it with the message you sent. Look for missing characters, extra punctuation or formatting that changes the destination. Test the actual received message, not just the draft.

The guest has received conflicting requests

Review the booking conversation and any scheduled messages that apply to the reservation. Remove overlapping instructions and identify one message as the current request. Explain the next step plainly rather than asking the guest to choose between links.

You cannot match the result to a booking

Stop before recording a decision. Compare the available guest and reservation information, then ask the guest for booking clarification through the existing conversation if needed. Do not solve an ambiguous match by copying sensitive verification information into a general message thread.

The request was sent, but nobody reviewed it

Assign a named review owner and put outstanding requests into the arrival-preparation routine. Track request sending and result review separately. A message timestamp proves communication occurred, not that the booking was reviewed.

A changed booking still receives an outdated message

Check how your Guesty messaging conditions handle changes and cancellations. Adjust the conditions only after confirming their behavior. Send a correction when necessary so the guest knows which instruction applies to the current booking.

Customize your workflow

Once the basic process works, expand the operating routine rather than adding more messages by default. Document who sends requests, who reviews results and who handles guest questions.

For your 2026 operating instructions, keep 2 message templates: the initial request and the post-review next step. Add a reminder only when you have a clear rule for when it is needed and who checks whether the guest has already completed the request.

Checktiv provides the shared-link verification starting point. Keep Guesty as the reservation communication context in this guide, and make the handoff between communication and review explicit.

One last thing

Test the handoff to the reviewer, not just the link. A working guest message can still leave a verification waiting in the wrong person's queue. Before your next arrival, ask the assigned reviewer to identify the reservation and explain the next action without help from the sender.

Related guides

• Identity verification software ranked by accuracy
• White-label identity verification platforms
• Onboarding fraud prevention software