It is the foundation every Alliants module runs on: one trusted profile for each guest, the brands and properties you operate, the systems you connect, and the people who sign in. It brings each guest's records together, matches duplicates, and keeps preferences and consent in one place.

Front office, guest relations, marketing and IT administrators. Messaging, Concierge, Contactless, Payments, Keys and Allin all read and write the same profile, so a preference captured at check-in is visible to every team, at every property, straight away.

No. It works alongside your Property Management System (PMS), keeping bookings, guest profiles and rooms in step. Check-in, check-out, arrival times and profile edits go back to the PMS, and staff can look up a live reservation or resync a single booking.

Guests update their contact details from the guest app, and the changes are written back to the PMS. Guests with linked profiles can see and act on all their bookings, including check-in, payments and stay extensions.

With a booking lookup, or with branded single sign-on through Microsoft Entra on your own sign-in domain, which you choose whether to switch on. Guests can also sign in with their loyalty or brand account where it is connected. Availability depends on your property; ask your Alliants contact.

Yes. Colours, themes, logos and custom fonts are set per brand and applied to guest-facing pages and messages. You can also choose to use guest links on your own domain and branded short links.

Profiles are matched on email, phone number and loyalty membership, and your brand can add name plus booking confirmation. Likely duplicates are ranked in a review queue with a suggested primary profile, and your team confirms each one.

It can be undone. Confirmed matches are linked rather than overwritten, so a wrong join is reversed without losing data. Fields a colleague has corrected are locked, so the next system sync does not overwrite them.

Contact details, memberships, room preferences, bookings, requests, conversations, consent and a change log, in one workspace with a quick view from anywhere in the app. Your brand defines its own preferences and questions, and accompanying guests arrive from the PMS as their own profiles.

Consent is held per channel (email, text message, WhatsApp and more) for your brand or a single property. It arrives from your PMS and dining platforms, staff can record consent given in person or by phone, and consent a guest gives directly outranks a later sync. Every outbound message is checked against it before it goes.

Yes. The platform has organisation, brand, property and department levels, and each brand's data is held in its own database. Modules and features are switched on per brand or property, and group administrators switch between their brands without separate logins.

Oracle OPERA Cloud, HotelKey, Shiji, Apaleo, Mews (switched on per property), StayNTouch, Infor HMS and iReckonu. Charges can be posted to the guest folio in OPERA Cloud and Shiji. If a write-back fails, staff see it with a retry, and integration health is visible for each property.

Yes. A GraphQL API, the same one every Alliants app uses, with a published Postman collection, plus REST endpoints for profiles, bookings, requests and locations. API keys are limited to the resources and actions each integration needs.

No. Core Platform is included with every Alliants brand. Optional features, such as matching rules and required profile fields, are set up for your brand or property during onboarding.

No. Staff use alliants.ai in any modern browser, and guests use a web app that opens from a link, with nothing to download.

Yes. Alliants is ISO 27001 certified. Security is built into the platform, from how staff sign in to how guest data is stored and erased.

On Amazon Web Services, in one regional deployment for your brand: Europe, the United States or Asia Pacific. Each brand has its own dedicated database, and data is encrypted in transit.

With your own single sign-on, so access follows the groups in your staff directory, or with passkeys and passwords that meet your brand's rules. Multi-factor authentication can be required for your brand, and access is removed as soon as a colleague is deactivated.

Yes. Roles are scoped to your brand, a property or a department, with separate permissions for sensitive guest details and exports. You can start from hospitality templates or set up your own roles.

When a guest asks to be erased, the request clears their data across related records, including conversations, and keeps a record of what was cleared without holding any guest details. Consent is held per channel and checked before any message is sent.

All of them: the Signature Bundle, Messaging Bundle, Seamless Bundle, Keys Bundle, and All-In Bundle. Talk to our team about which bundle fits your properties.

Talk to our team. We will show you the module running in a hotel like yours and talk through how it would fit your properties and systems.