The questions hotel teams actually ask.

Most properties are live within 30 days, and some in two weeks. We do the setup, the design and the launch. The pace depends on one thing: how quickly you get us what you have and approve what we draft.

Amenities, services, hours, policies, your local picks, and your brand assets if you have them. Most of it already lives in a binder behind your front desk, on your website, or in a folder of photographs. A spreadsheet is fine. So is a PDF.

A kickoff call, a build, a review and a launch. You see the guide on a phone before anyone else does; your editors get their logins; the QR codes go to the rooms.

Your team edits it themselves, and we stay on the other end of a request button inside your own portal — with screenshots, so nobody describes a problem over the phone. A report arrives every week and every month.

Yes — you can see it right now, without talking to anybody. The Continental is a complete demo hotel running on the real product: scan the code on this site and it opens on your phone. On a call we walk through your own property instead of a slide deck.

A one-time development fee, then a monthly hosting and service fee, set per property by size and scope. The spoken concierge is an add-on, priced separately from the typed one.

Because a 60-room boutique and a 400-room downtown hotel are different pieces of work. Fifteen minutes gets you a real number for your property rather than a range that fits nobody.

No lock-in. Cancel with 30 days’ notice; renewal is month to month.

Yes. Bundle pricing starts at 3 properties and improves at 5. Larger portfolios get their own agreement.

Hosting, security, support, design changes we make for you, and your editor accounts. The edits your own team makes are unlimited and cost nothing.

They scan a QR code, tap an NFC sticker, or follow a link in a message. No app, no login, no download. On a laptop the guide shows a screen that hands them to their phone, with its own code.

Yes. The same link works in a pre-arrival message or a confirmation email, and nothing expires — guests use it before, during and after the stay.

No. It answers the questions your desk answers twenty times a shift so your team can be present for the rest. Every path out of it leads back to a person.

It is a web page in the guest’s own browser, so it inherits the text size, contrast and screen reader their phone already has — and the guide has its own text-size control as well. We build to WCAG AA and check the colors of every hotel’s palette against it.

The desk is still there. This is a relief valve, not a replacement.

Yes, and the important part is what it is allowed to know: it answers only from your guide and your lists. If the answer is not there, it says so and passes the guest to your desk. It never guesses a price, a time or a distance.

Both. They can type, or hold a button and speak, and the answer comes back out loud and in writing. Spoken answers are the same checked answers as the typed ones — the voice reads them, it does not invent them.

The one the guest used. Ask in Spanish and it answers in Spanish; the same for French, German, Japanese and the rest. You do nothing to set that up.

No. Credentials are held apart from the guide, encrypted, and released only to a guest who opened it from the link in their own room. The spoken concierge is not even given them to read.

It answers with your property’s own emergency and reception numbers before any AI is involved at all. That path works even if every model we use is down.

Themes and counts — “four guests asked about parking and the guide had no answer” — never the sentences guests typed. That is deliberate, and there is no screen in the product that shows them.

Both. The whole guide is translated — your words, your page titles, your lists — and guests switch with a pill at the top. The concierge answers in the guest’s language whether or not that language is switched on for the guide.

We run the pass for you. Edit one line in English and only that line goes stale; the next pass translates it and leaves the rest alone. Your guide never sits half-translated.

Fourteen today, including ones that need a different alphabet. If your guests need one we do not have, tell us.

You do, in the same editor we use, with up to three editor accounts. Change it, see it on a phone, publish. Design-level changes are ours — send a request from your portal.

About half an hour, and that is generous. The editor shows your guide as a phone; you double-click the words on it and type.

The knowledge stays with the property. A new hire reads the guide their guests read, and is useful on day one.

Yes, and that is the part hotels use most. Your lists — restaurants, spa treatments, rooms, events, offers — are yours to add to, reorder and publish. Events take themselves off the guide when they end.

A guest taps a button and their own phone opens a message to your number, with the request already written — “I’d like to ask about a late checkout.” Your team replies from the number they already use. We are not in the middle of it.

Completely. Your colors, your typefaces, your photography, your tone. Every color in the guide is a value we set for you, so a change reaches every page at once — and nobody can tell which platform it was built on.

Yes, and we host them ourselves rather than loading them from Google, so your guests are not tracked when they read your guide. We confirm you hold web rights before a font goes live.

Yes — guide.yourhotel.com, or your whole domain, with the certificate handled for you. The printed QR codes keep pointing at our address on purpose, so a lapsed DNS record can never kill a code already on a nightstand.

Wi-Fi, dining, amenities, hours, policies, room details, local recommendations, transport, menus, events, photographs, video, and PDFs where a PDF is genuinely the right answer.

Yes. Suites, club floors or a particular building can have their own pages.

Your team. Nobody knows your neighborhood like the people working the desk. We organize and design what you give us — and the concierge answers from exactly that, so your recommendations are the ones guests get.

No. No new platform, no IT project. It works alongside the messaging tools your desk already uses.

It does not need to, which is why a launch takes 30 days instead of a year. It sits beside your stack rather than inside it.

Yes. The code can be printed on key card sleeves, room signage, welcome cards, a table tent — anything a guest already touches. Each code can be named, so you can tell which ones guests actually use.

Any phone with a browser from the last several years, plus tablets and laptops.

Hosting is enterprise-grade with monitoring and redundancy, and the guide is served as a published snapshot — so an editor mid-edit, or a problem in the studio, cannot take a guest’s guide down.

No. No sign-in, no account, no email address. The guide sets no cookies at all, which is why there is no consent banner in front of it.

Counts, not people: which pages open, which buttons are tapped, at what time of day, on your hotel’s own clock. No IP address reaches our database — it is hashed before anything is stored — and nothing identifies a guest.

Yes. They go from the guest’s phone to your number. We do not store them, read them, or sit in the middle.

The question text is kept only as long as you choose — thirty days by default — and then removed, with the theme and the count kept. Shortening that setting reaches questions already asked.

HTTPS everywhere, data encrypted at rest, credentials encrypted separately again, and every editor account behind a sign-in link rather than a password. Each hotel’s data is isolated at the database itself, not by our code remembering to filter.

Yes, and it is straightforward because we do not collect personal guest data in the first place.

Each property gets its own guide, its own brand and its own lists. Your operations team sees every property in one place; each hotel’s team sees only its own.

Entirely. Different branding, different content, different policies, different languages. Consistency happens in how they are run, not in how they look.

Yes, and we would. Start where the desk is under the most pressure, then roll out in waves of three to five.

Whichever you prefer. Editor accounts are per property, so you can centralize or delegate.

Yes — properties in Boston, across independents, branded flags and portfolios.