Questions, answered straight.

Event apps own registration, badges and the agenda — and stop at the venue door. Aikebom knows your event just as deeply — the programme, the venue, live changes — and keeps going where the app stops: the whole stay, the city, the trip, by voice, in six languages. It runs alongside your event app — or standalone, if you don’t have one. Complementary, not competing.

No — keep them. Aikebom is a companion layer, not a migration: your app keeps doing registration, badges and the agenda, and Aikebom adds the layer that knows your programme, venue and live changes — and plans the whole visit around them: the trip, the city, voice, six languages and your sponsor layer. Your programme imports from the tools you already run, so nothing gets ripped out. And if you don’t have an app at all, Aikebom is the whole attendee-facing layer on its own.

No — by design. Aikebom is not a ticketing or registration platform; yours keeps doing that. In companion mode the concierge points attendees to your official channels for tickets and registration, and handles the rest itself — your programme and venue, live updates, the whole stay, the city and your sponsors.

Every venue, address and opening hour is verified against live data at the moment it’s recommended. The agent is instructed never to invent a place or complete an address it can’t confirm — grounding is a hard rule, not a hope.

Sessions are anonymous — no attendee or guest accounts. Voice runs with zero retention. What happens next depends on the product: an event has one published cut-off date, after which all attendee data is purged automatically. A property never ends, so each guest’s data deletes on its own clock instead — about a week after they stop using the concierge, and never more than 45 days after their last message. Anonymised analytics survive both. Either way it’s us who enforce it, not a setting an organiser can quietly widen — that’s part of the commitment. Privacy is built into the schema, not bolted on.

Weeks, not months — and the platform itself deploys in days; loading your content well is what takes the rest. We build your city knowledge base and brand the concierge; you manage sponsors and partners, announcements and stand QRs yourself from an admin panel. No engineering on your side.

English, Portuguese, Spanish, French, German and Italian today — and the translation is agentic, meaning the whole conversation works in the attendee’s language, not just the buttons.

Yes — since July 2026 the concierge can live on WhatsApp. Guests message the property’s number and the same concierge answers there: grounded recommendations, staff-confirmed requests, and a personal day plan that arrives as a message with its share link — in the guest’s own language, switching the moment they do. Same engine and the same privacy limits as chat and voice; it’s switched on per property. Proactive messages — briefings, schedule alerts, post-stay follow-up — are next on the roadmap.

Yes. Colours, name and voice are yours, and each deployment can offer its own selectable guide personas. The concierge is unmistakably your event’s, not ours.

We set your event up for you and hand you a no-code admin panel to run it — most organisers prefer that for a first event. A self-serve setup flow is coming; white-glove is how you go live now.

Both — and they’re two products. Aikebom Concierge AI runs always-on for a hotel or resort: 24/7, all year, for every guest who checks in, sold as a subscription per property. Aikebom Events AI is scoped to one event — anchored on its programme and dates, then purged when it’s over, sold as a per-event license. Same engine underneath; what differs is duration, framing and how it’s priced. A hotel with meeting space typically runs both.

Within a conversation, yes: preferences mentioned once shape every suggestion after — no forms. Across the event, your dashboard shows what attendees actually ask, and every morning a digest flags what the concierge couldn’t answer, grouped by topic with a suggested fix. Fill the gap or publish an announcement and the very next answer improves — live, with no redeploy. And it learns for you, not from you: nothing your attendees teach it ever surfaces at another client’s event, and personal data is purged after your event.

Yes. Aikebom Concierge AI connects to your property-management system through a vendor-neutral webhook contract: your PMS — or your integrator — pushes bookings, check-ins, room moves and checkouts, and the concierge follows. A guest moved to a new room gets answers about the new room without telling anyone twice, and check-in can automatically hand each guest their personal concierge link. If your system can call a URL, it can talk to Aikebom.

Yes — upload the in-room guide, menus, spa brochures or appliance manuals, or point it at your official pages, and the concierge answers from them with the source attached: “per the in-room guide, page 12”. Your facts always outrank the open internet, and your live announcements outrank both.

Every property and event can already run its own MCP endpoint — a read-only, token-gated interface that a guest’s or attendee’s own AI can query for official facts, with partnerships disclosed. It serves official information only; no guest data is ever exposed. And since July 2026, hotel properties can go one step further: a checked-in guest gets a personal, stay-scoped connection, so their own AI answers “when is my spa booking?” from their actual reservation — personal, revocable, and it expires with the stay. Where the property switches it on, that connection can now act as well: the guest’s AI proposes a request to your staff or adds a stop to their plan — logged, attributed, and confirmed by your team before anything happens.