Recurring pattern detected — HVAC noiseWorth investigating
Room 406 · Engineering · HVAC & temperature
9th related incident in the selected period
9 records — view
Recommend: root-cause review
Lexra Recovery
Service recovery, with the judgment left where it belongs.
When a guest's stay goes wrong, the next thirty minutes matter. Recovery captures what happened, assembles reviewed options for your property, and then stops — visibly — at the decision that belongs to a person.
The moment that matters
A service failure has been captured and reviewed guidance produced. What happens next is a person's decision, and the interface makes that unmistakable.
The Santa Monica Coastal Hotel
Product walkthrough
Sample property · illustrative scenario
- Log
- Guidance
- Approval
- Draft
- Brief
Case status · Awaiting Manager on Duty
In-room dining failure
Severity 2 · Service failureContext assembled from the case record and the property's reviewed operating content.
Reviewed guidance
Service credit
Example authority band · Band 2
Remove the delivery charge and the affected items from the check.
Authority bands are the property's own approval tiers. The higher the band, the more senior the approval a remedy needs. Lexra reads them; it does not set them.
Standard luxury template — Food & beverage recovery menu
Stopped for manager decision
Nothing proceeds until a manager approves, modifies or declines. No credit exists, and nothing has been said to the guest.
Deciding on
Service credit — remove the delivery charge and the affected items
Reviewed F&B recovery standard · Band 2
Approve
Modify
Decline
Awaiting Manager on Duty
Guest-facing draft
LockedPrepared for review only after a manager decides. It is never sent by Lexra.
Conditional preview · available only after manager approval
Leadership brief
LockedSummarizes what happened and what recurred, for the leaders who need the pattern. Assembled only after a decision is recorded.
Conditional preview · available only after manager approval
Stage 3 of 5, Approval. Case status: Awaiting Manager on Duty
Walk through a recovery workflow
See how Lexra assembles the context, prepares reviewed options, and stops at the decision that belongs to a manager.
The work gets done. The context gets lost.
Your team already handles recovery every shift. The difficulty is what happens around it: the context scatters across logs, messages and memory; the quality of the response depends on who is working; and by the time anyone reviews it, the reasoning is gone. Recovery is built for that layer.
Five steps, and one line the system will not cross
Every screen below is a simplified public walkthrough of the working workflow, demonstrated with fictional data.
-
Step 1: Log
A colleague records what happened in plain language, while the details are fresh. Lexra structures it — category, severity, department, location — so the case arrives at a manager already organized rather than as a paragraph in a group chat.
The Santa Monica Coastal Hotel Product walkthrough · Sample property · illustrative scenario In-room dining failure
The shift context becomes a structured record without a manager retyping it.
A structured issue record. Illustrative scenario on a sample property.
-
Step 2: Guidance
Lexra assembles the recovery options your property has actually reviewed — each with its source, its authority band, and whether it can be actioned now. This is where Atlas does its work: the options are specific to your standards rather than generic hospitality advice.
✓Options are reviewed content, not generated suggestions
The Santa Monica Coastal Hotel Product walkthrough · Sample property · illustrative scenario Reviewed guidance
Reviewed F&B recovery standard
Reviewed options with their source and authority band. Illustrative scenario on a sample property.
Lexra stops here
Everything above this line is preparation. Everything below it requires a named human to decide. There is no configuration that moves this line, and no tier in which Lexra decides on your behalf.
-
Step 3: Approval
A named manager approves, edits or declines. Until they do, nothing has happened: no gesture is owed, no credit exists, no guest has been told anything. The record shows who is deciding and what authority that role carries.
✓No automatic compensation. Ever.
The Santa Monica Coastal Hotel Product walkthrough · Sample property · illustrative scenario Stopped for manager decision
In-room dining failure · Food & Beverage
Nothing proceeds until a manager approves, modifies or declines. No credit exists, and nothing has been said to the guest.
ApproveModifyDeclineManager decision required. Illustrative scenario on a sample property.
-
Step 4: Draft
Only after a decision exists does Lexra prepare guest-facing wording, written as an offer and carrying a manager-review footer. There is no send control on this screen. A person reads it, edits it, and sends it themselves — or does not.
✓Lexra never contacts a guest
The Santa Monica Coastal Hotel Product walkthrough · Sample property · illustrative scenario Guest-facing draftLocked
Prepared for review only after a manager decides. It is never sent by Lexra.
Conditional preview · available only after manager approval
Prepared for review only. No send control. Illustrative scenario on a sample property.
-
Step 5: Brief
The approved decision, the reasoning behind it, and the follow-up are preserved as one record — and feed the next shift's brief. The point is not the archive. The point is that the next person inherits the reasoning instead of guessing at it.
No screenshot shown
This step has no certified capture in the current set, so none is shown. Lexra's own rule applies to its marketing: no invented product interface.
What happens when nobody has the authority
Most software's honest answer to an edge case is to let someone click through it anyway. This is the state we are most willing to be judged on.
Recovery options carry authority bands. The highest band requires a second approver. When no second approver is configured, Lexra does not fall back to the nearest available person and it does not quietly let the first manager proceed.
The approve, modify and decline controls are removed from the screen. The status reads "Stopped · outside escalation required." The record line reads "Stopped in Lexra · no decision recorded."
The escalation happens outside Lexra, between people, and Lexra does not claim it happened. It refuses to invent authority it does not have.
Required approver unavailable
Lexra removes the decision controls and records that no decision was made. It does not fall back to a lower authority, and it does not let the case proceed.
Stopped, not routed around. Illustrative scenario on a sample property.
A closed ticket isn't always a solved problem
✓Recovery Insights · In development · demonstrated with fictional data
Task systems tell you work was completed. They do not tell you that the same room generated nine engineering visits this quarter, or that a resolved issue keeps returning within the week. Insights reads the recovery records your team already creates and surfaces what recurs.
It is deliberately careful with language. It says "recurring pattern detected" and "worth investigating", based on the records in the selected period, and leaves the conclusion to the manager reading the evidence. It does not convert a correlation into a diagnosis.
Insights is not finished. It is shown here as a single static example so you can see the intent. There is no animated demonstration and no interactive version on this site, because the work behind it has not been reviewed and signed off.
In development · demonstrated with fictional data
What Recovery does not do
- It does not issue compensation, credits, upgrades or gestures.
- It does not contact a guest, in any channel, at any time.
- It does not tell a guest that anything is confirmed, arranged or resolved.
- It does not approve its own recommendations, and it cannot self-approve the highest tier.
- It does not diagnose a root cause. It shows the records and names the pattern.
- It does not read a live PMS. The current Alpha runs without integrations.
Walk one case end to end.
A founder-led session on a fictional property — log to brief, including the state where the system stops.
Request a Product DemoOr see how Atlas makes the guidance property-specific.