Five questions per person.
Each staff member receives daily prompts for their role, setting and current stay. Staff answer through ordinary service and observation. Guests do not receive another questionnaire.
GuestMemoryOS gives the people serving your guests a simple way to capture what they learn. It connects that evidence to better service today, a prepared return anywhere in your participating group, and more relevant invitations between visits.

Read the argument, evidence and trial decision → · Explore the guest memory library
Technology helps the people delivering hospitality. Five daily prompts focus their attention; a separate QuickNote captures anything else worth remembering.
Each staff member receives daily prompts for their role, setting and current stay. Staff answer through ordinary service and observation. Guests do not receive another questionnaire.
Staff speak or type a QuickNote while the detail is fresh. Additional observations are unlimited. The system asks for useful missing detail in the staff member’s language.
Managers see the combined answers. Departments receive relevant briefs and recommendations. Staff decide how to serve, then record the guest’s response.
AFG reports an average of six seconds per QuickNote: about two minutes of entry for 20 notes. This is note-entry time, not the total daily workload. Read the staff adoption evidence →
“Could we have gluten-free bread?” records a request for the party. It may never identify which guest needs it. That missing detail changes the service.
A booking message can contain useful facts. If it does not say who the request concerns, the person’s identity remains unknown.
The team checks who the request is for and records the stated reason and context. The relevant department can prepare for that individual, while following its dietary and allergy procedures.
Illustrative example. AI can extract facts already present in messages; it cannot establish a missing identity from an ambiguous message alone. A dietary request is not automatically an allergy.
Why the capture method matters →Prepare using available guest-shared and booking context. Keep learning as the stay develops. Use the resulting evidence in the next interaction.
Available arrival plans and appropriate previous memories help the team prepare. New guests benefit from what staff learn during their first stay.
Food and beverage, chefs, housekeeping and guest services receive suggestions based on recorded requests, observations and feedback.
Stay evaluation and curated memories support the next welcome. Managers can review the service history behind compliments and concerns.
At the next check-in, your team builds on the last stay. The guest can return to the same hotel, visit another participating property or board another ship in your group without the relationship starting from zero.
Staff capture requests, preferences and responses during service. Useful memories retain the individual guest, source and context after departure.
The receiving team prepares with relevant memories before arrival. It checks what has changed and adds new learning throughout the stay.
Participating properties and ships contribute to an evolving guest history. Managers can also use recorded service examples to coach other teams.
Use what the guest actually enjoyed to shape a seasonal greeting, anniversary invitation or return offer. Recall a meaningful experience and offer a relevant reason to enjoy it again.
GuestMemoryOS supplies the service context. Your team uses approved memories in its communications and campaigns, then measures responses and actual bookings.
Sharing follows the agreed group structure, guest identity and permissions. It can include participating brands or groups under common ownership where authorised. Current wishes guide service; sensitive needs are reconfirmed. Marketing uses appropriate preferences and communication permissions.
Explore continuity across your group →GuestMemoryOS helps teams collect and use guest knowledge. It can operate standalone, with PMS and CRM connections scoped around your systems.
The booking, room and stay details.
The customer relationship, campaigns and communications.
What was ordered and paid for.
Which guest, what matters and the service context — so the next colleague can build on what is already known.
Capture daily staff answers and additional observations. Keep the guest, source and context attached. Prepare department briefs, suggest better service and retain useful knowledge for the next visit.
It is not a PMS or CRM replacement, a Wi-Fi browsing tracker or a questionnaire guests must fill in. Suggestions and rebooking estimates are not guest statements. Your team remains responsible for service decisions.
Existing PMS and CRM platforms can already hold preferences. The added value to evaluate is the ongoing collection of service knowledge and how effectively people use it. Integrations and cross-property use require agreed scope and permissions.
Standalone and integration options →A competitor can offer the same facilities. Your opportunity is to build a service relationship that grows with each interaction.
The next colleague can pick up the context. Staff can address feedback while the guest is still there.
Relevant knowledge survives absences and staff changes. Managers gain real service examples for coaching.
Use the trial to assess recognition, guest response and service consistency. Follow actual repeat bookings over time.
These are benefits to evaluate in your operation, not a promise of revenue uplift or five-star ratings.
Choose one team and a defined guest group. Agree the baseline, measure what reaches the next shift and review what guests experience. Start with a 30-minute product and trial discussion.
Our separate website and operations package for OTA hosts and rental agencies: a custom direct-booking website, connected OTA calendars, CRM, payments, daily operations and retained guest memory. Hotel groups and cruise lines use the separate Corporate GuestMemoryOS offering.
Read how AFG’s reported experience of repeated failures during live development shaped the GuestMemoryOS approach—and why identity, context, corrections and service follow-through matter.
Why AI alone is not guest memory →