AI concierge
AI concierge for hotels
The phone rings while you check a guest in, and a Zalo message from last night is still open. Lynn answers from your data on the website, WhatsApp, Zalo, the phone, an avatar, and the guest app. You go live within four weeks.
42 properties are live on 3 continents.

Example screens with demo guests in a lab hotel, names removed.
Where the guest waits today
01
The phone rings at check-in
A guest stands at the desk with a passport. The phone on the counter rings. The caller asks the check-in time. You answer, or you finish the key and let it ring. The person in front of you waits.
02
The Zalo message waits until morning
A guest writes on Zalo after dinner, or on WhatsApp, and asks for a late check-out. By morning the message sits under newer notes. You reply after breakfast. The guest asks again at the desk.
03
Two colleagues, two check-in times
One colleague says check-in is at 14:00. Another tells the guest at the desk it is 15:00. The house rule sits in a folder, or in one person's head. The guest holds two check-in times.
The same questions, two ways
On the left, the phone, the Zalo message and the check-in time as they sit today. On the right, Lynn answers from your data, and the thread goes with the question.
| Time | Channel | Guest question | Answered |
| 15:10, check-in | Phone | What time is check-in? | no |
| 22:40 | Zalo | Can we book a dinner? | ? |
| 07:50 | Is a late check-out possible? | no | |
| At the desk | Two staff | What time is check-in? | ? |
I wrote on Zalo last night. What time is check-in?
The phone is ringing. I think it is 15:00.
Your colleague said 14:00. Which check-in time is it?
Example screens with demo guests in a lab hotel, names removed.
What you lose if nothing changes
The phone rings again at the next check-in. You choose the guest at the desk, or the caller. A caller who gets no answer takes the question elsewhere. The key takes longer, and the phone is still on the counter.
The Zalo message from last night is still open when the guest arrives. They quote one check-in time. The folder has the other. A complaint and a group request sit in that same thread, with no owner.
What an AI concierge does for your hotel
Lynn reads your hotel's data and answers on the channels your guests already use. She does not invent a price, a discount or a house rule. You go live within four weeks. The next step is one 30-minute call.


















Example screens with demo guests in a lab hotel, names removed.
AI concierge screens we have built
Screens from a lab hotel, with demo guests and names removed. Click through, or let it run.

A guest asks Lynn what to do on a rainy afternoon, and Lynn suggests the wellness area, a massage, lunch and the bar.
Example screens with demo guests in a lab hotel, names removed.
Live now
42 properties on 3 continents
42 properties are live on 3 continents. Lynn reads each hotel's own data. We work with Optimum Hospitality and Hoteliers365.
42
properties live on 3 continents
How the four weeks go
Most properties go live within four weeks. We learn the hotel, Lynn learns your data, and we connect the channels. Day 28 is for guests.
Days 1 to 7
We learn the desk
We sit with the people who answer the phone at check-in. We take the house rules, the menus and the check-in time. We note what your team keeps: complaints, groups, and anything not in the source.
Days 8 to 14
Lynn learns your data
Lynn reads the rooms, menus, extras and house rules you gave us. A price, a discount or a house rule stays out unless it is in that data. You check a sample before guests see it.
Days 15 to 21
We connect the PMS and the channels
We connect your PMS, such as Mews, Opera PMS, Cloudbeds or Apaleo. We connect website chat, WhatsApp, Zalo, the phone, the avatar, and the guest app for wine, dinner, extras, late check-out and housekeeping.
Days 22 to 28
Your team tries one question
Your team asks the check-in time on the phone, sends the Zalo example, and opens the guest app. A complaint and a group question go to a person, with the whole thread. Day 28 is live for guests.
What sets the price and the time
Six things decide the price and the time. On a 30-minute call we set them against your hotel. There is no amount on this page.
- Channels you open: website chat, WhatsApp, Zalo, other messaging, the phone, and the avatar.
- The guest app: wine, a dinner, extras, late check-out and housekeeping, and how much of that your data already describes.
- The PMS Lynn reads, such as Mews, Opera PMS, Cloudbeds or Apaleo, and how much of the stay she can see. The list is on the integrations page.
- Your data: rooms, menus, extras and house rules. A price or a discount that is not written down goes to your team.
- Handoff: complaints, groups, and anything missing from the source, plus any extra rule you add.
- Properties and languages: how many properties, and which of the 50+ languages your guests use. One property goes live within four weeks. More properties take longer.
Questions before the call
Lynn takes what is already in your data: the check-in time, a written house rule, a menu, wine, a dinner, housekeeping. Your team keeps complaints, groups, and anything not in the source. The handover includes the whole conversation. The desk still checks the guest in.
In the guest app a guest can order wine, book a dinner, request an extra, ask for a late check-out, or send housekeeping. Lynn uses your data. She does not invent a price or a discount. A group, and any request the data does not cover, goes to your team with the thread.
The PMS systems on the integrations page, including Mews, Opera PMS, Cloudbeds, Apaleo and Protel. Lynn reads the details your desk already uses. On the call we name your system and what she can read.
She does not invent a price, a discount or a house rule. If the answer is not in your data, the question goes to your team with the whole conversation. The guest gets one answer from your team, not a guess.
The whole conversation: the channel, the question, and what Lynn already said from your data. Complaints, groups, and anything not in the source go to the team this way. The guest does not retell the Zalo message or the phone call from check-in.
Lynn answers in the language the guest uses, from the 50+ languages on the site. You do not write a script per language. On the call we note the languages your guests bring.
Vertize is based in Belgium and works under the GDPR. We sign a data processing agreement. Conversation logs are kept for a maximum of 30 days unless you ask otherwise. Data is encrypted in transit and at rest. We do not sell it or share it. Lynn says she is an AI at the start.
Most properties go live within four weeks. Day 7 is your hotel, day 14 is your data, day 21 is the PMS and the channels, and day 28 is your team. You do not need technical skills. More channels or more properties can take longer. We say so on the call.
Bring the phone and the Zalo thread
Bring the hour when the phone rings at check-in, a Zalo message that waited until morning, and the check-in time two colleagues give differently. On the call we name the four weeks and which factors change the price and the time.
Areas we serve
We work on site across Vietnam, from Hà Nội to Cà Mau, and remotely with clients in Europe, Asia and the Middle East.
Our main services
Each system is built for your business and connected to the tools you already use.

