AI agent skills & SOP automation for hospitality

Everyone follows the house rules. Including the software.

Every property has rules. Some are in a binder, most are in the head of whoever has been there longest. In ApexOS, skills are what your agents can do. You decide which are on, which need your sign-off, and the house rules each one follows.

Check-in, with conditionsApex skill library

Animation: the Apex skill library. The operator opens Check in a reservation, which is financial and so always needs a person’s approval, sets a daily limit of 25, writes the house rule “Don’t check in before 3 PM unless housekeeping has marked the unit ready” and saves. The skill is used by the Arrival Readiness and Front Desk Helper agents.

SOP automation for hospitality operators

Consistency without supervision. Which is to say, without you.

The procedure nobody wrote down, running anyway.

Your check-in has rules somebody worked out over years. Write them as house rules on the skills they apply to, in plain language. Every agent using that skill follows them, whoever is on shift.

  • Runs the same whoever is on shift
  • Your words, not a flowchart
  • Outlives the person who worked it out

Animation over a photo of a maintenance technician at work: a house rule says lock and key problems go to Marco. A new task for a sticking front door lock arrives, and the Task Assignment agent assigns it to Marco, following the house rules.

Everyone works the way your best person works.

The gap between your strongest operator and your newest is mostly procedure. Apex agents search your knowledgebase of policies and SOPs before they recommend anything, so the new hire’s shift runs on the veteran’s playbook.

  • Agents read your SOPs first
  • Account-wide or per property
  • Train judgment, not button order

Animation over a photo of a housekeeper making a bed: before a VIP arrival, the Arrival Readiness agent searches the knowledgebase, finds the turnover SOP for VIP units, and flags that the unit’s inspection has not been logged.

Nobody can loosen the rules. Not even on a busy day.

Anything that messages a guest or moves money always waits for a person, in every mode. That part is fixed. Everything else you can tighten: require approval, raise the risk level, set a daily limit.

  • Guest-facing and financial: always asks
  • Tighten any skill, never loosen
  • Daily limits across every agent

Animation: a table of skills against the Watch, Assist and Autopilot modes. Checking a reservation in and texting a guest always need approval. Turning on Always require approval for Assign a task makes it ask in Autopilot too.

Changing the procedure takes a sentence.

Procedures change. A new policy, a new season, a lesson learned the hard way in August. Edit the house rules in plain language and every agent using that skill follows the new version.

  • No conditions to reverse engineer
  • One edit, every agent that uses it
  • See which agents use each skill

Animation: the house rule on Draft a text is changed from an 11 AM late checkout to 12 PM from June to August and saved. The three agents that use the skill light up.

AI agent skills & guardrail features

Everything your agents can do. Nothing you didn’t allow.

Every skill your agents can use, grouped by what it touches: reservations, guests, messages, operations, payments and accounting, revenue and reports. Each shows its risk at a glance, and each has a switch.

One library, every skill

How AI agent guardrails work in ApexOS

Agents do the work. You set the terms.

An agent decides when to act. A skill is what it can do. Your house rules and guardrails decide how.

See how Agents work
SOP automation & AI agent guardrail FAQs

Reasonable questions.

How do you automate a standard operating procedure?

In ApexOS, you hand it to the agents that carry it out. Put the procedure in your knowledgebase, add house rules in plain language to the skills it touches, and Apex agents follow both when they act. There is no flowchart to build, and anything guest-facing or financial still waits for a person.

What is a skill in ApexOS?

A skill is one action an Apex agent can take, such as checking a reservation in, drafting a text or searching your knowledgebase. Skills ship with ApexOS, grouped by what they touch, and your account decides which are on, what needs approval and the house rules each one follows.

Can we write our own skills?

No. Skills ship with ApexOS, so each one is tested and carries its own risk level and staff permission. What you write is the procedure: house rules on each skill, SOPs in the knowledgebase, and plain-language instructions for your own agents.

Who can change skill settings?

Whoever holds the permission to manage agents, which you give by role. Every setting can only tighten a skill, and anything guest-facing or financial always needs a person’s approval regardless.

Does this replace training our staff?

It changes what training is for. Your team still needs to know your property, your guests and your standards. The order of the steps lives in ApexOS, so training can be about judgment instead of memory.

Book a demo

Your best manager took Tuesday off. The procedures didn’t.