> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dialogshift.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Protel / Planet Integration

> How to use Protel/Planet with DialogShift for booking agents and Journey Messaging.

The Protel/Planet integration connects DialogShift to the Protel Cloud API. Chat AI and Phone AI can retrieve availability and rates and create pay-at-hotel bookings directly. Journey Messaging can also use PMS data from Protel/Planet.

<Note>
  **Closed Beta Rollout:** This integration is not generally released for production use yet. Activation is only available in coordination with Customer Success.
</Note>

## Prerequisites

* Your hotel uses the Protel/Planet Cloud API.
* API key and API base URL are available.
* For Journey Messaging, the correct PMS context for your hotel is known.

## Activate the integration

Because there is a Protel/Planet integration page in the DialogShift app, the hotel can enter the credentials itself. For Journey Messaging, Customer Success also confirms the PMS context.

1. Enter the API key and base URL in the DialogShift app.
2. Activate the Protel/Planet integration.
3. For booking agents, enable only room categories and rates that can be booked without prepayment.
4. For Journey Messaging, Customer Success sets up the PMS context.

## Booking agents

| Topic                                   | Behavior                                                                                         |
| :-------------------------------------- | :----------------------------------------------------------------------------------------------- |
| Company code / coupons / discount codes | Not supported.                                                                                   |
| Minimum stay in the dialog              | Not explicitly communicated by DialogShift.                                                      |
| Checkout workflow                       | Direct booking in Protel/Planet, without a DialogShift checkout link.                            |
| Payment link in chat                    | Not supported.                                                                                   |
| Payment link by phone                   | Not supported.                                                                                   |
| Cancellation of unpaid bookings         | No. During a technical partial failure in a multi-room booking, DialogShift attempts a rollback. |
| Payment variants                        | Only pay-at-hotel/flexible rates. Prepaid rates should not be enabled for the agent.             |
| Offer/quote function                    | No.                                                                                              |
| Required guest data                     | Email, first name and last name are required. Phone number is optional.                          |

## Booking agent configuration

**Room categories.** Room categories are configurable so the agent only books categories directly in Protel/Planet that are suitable for the dialog. Enable only public, available categories.

**Rates.** Rates are configurable because Protel/Planet only supports direct pay-at-hotel bookings through DialogShift. Enable only flexible or pay-at-hotel rates and exclude prepaid or payment-required rates.

## Journey Messaging

| Topic      | Behavior                                                                                     |
| :--------- | :------------------------------------------------------------------------------------------- |
| Supported  | Beta. Protel/Planet can provide booking and guest data for Journey Messaging.                |
| Data flow  | DialogShift reads reservations from Protel/Planet regularly.                                 |
| Updates    | Polling, about every 15 minutes. Changes are therefore not visible immediately.              |
| Activation | Credentials can be maintained in the DialogShift app; Customer Success adds the PMS context. |

## Configuration

Journey Messaging flows and templates are maintained separately under **Journey Messaging**.
