What’s new
We ship. Here’s the proof.
No logo wall, no adjectives — just what went live, dated to the day. Everything below is running in production today; the frontier we’re building next is shared with prospects on a call.
Write it once — it follows the guest everywhere
Since July, your announcements, partner copy and offers can be written once, machine-translated and published in six languages after your review. Your welcome message, your example questions, your guide’s tagline and your reception’s contact details now go through the same step — publish a translation, and guests in that language read your own words, just in theirs. The guest’s own language is decided earlier too: from the link they were sent, their browser, or the language on their booking, set the moment they arrive rather than only settling once the conversation is under way — and it now travels with them into the day-by-day plan the concierge writes them and every way they export it.
Now it can show them, not just tell them
Upload your photographs and diagrams — the breakfast room, the climate panel on the wall, the way in from the street — and the concierge finds the right one by its published description, then puts it in the answer it illustrates. It still says in words what is in the picture, so a guest who cannot see it loses nothing. On WhatsApp the photograph is sent as its own image message after the reply; on a voice call it appears in the written conversation once the call ends. Each upload is described automatically for you to correct, and nothing reaches a guest until you have read that description and published it — and when you remove a photo, the concierge stops showing it. Photographs and diagrams, not video.
Their link opens the concierge, not a front door
A verified guest’s link used to land on a welcome page with a guide to choose; at a property it now opens the conversation itself — greeted by name, dates already known, with the guide you configured already there. And where you offer more than one, the others are offered as a small choice under that first message rather than a dialog standing in the way: tap one and they take over, or send a message and the choice steps aside. The full list of guides stays a tap away, on the welcome page the header links back to. Event links are unchanged.
A welcome when they check in
When your PMS reports a check-in, a welcome goes out to the guest without anyone at the desk doing a thing: an email in the language on their booking where you serve it, carrying their own private link straight into your concierge — which already knows their name, their room and their dates. Where a property confirms it collects WhatsApp consent at check-in, a short note goes to the number on the booking as well; it carries no link, because a reply is all it takes — and that reply binds the thread to their stay. Off until you turn it on, sent once per stay however many times your PMS repeats itself, and held to a daily limit per property.
The concierge speaks first — and every guest can stop it
A guest no longer has to come back and ask. When your team acknowledges a request or marks it done, the message goes out on its own — over WhatsApp, or by email to the address on the booking. A WhatsApp message that would land in the night window is held until it ends; sends are capped per guest and per day; and control sits with the guest throughout. A STOP on WhatsApp ends those messages on that channel and START brings them back, request notices we email carry a one-click unsubscribe link, and an address that hard-bounces or reports us is suppressed without anyone asking. We keep a record that a message was attempted, never what it said, and the suppression list holds a keyed hash of the address rather than the address.
Your agent channel, split by who’s asking
The agent page in your admin is now four lanes, one audience each: what a verified guest’s own AI can reach; what you put in front of agents before anyone books — your card, your marketing pack, the partner feed and the attributed clicks it earns; the keyed endpoint your integrations and partners come in through; and what agent traffic actually did. A lane that does not apply to you — the guest one, at an event — is not shown at all. The same controls under the same names, in the order you would go looking for them.
Local knowledge, curated once and shared by every property in a city
Local facts about a city no longer have to be written by each property. Aikebom curates a shared layer attached to a place rather than to a client: we maintain it, every property and event whose city it covers inherits it, and there is nothing to upload at your end. A source’s licence is checked before anything may be published from it; only facts that stay true belong here, and time-bounded material keeps reaching guests through live, date-windowed lookups instead; a person reads the source and presses Publish, because nothing here publishes itself; and the nightly check only detects — it re-reads what is published, flags what has changed, and rewrites nothing. Nothing reaches a guest from this layer until someone has read a source and pressed Publish.
Acknowledged, then done — the guest hears both
A guest who asked for something used to be told that staff would follow up, and then never hear another word. Now the two presses your team already makes in the queue reach them: acknowledged — someone has seen it and is on it — and done. Each message is written by us rather than by the model, in the guest’s own language, and names only the kind of request: never what they wrote, never who handled it, never a time. And they are told the state a request is in now, never its history — acknowledged and later finished is two messages, in order, and nothing else.
Your property became a business AI agents can address
Every property and event can now publish an agent card — the emerging agent-to-agent (A2A) standard — at a fixed address on its own domain, so a travel organiser’s, DMC’s or corporate booker’s assistant can address it directly: what it is, where it is, who its official partners are and what they’re currently promoting, every partnership disclosed and every link tracked. Alongside it, a marketing pack your own team writes — positioning, meeting and function spaces with capacities, room types, current packages, accolades and sales contacts. Public and read-only by design: no guest data, no bookings, no key required, and lapsed offers filtered out. Aikebom runs one on itself. Switched on per client, off by default.
Your agent channel, in one place
Everything about your property’s AI endpoint now lives on one page in your admin: what agents can see, exactly what an agent receives when it asks about your partners — rendered by the same code that serves it — which tools are exposed, the keys issued for your integrations, and what agent traffic actually did. Partner links carried into AI channels now carry a marker, so your dashboard reports attributed clicks from agents; links issued before this date carry no marker, so the real figure can only be higher. Revoking a key takes effect within a few minutes.
The WhatsApp thread knows the guest
A guest who messages the property’s number is now matched to their booking — pushed by your PMS or your integrator — so the concierge greets them by name, knows their room and their dates, and files every request against the right one, with no link to open. A number the booking doesn’t carry can be linked with a one-time code from the front desk. On a property that serves only its own guests, an unrecognised number reaches a short reception notice instead. And a guest who writes after checking out gets a warm close, not a dead thread.
The concierge is on WhatsApp
Message the property’s number and the concierge answers right there — grounded recommendations, staff-confirmed requests, and a personal day plan that arrives as a message, share link included. It answers in the guest’s own language and switches the moment they do, whatever the property’s default. Same engine, same privacy limits as chat and voice. Verified end-to-end in production: onboarding, a built plan, and the share link — all inside one WhatsApp thread.
A login above your properties
A group running several properties gets one login above them all: a portfolio overview, the monthly reports rolled up across the estate, and a standards page showing where each property differs from the group’s own defaults for branding, languages and retention. Read-only and engagement-focused — the per-property admin stays where the work happens.
The guest’s AI can now act — requests still go through your staff
A verified guest’s own AI can now do more than ask: it can raise a request your staff confirm — a late checkout, housekeeping, an amenity — and add a stop to the guest’s own saved plan, which is theirs and needs no sign-off. Every request is logged and attributed (“via guest’s AI” on the staff screen), and the connection still expires with the stay. Verified end-to-end in production: a request raised by the guest’s AI, acknowledged by staff, and the status read back in the same conversation.
Add your stay to your own AI
A checked-in hotel guest can now connect their own ChatGPT or Claude to their stay — their room, their dates, their saved plan, the status of their requests. Personal, read-only, revocable, and it expires when the stay does. Verified end-to-end: a guest’s own Claude answering with the right room after a room move.
A report at the end — and every month
When an event ends the concierge now produces a briefing; for a property, a report every month. Sessions and assistant activity, the languages guests actually used, the questions it couldn’t answer — each with a suggested fix — partner and sponsor reach, and which tools external AI agents used, and what they couldn’t get. Counts, topics and an example for each, with most email addresses and phone numbers removed: no conversation text goes into it. Download it, or have it mailed to your own staff address.
The AI-visibility report
The dashboard now counts which tools AI agents used on your endpoint — and, more valuable, what they couldn’t get. Split by anonymous vs authorized, per tool, exportable.
An AI-readable index: /llms.txt
A property or event on its own domain — and the platform itself — now serves an llms.txt index — the convention AI agents use to find official information. Real clients become the official answer; our demos label themselves as demos.
Each property can be its own MCP server
Each client’s agent endpoint is now kind-aware: a hotel presents itself to AI assistants as a property — house facts, partners, what’s on — token-gated, read-only, with the partnership disclosure attached. Verified end-to-end inside a guest’s own AI.
PMS integration: the concierge knows the front desk
Bookings, check-ins, room moves and checkouts, pushed by your PMS or your integrator over a vendor-neutral contract. Announced as “in build” in early July; live before the month was out.
Write once, publish in six languages
Announcements, partner copy and offers: write in your language, machine-translate, review every string, publish. Each guest reads their own language — with the exact wording under your control.
A reception role for the front desk
A requests-only staff login: the queue refreshes itself at the desk, and reception mints each guest’s verified concierge link at check-in — booking reference, name and room, nothing more.
Answers from your documents
The Knowledge Library: upload manuals, menus and guides — or point at official pages — and the concierge answers with the source attached: “per the in-room guide, page 12”.
Hotels became a first-class product
Aikebom Concierge AI: always-on properties with rolling, per-guest privacy — a guest’s data deletes itself after they go quiet, and never lives more than 45 days past their last message.
Custom domains and the Welcome page
Each property or event can run on its own domain, and gets a localized welcome page, a QR entry kit, and a printable leaflet for the front desk or the ticket email.
Set up from the admin — no code
A new property or event is created, branded, given its programme and pointed at its official pages and PDFs from the admin, then taken live — zero code, zero redeploy.
Each date is the day the capability went live in production. Nothing on this page is a roadmap item.
See it on your property — or your event.
Book a 20-minute demo and we’ll show your property or event, your city, your partners and sponsors — running in a branded concierge.
- No engineering on your side
- Live in weeks
- No accounts & GDPR-by-design