• Revenue and ratesAsk for today's rates, the real availability for a date, advice on a price. The agent reads the property's own numbers and suggests the move, without opening a single panel.
• Bookings and availabilityCheck and change the bookings of the connected channels. One request in chat, and the agent works where it has to.
• Guests and messagesAnswer guests in any language. You dictate the sense of the message: the agent writes it, translates it and sends it in the right tone, always inside your rules.
• Operations and housekeepingCleaning, check-ins, tasks and reminders from the same chat. Report a fault, open a task, free a shift: all of it stays on the record.
• Write however comes naturallyText, a voice note, a photo of a fault, a guest's document, a short video. ArmoLink™ understands every format and acts on it.

Nothing to install beyond Telegram. Open the chat and start: it works from day one.

• Identity and voiceThe property's trading name, the assistant's name, the languages it must answer in, and the tone of voice you want: warm, formal, spare.
• Contacts and hoursEmail and phone for escalations, reception hours and the night window, the address where service notices should arrive. This is what lets the agent hand over at the right moment.
• Your booking systemA dedicated login to your account: it is how the agent reads bookings, availability and rates straight from the booking system. If you prefer, we walk you through creating the user.
• Channels with guestsThe property's WhatsApp Business number and confirmation that you have access to the profile behind it. WhatsApp is the main channel: guests write to the number and get an answer in seconds.

Three steps and nothing else: gather, send, go live.

• Rules are the behaviourHow it must behave: what it may do alone, what it must say, when it must call you. "You may sell breakfast at €8 per person." "If a guest asks for an invoice, collect the details and tell the team."
• Details are the factsThe true facts of each unit: the address, the hours, the Wi-Fi password, the codes. Filled in once, unit by unit. Rules and details are never mixed.
• One rule, one sentenceWrite as you would speak to a new colleague: one instruction at a time, in one sentence, with no nested "ifs". Two rules that contradict each other stop the agent harder than a rule that is missing.
• When the agent stopsEvery time it hands over, the ledger says why. Read those escalations: they are the exact list of the rules you are missing.

Rules and details are written in Controls, in two separate lists.

• The rule"Unread" is the agent's; "read" means somebody has taken it. The state of the message is the border that keeps the two hands on one conversation apart.
• Why it works this wayA guest never gets two different answers to the same message, one from the agent and one from a person. And control stays yours: you decide, message by message, what to leave to the agent.
• What actually happensIt is the number-one cause of "the agent is not answering". Simply opening the conversation, even for a glance, is enough: at that instant the booking system marks the messages read, and to the agent the message is no longer its own.
• What to doIf you want the agent to answer, set the message back to "unread" and leave it there. One gesture, one second.

The same rule holds on every channel that comes through the booking system.

• What the guest findsThe property's services, the house manual, the access codes, and opening the door when the unit has a connected lock.
• One address, your markThe organization has a single portal address. On it you put either a logo or a text, never both; with neither, the portal shows the trading name.
• Your rules hold here tooThe portal is not a shortcut: a request outside the stay, or held by one of your rules, stays held exactly as it would in chat.
• Everything stays writtenEvery session and every opening leaves a line: who asked, when, and how it ended. Switched off, the address stops answering guests.

It is configured in Controls, on the ArmoPortal™ tab.

• What a case carriesEverything: the reason, the message that raised it, the answer the agent had ready, the risk it scored, the guest, the booking and the whole conversation.
• Answering the guestYou answer from inside the case, on the same conversation. You can also silence the agent on that thread for a few hours if you would rather carry it to the end yourself.
• The resolution noteIt is required, and it is not paperwork: the agent learns from those lines. "Called the guest, the code was stale, updated it on the unit" becomes one more rule; an empty note teaches nothing.
• Filing itPriority, class and risk type are written by hand, in your words. They are how you filter the queue and how we learn where the agent stops most often.

This week's handoffs are the list of rules you are missing.

• Where to open oneSettings → Reports → New report. Pick the category (bug, problem, idea), write the subject in one line and the rest underneath.
• What to writeWhat you were doing, what you expected and what happened instead. If it is about a conversation or a booking, paste the number: it takes us exactly where it happened.
• What happens nextThe ticket takes a state and a priority. You see both on the same page, together with what we answer: no reply gets lost in an inbox.
• When an email is the right doorFor the plan, an invoice or a commercial question there is the support button on the Subscription page: that writes to the team directly, it does not open a ticket.

A ticket written well closes in a day; one written in a hurry comes back asking.

• How to inviteSettings → Organization → New member. Name, email and role; the person gets the invitation and chooses their own password.
• ViewerReads everything the product shows — conversations, handoffs, figures — and changes nothing. The right role for whoever has to understand, not decide.
• ManagerThe operational role: writes rules, changes automations, manages units and closes handoffs. Does not touch integration credentials or the subscription.
• Admin and ownerAn admin adds credentials and integrations to all of that. The owner is the only one who touches the subscription and the payments: one per organization, and the one who answers for the invoice.

Changing someone's role tells you, before you save, what they will start and stop being able to do.

• Plan and extraThe plan credits your account at every renewal. If those run out first, the extra ones are spent: packs you buy when you need them, which stay on the account until they are used.
• Where to read themOn the Overview: how many the period consumed, what one decision costs on average, what those credits are worth in euro at your price, and how many are left.
• When they are running lowUnder a threshold the notice appears at the top of the product. You can turn on auto top-up under Subscription: when the balance drops, the pack you chose buys itself.
• If they actually run outThe agent stops answering guests: not badly — not at all. That is the guard that prevents a bill nobody authorised, and it is undone by topping up.

A tidy organization spends less: rules written well shorten every piece of reasoning.