> For the complete documentation index, see [llms.txt](https://help.guestreply.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.guestreply.ai/readme/user-manual/upselling/early-check-in.md).

# Early Check-in

The **Early Check-in** feature lets you offer guests access to your property before the standard check-in time for an additional fee. 

When a guest requests early check-in, GuestReply AI automatically checks availability, informs the guest about the fee, and generates a secure payment link through your connected Stripe account.

> &#x20;<mark style="color:$primary;">**⚠️ Stripe Required:**</mark> Early Check-in is available only when a Stripe account is connected.\
> All payments are processed directly through your Stripe account and are not handled by GuestReply.

## How to Configure Your Early Check-in Settings

Before enabling the Early Check-in feature, read and [follow the instructions to link your Stripe account](/readme/user-manual/settings/stripe.md).

#### 1. Select Your Listings

Choose which listings will offer the Early Check-in feature.

* **`Disable for all listings`**: Automatically disables early check in feature for all listings;
* **`Enable for all listings`:** Automatically activates the feature for every listing connected to GuestReply;
* **`Enable for selected listings only`**: Allows you to pick specific listings - ideal if only certain units have the cleaning capacity for early arrivals.

<figure><img src="/files/jdaNR3Ykxxy3wEBxbBYQ" alt=""><figcaption></figcaption></figure>

#### 2. Set Check-in Time & Fee

Define the window of availability and the cost for the guest.

* **`Early check-in allowed from`**: Select the earliest possible time a guest can enter the property (e.g., 11:00 AM). This time is based on the property’s local timezone.&#x20;
* **`Early check-in fee:`** Enter fee for this service. Ensure this amount aligns with the currency set in your connected Stripe account.

<figure><img src="/files/h0wx7qiNx1khKpcPPEqv" alt=""><figcaption></figcaption></figure>

#### 3. Configure Advanced Settings

These settings control **when** the AI can confirm early check-in requests and **how** it validates availability.

<figure><img src="/files/ul28zFvjl0MhZ9yF72lM" alt=""><figcaption></figcaption></figure>

#### Earliest Day to Allow Requests

This determines how far in advance the AI can confirm an early check-in request. Choose how many days before arrival the AI can confirm a request:

**`Only on check-in day` -** The AI can only confirm early check-in on the actual day of arrival. For requests made earlier, the AI will ask the guest to check back on their arrival day.

**`1 - 14 days` -** The AI can confirm requests within the specified window. For example, if set to "3 days," the AI will confirm requests for bookings starting within the next 3 days.

**`Any` -** The AI can confirm early check-in requests at any time.

> *<mark style="color:$primary;">**Example**</mark>*<mark style="color:$primary;">**:**</mark> *<mark style="color:$primary;">If set to 3 days, GuestReply AI will only confirm an early check-in if the booking starts within the next 3 days.</mark>*

#### **Availability Check Method**

This determines how the AI verifies that early check-in is possible.

**Option A: Checkout Conflict Check (Recommended)**

‼️ *The system confirms Early Check-in only if there is no checkout on the same day*.

If another guest is checking out that day, the AI will not auto-confirm Early Check-in.

***Best fo*****r**: Most listings which provide safe, automatic handling.&#x20;

**Option B: Always Allow**

The system confirms Early Check-in regardless of other bookings.

Even if another guest is checking out on the same day, the AI may confirm Early Check-in immediately.

***Best for***: Listings with guaranteed fast cleaning turnaround or dedicated same-day buffer time.

> <mark style="color:$primary;">‼️</mark> <mark style="color:$primary;"></mark><mark style="color:$primary;">**Use**</mark><mark style="color:$primary;">**&#x20;**</mark><mark style="color:$primary;">**`Always Allow with caution`**</mark><mark style="color:$primary;">**.**</mark> <mark style="color:$primary;"></mark><mark style="color:$primary;">If another guest is checking out, you must ensure the property will be cleaned and ready in time. The system will not prevent double-booking conflicts with this setting.</mark>

## How the AI Responds to Guests

The AI tailors its response based on your settings and the booking situation. Below are real examples showing how different configurations produce different guest experiences.

<details>

<summary><mark style="color:$primary;"><strong>Scenario 1: Immediate Confirmation Available</strong></mark></summary>

## **No previous guest - AI confirms instantly and sends payment link**

*Your setting: Checkout Conflict Check*

A guest asks for early check-in, and the apartment was not occupied the night before. So there's no cleaning conflict. The AI sees that the property is available, immediately offers the early check-in, and when the guest agrees, sends a secure payment link automatically.

**AI Response:**

> Dear Andre,
>
> Thank you for your message. We can arrange an early check-in for you from 10:00 for a fee of 20.00 USD
>
> Please use the following link to complete the payment for the early check-in: \[payment link]. Once the payment is complete, your early check-in from 10:00 will be confirmed.

No manual work needed — the AI handles the entire process from offer to payment.

</details>

<details>

<summary><mark style="color:$primary;"><strong>Scenario 2: Checkout Conflict</strong></mark></summary>

## Another guest is checking out — AI doesn't confirm early check-in

***Your setting: Checkout Conflict Check***

A guest messages asking to check in early. However, your previous guest is checking out on the same day. The AI recognizes this conflict automatically and lets the guest know politely:

**AI Response:**

> Dear Andre,
>
> Thank you for your message. **Unfortunately, we are unable to confirm an early check-in at this time, as we need to prepare the apartment after the previous guests.**&#x20;
>
> We will be happy to welcome you at our standard check-in time of 10:00. If the apartment is ready earlier than expected, we will let you know right away.

</details>

<details>

<summary><mark style="color:$primary;"><strong>Scenario 3:</strong></mark> Early check in always allowed</summary>

## Always Allow — AI confirms every time

*Your setting: Always Allow*

If you prefer to always offer early check-in regardless of whether the apartment was occupied the night before, use the **`Always Allow`** setting. With this option, the AI will immediately confirm early check-in for every guest who asks and send the payment link as soon as they agree.

This is ideal if you have a reliable cleaning team that can always prepare the apartment in time, and you don't want the AI to check for scheduling conflicts.

</details>

&#x20;<mark style="color:$primary;">⚠️ While GuestReply validates availability based on your chosen settings, you remain responsible for ensuring the property is clean and ready for the guest's early arrival. Please ensure your external calendar/PMS availability is accurately synced to prevent double bookings.</mark>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.guestreply.ai/readme/user-manual/upselling/early-check-in.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.