Otel AI

Otel connects to more than 100 hotel systems, including legacy ones and systems with no API, and sits above the existing stack with nothing to rip out and nothing to migrate. An Integrations surface sits in the product navigation, and data from third party hotel management systems flows into the platform. It acts as well as reads.

At the O'Callaghan Collection, one Flow carries out roughly 120 rate actions a month, and in the cross-department example agents create an operations task, route a labor exception for sign off and draft a review response, each with the customer's approval before anything goes live. Otel publishes no connector catalog of its own, so systems such as Opera, Guestline, IDeaS, Duetto, Lighthouse and STR are not listed there.

SourceOtel AI, otelai.com home and the O'Callaghan Collection case studyread 2026-09-08

Flows are recurring jobs built once and run automatically across departments.

The cross-department check runs distinct revenue, payroll and guest agents in sequence, each with its own elapsed time, and each produces an outcome and a handoff, creating an operations task, flagging a group block to a named colleague, routing a labor overage for sign off, briefing the front desk and drafting a review response.

Several agents run multi step work under a named runtime, and the handoffs happen without a person moving the work along. There is no workflow designer or branching surface, and customers describe their Flows in plain English.

SourceOtel AI, otelai.com homeread 2026-09-08

A maintained structure sits over the hotel's own operations. Otel reads years of the hotel's own trading history on the first night and keeps every snapshot after.

It encodes the property's context, such as rates, segments, comp set and the renovation that breaks the comparison, reads every connected system as one hotel, and answers questions across revenue, payroll, guest and ops from that layer, with every number traceable to the source system. The platform has a Library surface, and commercial and market data are ingested into it.

This structure persists, is maintained and can be queried, and it outlives any single run. Otel does not describe how it indexes, embeds or retrieves that material.

SourceOtel AI, otelai.com homeread 2026-09-08

A person approves each action before it runs. The work happens on top of the stack with the team approving each action. Rate moves are drafted with the working shown and wait for the user's yes, and nothing goes live without it. Exceptions are routed to named people for sign off, and the privacy statement commits that the platform makes no automated decisions with legal or similarly significant effect and that all decisions of material significance get meaningful human oversight and intervention.

SourceOtel AI, otelai.com home and otelai.com/privacy-policy section 5.2read 2026-09-08

Otel holds an ISO 27001 certification and names an access model. Its security section carries the ISO 27001 seal, the international standard for information security management, alongside GDPR. The platform's access model covers login credentials and authentication data, user access permissions and roles within the platform, session tokens, and system activity logs tied to the account. Otel also runs a Trust Center at trust.otelai.com. SOC 2 Type II is still in its observation period, and no auditor, report or certificate date is published for the ISO certification.

SourceOtel AI, otelai.com home and otelai.com/privacy-policy section 1.4, trust subdomain probed and refusedread 2026-09-08

Otel says nothing is a black box, every answer shows its working, and every number traces back to the system it came from. The cross-department run shows what each agent read, what it concluded, how long it took and who it routed the item to, and a Confidence surface sits in the product navigation alongside the working shown on each recommendation. So Otel itself keeps a record of what the agent did and why, instead of inheriting audit from the systems it reads. There is no retention period, export or log query surface, so the trace is what the product displays, not a described audit store.

SourceOtel AI, otelai.com homeread 2026-09-08

A Memory surface appears in the product's navigation, but nothing says what it holds. The persistent trading history and encoded property context are a customer data store that grounds the agents, not agent memory. The Memory surface has no stated scope, whether per user, per property or per workflow, and no stated lifetime, and the privacy statement's retention section covers personal data duties, not agent state.

SourceOtel AI, otelai.com homeread 2026-09-08

Data sits in one named region, and there is nothing for a customer to choose. Otel hosts the platform itself on AWS in eu-west-1, Ireland, its primary hosting environment, and all personal data is stored within the EEA, with SCCs where third party processors sit outside it. There is no region list, customer environment option or selection, and data does not stay in the client's own environment.

SourceOtel AI, otelai.com/privacy-policy sections 3 and 4read 2026-09-08

Agents ship, but there is no catalog to choose from. A cross-department check runs distinct revenue, payroll and guest agents as shipped units, a Library surface sits in the product navigation, and customers define Flows in plain English and build them once. There is no template or agent library, agents the customer describes and creates are a builder, not a pack, and the four audience sections, Owners, General Managers, Revenue and Finance, are personas, not units to select.

SourceOtel AI, otelai.com homeread 2026-09-08

Work starts from events and schedules, not only from people. Agents watch while the team sleeps and speak only when something needs a person. Comp set moves are caught overnight, a Flow reviews the forward calendar overnight and produces roughly 120 rate actions a month at the named customer, recurring reports and control checks run on a schedule and arrive before the team sits down, and a cross-department check raises items by exception and routes each to a named person. Delivery goes to the product inbox and the surfaces in the product, and there is no webhook or outside channel.

SourceOtel AI, otelai.com home and the O'Callaghan Collection case studyread 2026-09-08

Two named model providers run the platform, and Otel chooses them. OpenAI and Anthropic supply the large language models used within the platform, on enterprise terms with zero data retention. Customers and admins cannot select a model. The chat header in the product screenshot shows a model label, which suggests a selector, but none is described. AWS, on the same subprocessor list, is infrastructure, not a model.

SourceOtel AI, otelai.com/privacy-policy section 3 and section 5.3read 2026-09-08

Outside callers have no interface to drive this platform. There is no API reference, SDK, developer portal or MCP server, and the site links no docs or developer subdomain. The only subdomains exposed are the Trust Center and a recruitment form. The Integrations surface and the more than 100 connected systems run the other way, with the platform reaching into the hotel's stack.

SourceOtel AI, otelai.com estate, probe recordedread 2026-09-08

Agent behavior is not evaluated. The Confidence surface in the navigation and the confidence label beside an answer are signals on a single response, not a gate on a change. Agents checking each other's work is a cross check inside a run, and the customer results quoted, RevPAR, hours saved and output multiples, are outcome marketing about the hotel, not measurement of the agent. There is no deployment validation surface either.

SourceOtel AI, otelai.com homeread 2026-09-08

The platform reaches the hotel's systems through integrations and data sync, sitting above the stack instead of driving anyone's interface, and there is no browser, desktop or remote computer control.

SourceOtel AI, otelai.com homeread 2026-09-08