# Onboarding an eligible partner

This article provides guidelines on how to onboard *[eligible](/connectivity/docs/request-to-book/eligibility)* partners to the *Request To Book* booking flow.

## Inform partners about how the product works

Before bringing a partner on board with *Request to Book*, you, the Connectivity Provider *must* inform the partner on how the [RtB flow](/connectivity/docs/request-to-book/overview#rtb-flow) works.

To do this, **you must show the following text on your interface when onboarding a partner:**

Onboarding
**When using request to book, the booking process will be as follows:**

* Guests who want to make booking with the checkin that is more than 48 hours in the future will be able to find your apartment and send the booking request.
* You'll have 24 hours to accept or decline the request.
* Guests will have 24 hours to finish their booking and confirm their stay.


**This is how Booking.com shows the above text in our registration flow when the partner selects the Request To Book option.**

![Information to show while onboarding properties to RtB](/assets/registration-information.5c0a9c7a8e1ef3cdb146640a5d43ad1415f651567e91d7d159c2b0a55caf233f.d44379f7.png)

**Partners should be aware that they are expected to take action on the request within 24 hours by either approving or rejecting it.**

## Inform partners about non-discrimination policy

Connectivity providers must inform their partners that when they use *Request to Book*, they are subject to the *same* non-discrimination policy as partners who *do not* use a connectivity provider.

**The following text and non-discrimination policy must be displayed** to partners *each time* they accept or decline a booking request on the provider interface:

You must display this non-discrimination policy
By accepting or declining this request, you acknowledge that you are doing so in accordance with Booking.com's [non-discrimination policy](https://partner.booking.com/en-gb/help/legal-security/policies-local-laws/non-discrimination-guidelines-when-accepting-or-declining).

This is how Booking.com displays the disclaimer in the Extranet. You *must* also display this disclaimer where properties manage (accept or decline) incoming booking requests.

![Non discrimination policy to show on request detail page](/assets/nda-policy.512239215e96cf9088e66301a040def88886b352e6698b6ab0bf89340b5e6962.d44379f7.png)

## Getting started

To get started, you need a property with RtB booking model. You can leverage [Content API](/connectivity/docs/tsk-create-property#enabling-request-to-book) `OTA_HotelDescriptiveContentNotif` call to:

* Onboard a new [eligible](/connectivity/docs/request-to-book/eligibility) property, or,
* Change the *booking model* (`RTB` or `IB`) of an existing [eligible](/connectivity/docs/request-to-book/eligibility) property


RtB Provider Feature
In order to make use of the Content API to change a property's booking model to *RtB*, you must have the `content_api_rtb_enabled` feature on. You can do this in the provider portal by going to your [feature management](https://connect.booking.com/feature_management).

Please note that, [eligible](/connectivity/docs/request-to-book/eligibility) partners can also use Extranet policy page to change their preferred booking model, at any given time. For detailed steps please refer to [the partner portal article](https://partner.booking.com/en-gb/help/reservations/manage/everything-you-need-know-about-request-book).

![Example showing opt in and opt out UI in Extranet](/assets/opt-in-opt-out.2c4827cb098dfea15cbccd636e0376593eb42dec630f6702a2c4a6b24cb26a2c.d44379f7.png)

Dive into [Content API](/connectivity/docs/tsk-create-property#enabling-request-to-book) documentation to get started with opting-in & opting-out of RtB.

See [Pre-reservation messaging](/connectivity/docs/request-to-book/pre-reservation-messaging) documentation on how to enable and use Messaging API for RtB pre-reservation messaging and its limitations.