How it works

Three agents do the work. Your Workspace decides what they may do. A verified library tells them how. Nothing they say to a guest comes from a guess.

Who sits where

The names are those of our own operation. Your business can give its agents its own names: the roles are the product.

Your Workspace governs every action they take

Your Workspace · your business's own layer

Settings and dataYour settings always come first; your properties, values and conflicts section
Business playbookYour own rules and values, applied to the verified templates you use
The ManagerRoles, permissions and access; holds check-in form data and door codes The KeymasterAdd-on: cards, banking and payment details and passwords, in an encrypted vault

Verified templates reach your business playbook · copilot cards go to the library

The library layer · how the work is done

MildredThe librarian: builds templates from copilot cards, with none of your data
The Aonios LibraryVerified templates: the structure of each job, never a business's values
Aonios authorsWrite and verify templates and monitor the agents

How an agent decides what to do

The order is always the same.

  1. Your settings come first, and you always win.

    If you change a step the library recommends, the agent warns you what could happen, you accept it with a click, and it is logged in your conflicts section.

  2. Otherwise the agent follows the verified template

    for that kind of job, filled in with your own values: your check-in time, your prices, your arrival contact.

  3. If a value is missing, your Manager asks you for it

    before the agent acts, with related questions grouped so a couple of minutes covers them.

  4. If nothing verified covers it, the agent asks before it acts.

    It tells the guest it will confirm, raises a copilot card, and waits for your answer. Your answer becomes part of your business playbook, so the same question never waits twice.

The one automatic override is an emergency: a lockout, fire, flood, crime or power loss. Help starts once the guest confirms it; for a fire, the local emergency number goes out at once.

Shared knowledge, private values

The library holds the structure of each job. Your names, addresses, times and prices stay in your Workspace.

A verified template

The steps of a job, the options each step offers and the names of the fields it needs, for example “check-in time”, with a default value where one is verified. Never a business’s own values.

Your choices

Picking an option, filling in a value, the wording of your messages. They live in your Workspace and never reach the library.

Something new

An option the template does not offer yet. Mildred turns it into a template with none of your data, and once verified every business can choose it.

An exception

Removing a step or overriding a recommendation. You always win; it is logged as an accepted conflict, so nobody forgets it was a choice.

Onboarding builds your business playbook

Your business playbook is one document, living only in your Workspace: your own rules and every value your agents use, applied to verified templates, with where each value came from and whether they may use it yet.

  1. Register,

    and give your agents your own names if you wish.

  2. Connect your property management system and booking channels.

    Marika reads your properties and their values.

  3. Set up your Manager:

    roles, who may confirm what, the emergency alert order, door codes and access details. Passwords and payment details go into the Keymaster, if you add it.

  4. Share your documents:

    house manuals, price lists, staff lists.

  5. Mildred drafts your business playbook

    from your systems, your documents and the library's defaults. Nothing is invented; prices never apply until you accept them.

  6. Review it, category by category,

    with Mildred: confirm, change or answer. One tap confirms a whole category.

  7. Your agents go live on it.

    Anything still waiting holds back only the actions that need it, and every later answer becomes a new dated version.

Who holds what

Sensitive data is protected by never being in the library at all.

InformationHeld byWho can reach it
Check-in form data (identity documents, personal details), door codes, key-safe codes, the Wi-Fi passwordThe ManagerOnly with permission, under the roles and access you set. Its assistant explains and prompts, and never grants access itself.
Credit cards, banking and payment information, passwordsThe KeymasterAn encrypted vault with its own permissions. Never written into the library or a copilot card.

How the library is kept true

Nothing becomes a rule because someone typed it. Every entry is proposed, verified, and recorded.

Your business playbook

You, or someone you authorise in the Manager, verify every rule and value in your business playbook.

The shared library

A template is verified by an Aonios author, or by twenty identity-verified people from at least three businesses with different owners, each approving it unchanged with their own values in place.

The signed log

Every verification, edition, door code release, accepted conflict and undo is written to an append-only log, so anyone can show which knowledge was in force, and when.

Read the white paper: Proof of Outcome

Start with Alexandros

Create your account in My Agent, connect your property management system, and unlock Marika or Keymaster whenever you need them.