Private preview · Pilot cohort open
A guest asks for something on a terrace, in a lounge or in a private room. Too often nobody owns that moment: the guest does not know they were seen, the floor does not know who is going, and the manager hears about it afterwards. HALO gives every request an owner, a clock and a verified end, on a record the operation can audit.
The problem
Nothing in a busy service is neutral about time. The interval between a guest needing something and the operation finishing it is where reputation, recovery and revenue are decided, and in most venues that interval is invisible.
01
The guest
Asks twice, or stops asking. They never learn whether the first attempt registered, so they read silence as indifference.
02
The floor
Two people go, or nobody does. Without an owner, willingness is not the same thing as coverage.
03
The manager
Learns late, and only about the failures loud enough to reach them. There is no record of the ones that quietly resolved themselves.
04
The operator
Cannot tell a service problem from a staffing problem, because nothing counted the interval in the first place.
HALO's premise is simple and absolute: no request without an owner, a clock and a verified end.
Category
The fastest way to understand a new category is to hear what it refuses to be. Each of these was a real design decision, and each one costs us something.
A button raises noise. HALO raises an accountable object: owner, clock, escalation path, verified end.
Workload indicators stay private, location stays at zone level, and no minute-level productivity score is produced or published by default.
HALO summons people. It does not take orders and it does not take payment. It is designed to run with no integrations on day one.
Routing is deterministic and explained: the chosen person, the alternatives and the rejection reasons are all recorded. No model is guessing about your floor.
See it work
Scroll, and the drawing makes it. Aster House is a synthetic demonstration venue: a terrace the pass cannot see into, two guests, one waiter and ninety seconds that either get counted or do not. The lifecycle rules it exercises are the ones that are actually built.
The room exists before the request does. A terrace the pass cannot see into.
A guest presses. A need stops being a mood and becomes a fact on a ledger.
Routing runs, and keeps its reasons. One owner, the alternatives, and why they were passed over.
It lands on one wrist as one next action, with the reason attached.
Somebody walks. The clock is still running, and everyone can see it.
Closed by the guest, not by the person who did the work. Ninety-nine seconds, on the record.
Aster House · synthetic venue · not a screenshot
Four promises
The same request is a different promise depending on who is holding it. HALO is only useful if all four are true at once.
Guest
The guest surface confirms the request the moment it exists, names the state it is in, and closes only when the guest, or an integration event, agrees it is finished.
Guest view
Staff
Staff receive a single next-best action rather than a queue to triage, with the reason it was routed to them. Declines are attributed to protocols, not to people, and break protection is a hard filter rather than a courtesy.
Staff view
Manager
Zone load, requests past their accept budget, armed recovery protocols and the full event chain behind any outcome. Intervention becomes a choice rather than a scramble, because the clock is visible before the complaint arrives.
Manager view
Operator
Every published number carries its formula, its source events, its exclusions and its confidence. The ledger is append-only, so a result from week six can still be reconstructed months later.
Operator view
The evidence contract
There are no customers to quote and no results to show. What can be committed to now is the method, frozen before the measurement window rather than chosen after it.
Definitions, formulas, exclusions and dayparts are signed before the measurement window opens. Amendments are versioned and signed; they never quietly replace the original.
A request closes on the guest's confirmation or an integration event, never on the say-so of the person who performed it.
Demonstration venues like Aster House exist to explain the system. They never appear in a pilot result, and every figure states its source events.
If the frozen criteria are not met, that is the finding and you receive it complete, with the limitations and confidence stated. A pilot that proves HALO is not worth buying is a successful pilot.
Signed before the window opens, not after the numbers arrive
Where HALO fits
HALO is not built for one kind of room. Property, then zone, then service point: the same model describes a forty-cover restaurant, a resort, a members' club or a stadium suite. If a guest can ask for something and a team has to deliver it, the record applies.
Pilot cohort · open to every premium venue
Pilots are open to any operator who takes service seriously enough to want it measured. The venue type does not decide eligibility. The standard of service does.
Same record · wider world
The problem is not unique to restaurants and hotels. Wherever people are served at a premium, requests go unowned and nobody keeps the record. Operators in these settings are welcome to open a conversation.
What is real today
HALO is in private preview. The lifecycle rules the drawing demonstrates are real and tested; the surfaces staff and guests will hold are in build. Nothing below is aspirational.
Built and tested
In build
Not built, not claimed
The paid pilot
You are buying evidence about your own service intervals, and the honest answer either way. Free pilots are not offered: they buy politeness rather than evidence.
01 Two weeks
Manual sampling on your floor, plus whatever data already exists, each with a data-quality score. The metric contract is frozen and signed at the end of this step.
02 Six weeks
HALO runs live in one venue with weekly operator review. Nothing in the metric definitions moves during this window; matched dayparts are compared against the baseline.
03 The remainder
You receive the full result with limitations and confidence stated, against written success criteria and a conversion price agreed before go-live.
Start a conversation
Five fields, two of them optional. We reply personally, usually within two working days.
Read the two-page pilot brief: the engagement, the evidence contract and the build status on one printable page.
Who you would be working with
HALO is being built by one accountable person, not a sales organisation. A pilot means direct access: setup and staff training on site, weekly review with the operator, and the same person answering the phone when something breaks. Pilots are run on site wherever the venue is, and travel is priced into the engagement rather than bolted on. Invenio Protocols Limited is the legal owner of the product, contracts and any pilot evidence; Invenio HALO is the product brand.