Hostaway

The request is written into Zenvox with the reservation, the channel and the listing. Hostaway stays in charge of the stay, and the receptionist re-reads the reservation before answering the guest.

7 days, 20 answered calls, no card

Where your guest request lands

The request is written into Zenvox: the reservation identified, the originating channel, the listing, the person, the incident or change request. Hostaway stays in charge of the stay and its calendar. Cancelling a reservation stays with you: it is not written from Zenvox, and no key handover time is announced without confirmation from the ground.

With the connection, the receptionist reads reservations, calendars and message threads, and creates or updates a direct booking. You authorise access from your own Hostaway account; Zenvox asks for no password. Distribution channel permissions are granted separately from direct-booking permissions.

Hostaway holds listings, reservations, calendars and distribution channels; a guest calls because a message went unanswered, they already wrote on the booking channel, and cleaning is running late.

Read, create, update, cancel

What the receptionist does in Hostaway, action by action, and what stays the host's decision.

ActionWhat that means
ReadShe reads reservations, calendars and message threads. That read is what makes an answer useful: the receptionist answers about the stay as it stands, even if it changed the day before.
CreateShe creates a direct booking in Hostaway, with the listing, the dates and the guest. A booking on a distribution channel follows the rights that channel grants your account.
UpdateShe updates a reservation and re-reads the platform before each confirmation, because a stay can shift during the call.
CancelAn exceptional cancellation, a compensation or releasing an access code after identity verification belong to the host. The receptionist captures, passes on and alerts; she does not decide.

What is included, what needs an add-on

Answering the phone during a stay, identifying listing and reservation, capturing an incident and alerting under your rules belong to your real estate base. Cleaning and maintenance coordination, and picking a conversation back up across channels, are named add-ons. Every add-on is included in the free trial.

Add-ons that work with your software

Maintenance and vendors

Cleaning, repair, status and the answer back to the guest: a stay incident is settled by a tracked assignment, not by a reassuring message.

Web and SMS conversations

The same guest often writes across several channels. History shared with the phone saves them repeating a reservation number every time.

The authorisation, and what holds the truth

Here the most important rule is not access: it is the order of operations before a confirmation.

  • You authorise access from your own Hostaway account; Zenvox asks for no password
  • The platform is re-read before any change is confirmed to a guest — a stay can shift during the call
  • Distribution channel rights are granted separately from direct-booking rights
  • Releasing an access code follows your identity verification, not the caller’s good faith
  • A gap between Zenvox and Hostaway is flagged to the host, and nothing is confirmed while it lasts

Half past three, arrival day. Cleaning is running late on one listing. The call is taken by Zenvox, which finds the reservation in Hostaway.

GuestHi, I am standing at the door and my code does not work. I already wrote on the platform.

ReceptionistLet me take your name and your reservation number, and check the exact listing address with you.

ReceptionistI am sending this to the host right now, flagged that you are on site. An access code is released after identity verification, and the host does that.

The host receives the alert with reservation, listing, originating channel and the fact the guest is at the door. Nothing was promised about a key handover time cleaning had not confirmed.

When the connection is not there

The platform stays in charge of the stay, and the receptionist works in your Zenvox app.

  • The request is created inside Zenvox with reservation, listing and originating channel as the guest states them
  • Stay incidents raise the host alert under your rules
  • No access code is released without the identity verification you defined
  • You find the call, its transcript and its reason in the app
  • With the connection in place, the reservation is re-read in Hostaway, and your setup does not change

Questions about this connection

Can Zenvox change a reservation?

Yes: the reservation is re-read in Hostaway before any change is confirmed to the guest, because a stay can shift during the call.

Do distribution channel rights follow direct-booking rights?

No, they are two separate subjects. The receptionist creates a direct booking in Hostaway; on a distribution channel, she follows the rights that channel grants your account.

Does she release the access code to the guest?

Only after the identity verification you defined, and releasing the code belongs to the host. The caller’s good faith is not enough.

Cleaning is running late — what gets announced?

Nothing about a key handover time cleaning has not confirmed. The host receives the alert with the reservation, the listing, the originating channel and the fact the guest is at the door.

Does Zenvox ask for my password?

No. You authorise access from your own Hostaway account.

Where to next

See the practice concerned, or the full list of software.

Hostaway

The request is written into Zenvox with the reservation, the channel and the listing. Hostaway stays in charge of the stay, and the receptionist re-reads the reservation before answering the guest.

Start your free trial7 days, 20 answered calls, no card