Which PMS systems does OPEX integrate with?

OPEX is designed to integrate with widely used PMS systems including ElektraWeb, Oracle Hospitality OPERA, OPERA Cloud, Fidelio and Protel. Because the architecture is API-based, integration with a system outside that list can also be built; talk to our team for the scope specific to the system your hotel runs.

Does the chatbot work without PMS integration?

It works, but it doesn't recognise the guest. Without integration the chatbot answers general questions; because it doesn't know who the guest is, which room they are in or what their reservation covers, it has to ask for those details on every request and cannot attach the resulting task to the right record.

How does an integration project run?

In three stages: a system analysis that reviews the hotel's PMS, CRM and telephony infrastructure; a connection setup that synchronises guest, reservation and request data with OPEX; and end-to-end testing and go-live before the integration is switched on in production.

What is integrated besides the PMS?

Messaging channels — WhatsApp Business API, Instagram and Facebook Messenger — converge in a single inbox. Beyond that, OPEX integrates with reputation management tools such as Shiji ReviewPro and Customer Alliance, with telephony systems, and with departmental systems across housekeeping, front office and technical service.

What Is Hotel PMS Integration? Which Systems Does OPEX Work With?

Q: What is hotel PMS integration?

PMS (Property Management System) integration is the data connection between the hotel's core system — which holds reservation, room and guest records — and its other software. With integration in place, guest, room number and reservation details are never re-keyed into a second system; a record created in one appears automatically in the other.

A system that doesn't recognise the guest asks for a room number on every request. A look at how OPEX integrates with PMS systems such as ElektraWeb, Oracle OPERA, OPERA Cloud, Fidelio and Protel — and what that changes in daily operations.

"Could I Take Your Room Number?"

A guest writes on WhatsApp: "Could I get two more towels in the room?" If the system doesn't recognise the guest, the reply always starts from the same place: who are you, which room are you in. For the guest, that means giving the same information for the third time. For the operation, there is no guarantee that the task being created will attach to the right room and the right guest record.

The cause is not what the software can do — it is where the data sits. A hotel's reservation, room and guest information lives in the PMS (Property Management System). If the system talking to the guest cannot read the PMS, it has to ask the guest for information the hotel already has.

What Does PMS Integration Actually Do?

PMS integration is the connection that brings guest, room and reservation data from the hotel's core system into OPEX. Once it is in place, three things change:

The guest is recognised automatically. The number a message arrives from, or the user signing into the app, is matched to the active reservation in the PMS.
Requests land on the right record. The task created is linked to the room, the reservation and the guest profile; "who raised this request" never becomes an open question later.
Data is never entered twice. Information created at the front desk is not retyped on the operations side.

OPEX is designed to integrate with widely used PMS systems including ElektraWeb, Oracle Hospitality OPERA, OPERA Cloud, Fidelio and Protel.

Integration Doesn't Stop at the PMS

In hotel operations, guest data never sits in a single system. The integration layer therefore reaches beyond the PMS:

Messaging channels: WhatsApp Business API, Instagram and Facebook Messenger converge in a single inbox; whichever channel the guest writes from, the conversation is written to the same CRM record. We covered that structure in One Shared Inbox.
Departmental systems: Integrating with housekeeping, front office and technical service flows routes each incoming request to the right team automatically.
Review and survey platforms: Guest reviews and survey results from reputation management tools such as Shiji ReviewPro and Customer Alliance feed into the operational flow.
Telephony: Call centre conversations are linked to the relevant guest record.

Why a Single Guest Profile Starts With Integration

The value of a hotel CRM comes from being able to see the guest as a whole. That completeness doesn't appear on its own: when PMS and CRM data merge into one guest record, teams stop entering the same information repeatedly and the guest's history is read in one place.

In other words, the "single guest record" is not an interface choice — it is the output of integration. We looked at what that record does in daily operations in One Guest Record in Hotel CRM.

Rollout Runs in Three Stages

The biggest concern in integration projects is disruption to live operations. The process is therefore run in stages:

System analysis — Your hotel's PMS, CRM and telephony infrastructure is reviewed and the integration scope is defined.
Connection setup — The necessary API and data connections are built; guest, reservation and request data is synchronised with OPEX.
Testing and go-live — The integration is tested end to end before it goes into production, with your team informed at every step.

Because the architecture is API-based, integration with a new PMS, CRM or telephony system can also be built quickly and at low risk. A system not being on the list does not mean integration is impossible.

In Summary

The first question to ask when evaluating hotel software is not "which features does it have" but "does this system know what the hotel already knows?" PMS integration is precisely what delivers that: an operation that recognises the guest, attaches requests to the right record, and never asks for the same information twice.

For supported systems and the rollout process, see the Integrations page; for the guest profile that integration feeds, see CRM Management.