Mr.GG: today and the concept Contents

Hostify

Mr.GG: what it does today and what it could become

The guest product as it exists, from its code, and the concept of the same product built around a conversation with an AI agent. The first half is fact; the second is ideas, and nothing in it is decided.

November 2026

Laid out for A4 as well: Print, "Save as PDF", paper A4, background graphics on.

1 Mr.GG today

Status: 2026-11-16. Owner: CTO. One document for the team that works on the new version.

It has two halves. Part 1 describes the product as it exists, from reading its code. Parts 2 to 6 describe a concept: the same product built around a conversation with an AI agent. The first half is fact, within the limits stated in 1.13. The second half is ideas; nothing in it is decided and nothing in it binds a build.

Every conversation in this document is an illustration written for it. The property, the manager and the guests are invented.

1.1 What it is

Mr.GG is the guest side of Hostify. Each reservation has one link. Through it the travellers register, sign and pay what the listing requires before they arrive, then receive their entry instructions and the guide to the home, talk to the host, buy extras, report damage and check out.

It is a separate service today: a server and a web app for guests, fed by the legacy PMS, where the manager configures everything.

WhoHoldsCan do
Link holderThe reservation link, nothing elseOpen the hub, fill any unfinished guest place, read the guide. The link is the permission
Guest with a placeA place they filledEdit it until it is completed; sign their own declaration
Main guestThe first guest to completeIs the registered lead of the booking
Signed-in accountAn optional account (Google, Apple, email link)Save stays and see them later. An account is never linked to a reservation automatically
Property managerThe PMSConfigure through templates assigned to listings; see results; act on a reservation
SupportA staff consoleReopen, correct, merge, undo, open entry instructions, each with an audit entry
AI guest agentThe PMS inboxAnswers guests in the channel thread; reads Mr.GG's content through the PMS

1.2 How the manager sets it up

Every feature is a template assigned to listings, one per listing per category.

Template or listWhat the manager defines
Online check-inHow many guests must register (main guest only, all adults, all guests, all including infants); the adult legal age; whether a copy of the document is required; which document types are accepted, by country scope; for each field, shown or not and mandatory or not; a compliance preset (for example the Spanish one) that locks the fields the law requires
Rental agreementThe text with placeholders filled from the reservation; for which booking channels it applies; languages
DepositCharge or hold; for which channels; the terms text; optionally a non-refundable waiver fee or an insurance partner instead of a deposit. The amount is the reservation's own deposit
Entry instructionsRich text or steps with photographs; when they unlock
House manual, directions, emergencyRich text; Wi-Fi and house rules are pulled from Hostify
Area guidePlaces near the property
Check-out tasksA list the guest ticks
UpsellsHostify fees enriched with photographs, translated titles and a condition (paid at once, or "on request"); partner upsells
Quick access badgesShort values shown on the hub: a custom field, a text, a smart-lock code, an action

Account-wide settings are few: the supported languages, the payment processor for deposits and for upsells, and the guest chat switch.

The guest link exists when the integration is active, the reservation has an identifier and is not cancelled. The manager sees it on the reservation, and automated messages carry it through placeholders.

1.3 The guest's journey

There is no linear wizard and no Submit button. The hub shows a checklist, and the server sends the check-in to the PMS when the last required item is in.

  1. Open the link. The reservation is read from the PMS and a link session starts. No guest record is created by opening.
  2. Stay details: arrival and departure time. Always shown, never required for completion.
  3. Guests. Each required traveller has a place. Whoever holds the link can fill any unfinished place, so one person can register the family. For each guest:
    • Document: scan with the camera, upload photographs, or type the details. A passport has one side, an identity card two. The reading of the document and the check that the image is a document are advisory and block nothing. A child may be declared to have no document.
    • Guest information: the fields the template and the compliance scheme ask for.
    • Contact: email and phone, for adults.
    • Declaration and signature, under the schemes that require one.
  4. Rental agreement, if the reservation has one: read, choose who signs when there are several adults, sign.
  5. Deposit, if required: a card hold or charge, or the waiver.
  6. Additional information: the manager's own questions.
  7. Invoice details, optional.
  8. Completion. When every gate is satisfied the check-in is submitted to the PMS once. A success screen follows. It shows no door code.
  9. Entry instructions unlock by the listing's rule.
  10. During the stay: the guide, chat, extras, damage reports.
  11. Check-out: tasks, confirmation, a review. The guest's profile is purged 30 days after the last stay, by rule.

The catalogue has 91 possible fields. Most are conditional. An adult under the Spanish scheme fills 16 to 19.

1.4 Registration rules by country

SchemeWhat it adds
Spain (SES Hospedajes)A fixed set of fields per traveller, including the support number of a Spanish identity card and the relation of a minor to the adult; a traveller declaration that every guest of the declaration age (14 by default) signs personally
RomaniaA registration form with its own fields and a personal signature
PortugalAdditional fields; no declaration flow
BulgariaAdditional fields, including the personal number; no declaration flow
ColombiaAccepted as a field set; no declaration flow; in doubt whether any property uses it

Mr.GG collects and signs. Reporting to the authorities is done by the PMS.

1.5 Money

Only three things take money: the deposit, the deposit waiver and extras. There is no payment of the reservation balance, of city or tourist tax, or of guest and pet fees.

  • Payment runs on the manager's own connected payment account, through a hosted checkout.
  • A deposit is a hold only when the manager chose "authorize"; otherwise it is charged. The waiver and extras are charged at once.
  • Capture, release and refund of a deposit are done in the PMS. The guest sees "authorized" and nothing after it.
  • The amount and the currency come from the server and the payment processor, never from the browser.
  • An extra offered "on request" is never charged; the guest is told the host must approve.
  • A deposit paid outside Mr.GG is mirrored so the requirement counts as settled.

1.6 Entry instructions and access

Entry instructions are the one part of the guide that is locked. They open by the listing's rule: a number of hours before arrival (24 by default), at completion of check-in, at a scheduled time, or when Support opens them. Until then they are removed from what the guest's device receives, not merely hidden. They are withheld again for cancelled and past stays.

Everything else in the guide is open to anyone with the link.

1.7 The guide and the stay

The hub shows tiles: Directions, Entry instructions, Wi-Fi (with a code to scan), House manual, Extra service, Area guide (places with a category filter), Check-out, Emergency instructions, Report damage, Chat.

  • Chat has one store: the PMS inbox. A message the guest writes in Mr.GG lands in the same thread the booking channels and the AI guest agent use.
  • Damage report: a photograph and a description.
  • Check-out: the manager's tasks, a confirmation, then a review of the stay.
  • Past stays become a read-only record.
  • Languages: 34 in the app. The guest picks the language; the manager's texts fall back to the original when a translation is missing.
  • Themes: a private-label theme changes colours, logo, name and background. There are no custom domains, and the manager has no screen to edit a theme.

1.8 Notifications

Event-driven: a new chat message (in the app and as a push); the guest has checked in; a check-in was reset. Emails: payment receipts, the invitation of a guest, the check-in summary with the signed agreement, a request to correct details.

Scheduled reminders run on fixed hours and catch up on missed days: check-in reminders at seven days, 48 hours and 24 hours before arrival, by email and push, to every adult and not only the main guest; then access instructions available, an offer of extras, the check-out reminder and an invitation to review.

1.9 What the manager sees and can do

  • On the reservation: the registered guests, their documents, the signed agreement, arrival time, payment status, and the status of the submission.
  • An Arrivals and Departures board with export, piloted for some accounts.
  • Actions on a reservation: view as the guest, open entry instructions early, reset the check-in, edit or delete a guest, replace an expired link.
  • Support has a console of its own with the same actions plus merge of duplicate guests and undo, with masking of personal data and an audit trail.

1.10 How it is connected

  • PMS. The guest service reads reservations and listing settings from the PMS and writes guests, the completed check-in, payments and chat messages back. It listens for four kinds of change from the PMS: a listing changed, a reservation changed, a reservation moved, a new message. There are six regional PMS installations; reads try all of them, writes go to the reservation's own.
  • Outside services: the payment processor, document reading, an image check, push and email delivery, a places directory, lock providers.
  • The AI guest agent never calls Mr.GG. It learns the house manual, entry instructions, directions, area guide and check-out tasks through the PMS, and whether a check-in form is active. It does not see who has registered, what was signed or bought, or whether entry instructions are open. It and Mr.GG both write four fields of the reservation (planned arrival, planned departure, the checked-in and checked-out marks) with no rule about who wins.

1.11 The rules that hold it together

These have each cost a correction in production. They are the part of today's product that any new version must keep, whatever its surface.

  1. Unknown is not "not required". A requirement (agreement, deposit) starts unknown and blocks completion until the PMS has answered.
  2. There is no check-in status field. State is derived from places completed, corrections open, requirements, signatures, payment and submission.
  3. Readiness is an ordered list of gates, first failure wins: open corrections and missing documents; required guests; unknown requirements; mandatory additional information; the agreement signature; the deposit; declarations. Stay details is never a gate.
  4. "Submitted" is set only when the PMS accepted and cleared only by an explicit undo.
  5. Opening a link never creates a guest. An unfinished place is edited by whoever holds the link; a completed place is frozen until Support reopens it.
  6. No online check-in template means nothing is ever submitted, even with the agreement signed and the deposit paid.
  7. "Nothing due" is not "paid". A booking with no deposit amount requires no deposit; a zero amount never settles a requirement; a waiver never stands alone.
  8. Amounts and currency come from the server and the processor.
  9. An extra "on request" is never charged.
  10. Entry instructions are withheld from the device until the unlock rule is met.
  11. Reminders are de-duplicated per reservation and go to every adult.
  12. Chat has one store, the PMS inbox.

1.12 What it does not do

The marketing site and the help centre describe more than the code does.

  • No payment of the balance, of tourist tax or of fees.
  • No selfie, face match or liveness check.
  • No "check-in opens on" date. The link works from the moment it exists.
  • No reporting to municipalities from Mr.GG itself.
  • No release or refund of a deposit shown to the guest.
  • The help centre calls "Report damage" and "Contact host" not yet implemented. Both work.

1.13 Where the detail is, and how far to trust it

The full harvest is in this folder: four parts with 986 behaviour rows, each with an acceptance wording, a pointer into the code and a class (requirement, workaround, bug, accident, dead), plus data, endpoints, edge cases, 200 "not carried over" rows, 125 open questions and parity checklists.

FileScope
part-1-guest-journey.mdAccess, places, documents, declarations, schemes, agreement, finalization, unlock, retention
part-2-money-comms-platform.mdDeposit, extras, chat, notifications, guide content, support console, the PMS contract
part-3-guest-experience.mdEvery screen and state, the field catalogue, the 98 moments in which a guest gives or receives something
part-4-manager-side.mdTemplates, settings, results, reservation actions, the Arrivals board
annex-ai-agent-touchpoints.mdWhat the AI guest agent reads and writes of Mr.GG today

Everything in Part 1 comes from reading code; nothing was run against a live system. About a hundred rows in the parts are marked unverified, mostly the document step, declarations, accounts and the support console. The manager side was read partly from outlines. The Facelift PMS already contains a port of the manager side that trails the legacy product by about fifteen features added since May 2026.

2 The concept

2.1 The idea

Mr.GG would become one conversation with an AI agent. The manager talks to it about a property and it learns the property. The guest talks to it about a stay and it gets them through the door. When a step needs something a sentence cannot carry, such as a signature, a payment or a photograph of a passport, the agent puts a small widget into the conversation, and the conversation goes on when the widget is done.

There would be no forms to fill and no templates to build. There would be a memory of each property, a small set of rules the manager has agreed to, and an agent that works from both.

2.2 Why

Today both sides do the software's work for it. The manager fills about a dozen kinds of template and list, assigns each to listings, and translates the texts. All of that structure exists because a form needs to know in advance what will be asked. The guest gets a checklist and up to 91 possible fields, then searches tiles for the Wi-Fi password.

An agent needs neither. It needs to know the home, and to know what the manager and the law require. Knowing a home is better done by looking and asking than by filling a template, and helping a guest is better done by answering than by presenting tiles.

2.3 Three layers

LayerWhat it isWho writes itMay the agent be wrong?
KnowledgeA wiki of the property: how things work, where things are, what is nearby. Every fact has a source and a date. Inherited from account to building to apartmentThe agent, from conversation, photographs, manuals, reviews and past guest questionsSometimes, and it must know it. Facts about use and the area go live marked unconfirmed and are withdrawn at the first contradiction. Facts about safety, access, money and rules wait for the manager's confirmation
PolicyDeposit, accepted documents, registration scheme, agreement text, what may be sold and for how muchThe manager, by talking; the agent stores it as rules and shows it backNo. A rule is confirmed before it applies
StateWho registered, what is signed and paid, whether the check-in was accepted, whether access is openThe system: the gates of 1.11No. The agent reports state, it never judges it

Door codes are not in the knowledge the agent reads. A rule releases them into the conversation when the stay is ready and the time has come. The agent can ask for the release and cannot be talked into it.

2.4 The widgets

  • Document: photograph or scan an identity document. The image goes to the system and never sits in the thread.
  • Signature: read a text and sign it.
  • Payment: a hold or a charge, on a hosted payment form.
  • Summary: what the agent has gathered, for the guest or the manager to check and confirm.
  • Access: the code, the lock button, the Wi-Fi, shown when released.
  • Photo: send a picture of damage, or of an appliance.
  • Progress: what is done, what is left, each line a way in. A guest who does not want to talk completes everything from here.

Everything else is text and quick buttons. The same widget would appear inline in our own chat, as an in-thread form in a messaging app that supports them, and as the chat itself opened at that step from a channel thread that carries only text.

2.5 One agent, three roles

The manager, the guest and the cleaner would talk to the same agent over the same knowledge, each in a role with its own tools and its own view of the data, enforced by the system and not by instructions. A guest never sees the manager's notes or costs. A cleaner sees tasks and the knowledge of the home, not the guests' personal data.

3 Conversations

Illustrations. Elena manages six apartments in one building in Valencia, "Casa Olivo". The Ivanov family (Maria, Georgi, their daughter Ani, six, and Maria's nephew Niki, fifteen) stay in apartment 4 from 14 to 18 July. Lines in (italics) are widgets or photographs.

3.1 The manager

A new property, starting from what is already known

Teaching the home by photographing it

One answer, six apartments, one exception

Setting a rule

What must guests do before arrival

The digest

Asking about tomorrow

Selling something

3.2 The guest

First contact

Reading instead of asking

A family, and a teenager who must sign himself

A document the system cannot read

The deposit

The guest who does not want to chat

Asking for the code too early

Someone else asks for the code

Trying to talk the agent out of its rules

An early flight

During the stay

Something the agent does not know

Something breaks

A complaint goes to a person

Check-out

3.3 The cleaner

3.4 Three things to notice in these conversations

  • The agent reads and confirms instead of asking. Nobody answers 16 questions.
  • The agent says where things stand from the system: "three of four", "300 EUR held", "the code goes out at 15:00". It never infers state from the chat.
  • The agent says no in three ways: "I do not know" (knowledge is missing, so it asks the manager), "that is Elena's decision" (a person decides), and "I cannot" (a rule decides, and it does not hold the secret).

4 From today's product to the concept

What would happen to each piece of today's Mr.GG.

TodayIn the concept
Content templates: house manual, directions, emergency, check-out tasksKnowledge. Existing texts are read in; no template is edited again
Translations of each textNot needed; the agent answers in the guest's language. Legal texts keep fixed translations
Assignment of templates to listingsInheritance: account, building, apartment
Area guideKnowledge: the manager's own picks, filled out from map and review services
Online check-in template, field by fieldPolicy: the registration scheme and what the manager additionally wants. The agent reads the document and asks only for what is missing
Rental agreement templatePolicy: a fixed text, signed in the signature widget
Deposit templatePolicy: set in conversation, shown back, confirmed
UpsellsPolicy for price and condition; offered in conversation when they fit
Quick access badgesDisappear; the guest asks
The hub and its checklistThe progress widget
The per-guest wizardDocument widget, summary widget, signature widget
The tilesThe conversation
Entry instructions and their lockKnowledge for the instructions; the access widget and the release rule for codes
Reminders on a scheduleThe agent's own nudges, driven by what is still missing
Chat with the hostThe same conversation; a person joins when the agent hands over
Damage report formA photograph in the conversation
The readiness gates, places, requirement states, submissionUnchanged. This is the core the conversation stands on
Support actions (reopen, correct, undo)Unchanged, as actions of the manager's and staff's role
The rules of 1.11Unchanged

5 What stays hard

A concept that hides its difficulties is an advertisement. These are real. The fuller analysis, with sources, is conversational.md.

The law decides some steps.

StepWhy it cannot be a plain chat messageWhat it becomes
Identity documentData protection authorities object to documents sent through messaging apps: the photo stays on the phone, in backups and at the platform, and cannot be deletedThe document widget, which sends the image to the system and leaves nothing in the thread
Registration signatureSpain asks everyone over 14 to sign; Portugal says "signed personally". Whether a typed "I agree" is enough was not foundA drawn signature, until a lawyer says otherwise
Identification in ItalyThe law requires real-time identification of the person against the documentA live video step or a person. No form or chat solves it
PaymentCard details typed into a thread bring the whole channel under card-security rules; bank authentication appliesA hosted payment form. Later extras can be charged on a "yes" once a card is on file
Door codeA model can be argued withA release rule outside the model

The channels decide others.

ChannelWhat the conversation can carry
Our own chatEverything, with widgets inline
A messaging app with in-thread formsText, buttons, and the widgets as forms; payment by link
Airbnb threadText and images only. From bookings of 20 November 2026 a host may not collect contact details, identity documents or financial data except where a law requires it and the house rules say so; separate agreements and deposits are limited. This reaches today's product as much as the concept
Booking.com messagesText and images; links only if allow-listed; the guest's phone number is no longer passed on

And the rest.

  • The guest must be told it is an AI, at the first message; this has been law in the EU since 2 August 2026. Today's guest agent is instructed never to confirm it.
  • The agent's word binds the manager. That is why state and rules are not the agent's to judge.
  • Photographs can be misread. That is why an unconfirmed fact is marked, and why a contradiction withdraws it.
  • Conversation is not faster by nature. People prefer a button to typing. The product is judged on minutes to finish, not on how much was said.
  • It costs money per guest, where a checklist costs none.
  • Map and review services set terms for storing and showing their content. Those terms have not been read yet.
  • No vendor does this. Every competitor found uses chat to invite and remind, then sends the guest to a web form. There is no one to copy and no evidence yet that it is better.

6 What is open

  1. Where it is built: the Facelift PMS, which already holds the manager side, or a new repository.
  2. Whether the hub and the template editors are rebuilt at all, or only the core, the chat and the widgets. The proposal on record is the second.
  3. Which channel comes first: our own chat, or the messaging app where guests already are.
  4. Whether the agent may start the conversation and nudge. Today it may not mention check-in unless asked.
  5. How the disclosure is worded, and who confirms the legal reading.
  6. Who confirms a fact the agent learned: the proposal is confirmation by risk, with a weekly digest.
  7. Whether a typed "I agree" is accepted for the rental agreement.
  8. How much the agent may charge on a "yes" without a person.
  9. Who owns the arrival time and the arrived and departed marks: the guest's statement, the agent's inference, or the manager.
  10. Scope of money: stay with deposit, waiver and extras, or add the balance and tourist tax.
  11. Which registration schemes ship first.
  12. How we would know it works: the share of stays fully prepared before arrival; the minutes a guest spends; the minutes a manager spends making a property ready; the questions that still reach a person.