Service desk handoff
What the agent cannot resolve leaves as a structured case: the request, the approved evidence, the steps already completed and an accountable next action.
CHANNELS AND HANDOFF / FOR COMPANIES
The product goal is to resolve bounded, grounded requests in the place itself. When it cannot, the same service should create a case in the service desk your team already runs, reach the channel they already watch, call a person or, in a future governed workflow, hand state to the visitor's phone.
There is a step-free route on the west side, 90 metres from here. I have opened it for you and reported the lift.
SIX WAYS OUT OF THE TERMINAL
Each route out carries its own maturity label. Some run in the product experience today, some are workflow prototypes shown with synthetic records, and some are the enterprise functionality this platform is built toward.
What the agent cannot resolve leaves as a structured case: the request, the approved evidence, the steps already completed and an accountable next action.
The case surfaces where the responsible team already works, so a floor problem reaches a duty manager in the channel they watch instead of a console they never open.
Today the QR opens the public demo on a phone but transfers no route, answer or session state. A short-lived stateful handoff is a paid-pilot target.
Reach a person by phone when the moment needs one, or leave the request in the queue and be called back when a specialist is free.
After the visit, a receipt, a reminder or an offer on the channel the visitor chose, sent only because they asked for it.
Pass the full context to the online assistant the company already operates, so nobody has to start the story again in a different window.
PILOT TARGET / CURRENT QR OPENS THE PUBLIC DEMO
The current QR opens a fresh copy of the public demo on a phone. It does not transfer the route, answer or conversation shown on the Terminal. The pilot target is a short-lived, consented handoff that carries only the state needed to finish the task.
FIT THE COMPANY
Every organisation already owns its service stack. Each deployment names the systems, permissions and retention rules that fit, and the boundary is agreed before anything is wired. The public product preview connects only to synthetic fixtures.
Structured cases with ownership, completed steps and a resolution receipt
The case appears in the channel the responsible team already watches
A written record for teams that run service from an inbox
Escalation to a person on the phone, or a callback when a specialist frees up
Follow-up, receipts and offers on the channel the visitor chose
Context handed to the web assistant the company already operates
THE BOUNDARY IS PART OF THE PRODUCT
Nothing continues to a personal channel unless the visitor picks it at the terminal, in the moment, for that request.
A handoff carries the request, the approved evidence and the next action. It does not carry a recording of the person who asked.
The agent writes into approved systems within the rules of the deployment, and reads only what that deployment granted.
The public demo has no stateful phone continuity. A pilot handoff would use a declared short-lived link rather than a returning-visitor profile.
ONE SERVICE, MANY DOORS