Skip to content
Vedom home

Product

Everything in the hotel that isn’t the booking.

Six areas on the web for managers and the desk. Five tabs on the phone for everyone on the floor. Ask Vedom and Studio over all of it. One set of records underneath: the property, the people, the work, the guests, the knowledge and the numbers.

Vedom is in build. This page describes how it is designed to work, and every screen is a design with example data. Founding pilots are targeting early 2027.

01 / 06

Today

18 of 26 ready. 214 needs you by 10:00.

What needs you now, the live room board, arrivals and departures, the handover, every open job in one list, and the calendar. The board is ordered by what unblocks the next arrival.

  • Room turns sequenced by the next arrival, status written back to the PMS
  • Handover written from the PMS and the day’s notes, every line with its source, signed off by a person
  • Tasks, snags with a photo and no name attached, maintenance, lost and found and recurring checks in one list
The Today area as designed: what needs you now, why, the two fixes on offer, and who is on shift.
The handover, written from the day’s data, every line with its source, signed off by a person.
The handover, written from the day’s data, every line with its source, signed off by a person.
Arrivals with a suggested room plan, reasons per room, confirmed by a person and sent to the PMS.
Arrivals with a suggested room plan, reasons per room, confirmed by a person and sent to the PMS.

02 / 06

Guests

3 requests open. Oldest is 212, 18 minutes.

Who is in the house, what they prefer and what happened last time. One inbox for WhatsApp, SMS, email and OTA messages; every message becomes a request with an owner and a time. Reviews, events and members live here too.

  • Profiles from reservations, merged, with consented preferences and access-logged allergy notes
  • The Vedom Concierge answers alone only on topics you allow; everything else goes to a person with a draft
  • Compensation posted to the folio, post-stay surveys, reviews in one place
A guest profile as designed: preferences, notes, past stays and the open request.
One guest inbox for WhatsApp, SMS, email and OTA messages, shared by guests and team.
One guest inbox for WhatsApp, SMS, email and OTA messages, shared by guests and team.

03 / 06

Team

Saturday is two short. Open shift sent to 5.

People and their certificates, a rota built on the occupancy forecast, open shifts offered to people who are qualified, the time clock, team chat with translation, and the hotel’s own SOPs and quizzes. Not an HR system.

  • Rota gaps shown where the forecast needs more hands; one move to reassign
  • Clock in and hours ready for payroll; chat translated with “show original”
  • SOPs, onboarding and quizzes with sign-off, so week one needs no course
The rota for the week as designed, built against occupancy, with the short days marked.
Team messages, each shown in the reader’s language.
Team messages, each shown in the reader’s language.

04 / 06

Stock

Bath towels under par. Order to Weber drafted.

Counts by store and par levels on the phone, suppliers and contacts next to the items they deliver, and an order drafted when something runs low.

  • Counts on the phone, totals on the web
  • Par levels and reorder lists
  • Suppliers, orders and invoices
Stock counts as designed, by store, with the items below par.

05 / 06

Insights

€14.20 per occupied room. Down €1.10 on last week.

A written brief first, then a few quiet charts: the week, labour against occupancy, revenue read from the PMS, turn times. Every number links back to the rows it came from. Nobody is ranked.

  • Labour cost per occupied room against your target, daily
  • Hours by department against the forecast
  • Revenue read from the PMS; Vedom never sets prices
The weekly summary as designed: occupancy, labour per occupied room, average room turn and complaints.

06 / 06

Settings

Who sees what. Your property, your rules.

Property details, people and access, modules on and off, your own templates, connections, privacy tools and your plan, all in one place.

  • Custom roles and access per person; two-step sign-in and access reviews
  • Templates: handovers, checklists, inspections, forms, quizzes
  • Retention, GDPR tools and the PMS connection
People and access as designed: who can sign in, two-step sign-in and access that needs a look.

Over every area

Ask it. Shape it. Connect it.

Ask Vedom

Any question, any language, with its sources.

The ask bar on the web and the Know tab on the phone. Anyone permitted asks a question or gives an instruction in their own language; it answers from all of the hotel’s data, only within what that person may see, and proposes work for a person to confirm.

  • Every answer carries its sources: “From the room board and the rota, 09:41”
  • Standing approvals for small, reversible actions; each one lands in “review what the assistant did”, with Undo
  • Every screen works with it switched off
Ask Vedom as designed: “Which arrivals are behind?” answered with one room behind, a suggested fix and seven rooms on pace.

Studio

Your own tools, built in a sentence.

Describe a report, an automation, a small app or a check, and Studio builds it on the hotel’s own data: a linen log, a bike-hire list, a VIP welcome task. It shows what the tool reads, who it tells and when it runs. Nothing is live until a person publishes it.

  • Built on the same records as everything else, so it sees only what the builder may see
  • Tools keep running past any AI allowance
  • Tagged with who built it: “Linen per floor · Built in Studio by Mira”
Studio as designed: Mira describes linen tracking, and the preview shows the log, the board and the warning it built.

Connections and the API

Apaleo first. Everything writes back.

Apaleo through its open API, Mews and Cloudbeds next. Then the till, payroll, accounting, door locks, reviews and channel managers. The open API and the developer portal are included, for the tools that need “room ready”.

  • Documented APIs only, with credentials issued to us; never a borrowed login
  • Status, assignments and approved charges written back; rates, availability and cards never touched
  • An open, versioned API (OpenAPI), included in every plan
Connecting Apaleo as designed: what Vedom reads, what it writes back, and what it never changes.

Phone app

Five tabs for the floor. Her language, offline, two taps.

One app for iOS and Android, on staff members’ own phones or a shared device at the desk. It keeps ticks, photos and messages when the signal drops in the basement, and sends them when it returns.

  • Today: Clocked in, what’s next, my rooms in order.

    Today

    Clocked in, what’s next, my rooms in order.

  • Board: The rooms or jobs for my role, live.

    Board

    The rooms or jobs for my role, live.

  • Chat: Team threads, translated for each reader.

    Chat

    Team threads, translated for each reader.

  • Know: Ask the house: SOPs, procedures, answers.

    Know

    Ask the house: SOPs, procedures, answers.

  • Me: My shifts, hours and certificates.

    Me

    My shifts, hours and certificates.

What the assistant does

It drafts, answers and builds. People decide.

  • Answers questions about the hotel, with the sources shown
  • Writes the handover from the PMS and the day’s notes, for a person to sign off
  • Drafts replies to guests in your tone; the Concierge answers alone only on topics you allow
  • Translates chat, SOPs and the app into each person’s language
  • Fills in room, trade and urgency from a snag photo
  • Builds tools in Studio from a sentence

It never.

  • Decides who to hire, rates staff or ranks them
  • Books, sells or answers the phone
  • Sees health or allergy details

What Vedom is not

Beside your PMS, never in its place.

  • Not a PMS

    Your PMS keeps rooms, rates and money. Vedom is built to work alongside it.

  • Not a booking bot

    The Concierge answers what you allow. It never sells, never books and never answers the phone.

  • Not revenue management

    We show revenue from your PMS. We never recommend prices.

  • Not an HR system

    Team holds people, rota, hours and SOPs. Hours go to your payroll provider.

Design · in build. Screens from the Vedom product design; names and numbers are example data.

Put your hotel forward.

Ten founding places for hotels on Apaleo. One email field, and you confirm it before anything else happens. The founder reads every application; yes means a 20-minute call about your hardest morning.