Part of the Ellipse platform

Messages API — central communication with guests

Ellipse is a cloud system for hotels and restaurants. Central communication with guests from OTAs and from direct bookings.

See the module in practice

Ellipse Messages API — Booking.com, Expedia, Airbnb, Vrbo and direct bookings in one central inbox

1 inboxmessages from several booking channels in one place
1 vláknocommunication tied to that guest's reservation
OTAcentral guest communication from portals and your own bookings

ALL MESSAGES. ONE PLACE.

The guest writes through the portal. You reply from Ellipse.

Guest communication is moving into the closed messages of booking portals. Instead of checking Booking.com, Expedia, Airbnb or Vrbo one by one, the desk can work on conversations next to the reservation in Ellipse. One inbox, one team and the whole stay in one place.

One central inbox
- Messages from OTAs and direct bookings
- One communication history
- Incoming and outgoing messages in one thread
- Less switching between OTA extranets
Booking context
- A message tied to a specific stay
- Dates, guest and booking in one place
- A faster reply without hunting for details
- Communication as part of the PMS workflow
The desk and the team stay in the picture
- Notifications for new messages
- Connection to Ellipse Team
- The option to handle messages away from the desk
- One process for several properties
Automation and AI
- Reply templates for repeated questions
- Automatic messages by stage of the stay
- Tied to check-in, payments and upsell
- Ready for AI drafts and assisted replies

How many extranets does reception open for one guest question?

We will show how to bring portal and direct-booking messages into one inbox in Ellipse, and tie them to the reservation, the team and the stay.

Book a Messages demo See the Channel Manager

FAQ

Questions about this module

What is Ellipse Messages API?

Ellipse Messages API is a central communication layer that connects messages from supported booking portals and direct bookings with Ellipse PMS. The front desk can handle guest communication on the booking without constantly switching between OTA extranets.

Why is API communication with the guest becoming more important?

Booking portals increasingly limit sharing of a guest's personal contact details. The hotel may not have a direct phone number or personal email, so messaging through the portal stays an important way to reach the guest.

Which portals can central communication include?

It is built for communication through supported OTA messaging APIs, including portals such as Booking.com, Expedia, Airbnb and Vrbo, and for direct bookings created through your own Ellipse channels.

Is a message linked to a specific booking?

Yes. The aim is that the front desk sees the message together with the booking, the stay dates and the relevant guest details, and replies with context instead of looking it up elsewhere.

Can messages be handled away from the front desk?

Yes. Communication can be connected to Ellipse Team, so authorised team members can reply or follow conversations from the mobile work environment.

Does it support automatic messages?

Yes. Central communication can be combined with automated messages along the booking lifecycle, for example before arrival, during the stay or after departure, according to what that channel allows.

Can communication also be used for upsell and online check-in?

Yes. Messages can point the guest to online check-in, payment, managing the booking, extra services or other Ellipse self-service functions.

Ella answers a question about Ellipse right on this page.