Is the room free, how do visitors register, how does expense work — one sentence by the elevator, at the front desk, in the corridor; answers come from OA and policy documents.
Each is small; together they cost everyone ten-plus minutes a day.
Booked but unused, needed but taken, and no free room in sight.
Registering, escorting, notifying — the front desk is chained to the process.
How to expense, who stamps what — ask around before finding clause 4.2.
Broken lights and leaking AC vanish into a chat thread.
The most common questions from live deployments. EBOX hears the question, queries your systems within authorization, answers by voice and shows the key figure on screen.
Sample dialogue; data from live OA queries (illustrative).
Read-only standard APIs into OA and document systems; writes like booking and repairs open by authorization.
Is the room free, how do visitors register, how does expense work — one sentence by the elevator, at the front desk, in the corridor; answers come from OA and policy documents.
Not another system to learn — the entrance to your existing systems, moved to the tip of the tongue.
Lobby, front desk, elevator hall, pantry — wherever questions happen.
Policy Q&A names the clause — never a guess.
Booking rooms and filing repairs by role, logged and auditable.
Tell us the building scenario, your OA system and the ten questions everyone asks — start with the one in the lobby.
