# Activation Scenarios

KribOS supports two practical activation paths.

![Two OTA activation scenarios](/files/TghRMf9UlHPy2Z6jxsn0)

## Scenario A - Existing OTA listings

Use this path when your properties already exist on Booking.com, Airbnb, Expedia, VRBO or another OTA.

### Workflow

1. You choose the OTA in KribOS.
2. You provide the listing, hotel or property identifier.
3. KribOS retrieves or verifies the available OTA information.
4. You validate the mapping between OTA listings and KribOS properties.
5. KribOS activates synchronization after verification.

## Scenario B - KribOS first

Use this path when you want to create clean property data in KribOS before connecting OTAs.

### Workflow

1. You create properties, rooms or units in KribOS.
2. You add the OTA identifiers or listing links when available.
3. KribOS prepares the OTA correspondences.
4. The KribOS team finalizes activation with you.

## Why mapping matters

Mapping prevents a reservation or availability update from being linked to the wrong property.

Before activation, KribOS verifies:

* property match;
* room or unit match;
* rate plan match when applicable;
* availability and restriction behavior.


---

# Agent Instructions: 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:

```
GET https://kribos.gitbook.io/kribos-docs/for-hosts/activation-scenarios.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.