For hotels

What your desk knows, in every room.

The concierge answer, the one about the good restaurant two streets back, does not scale past the people standing at the desk. A guide does: made per booking, in the guest’s language, carrying your brand and nobody else’s.

A hotel already gives guests something on arrival — a printed map, a card of recommendations, a PDF nobody opens twice. It ages, it is in one language, and it says nothing about the street it is handed out on.

This replaces it with something on their phone that carries your name, is written in the language of the booking, and keeps working in the metro. Your colleagues make them themselves, each with their own login, and you see everything the team has sent out.

What runs in production, right now

Your brand on every guide the team makes

Logo, favicon, your two colours and the support address guests write to are set once for the hotel. Every guide anyone on the team makes from then on carries them.

Colleagues with their own logins

Invite the desk yourself and decide per person what they may do: make guides, or oversee everyone’s. Nobody has to email us to add someone.

One view over everything you send out

Managers and owners see every guide the hotel has made, not only their own — and can withdraw a share link the moment it should stop working.

Guest reports, scoped to your hotel

What guests report on your guides reaches your own inbox and stays there. Taking down what a guest wrote stays ours to do: a hotel deleting criticism of itself is not a feature we are going to build.

A guide per booking, in the guest’s language

Six languages, one per guide, chosen when it is made. Made in a couple of minutes at the desk, shared as a link or a QR code, working offline from the moment it opens.

Quotas set to your volume

How many guides you may hold is set per hotel, where your operation actually needs it. The “Powered by VidiVeni” line at the foot of a guide comes off on request.

And what you do not get, yet

Everything above runs in production today. This is the rest of it — what a host reasonably expects and we have not built:

Your own web address. Guides are shared from vidiveni.app links. guides.yourhotel.com is not wired up.
Your own places. Every guide draws on one shared, checked catalogue. You cannot yet keep a list of your own — the bakery you send everyone to — that only your guides use.
Plans you can pick yourself. There is no checkout and no plan picker. During the pilot it is a conversation, which is why this page ends in a form rather than a card number.
A connection to your booking system. No API and no keys. A guide is made in the dashboard, by a person.
A dashboard in every language. The screens you make guides in are in Dutch and English; French, German and Spanish are not there yet. The guide your guest receives is in their language either way.

All of it is on the roadmap. None of it is in the product, so none of it is in the price.

Getting started

Bring the person who works the desk.

Ask for a demo and we make a guide for your own address on the call — and let whoever would actually use it try making the second one.

Request a demo