Demo control
Take the tour
Explore seven implemented workflows. Each step selects a demo profile and distinguishes the behaviour shown from the simulation's limits. You can leave the tour at any time.
- 01
Ask something it can answer
Send the first suggestion, about a guest with no credit card.
What it shows
The answer includes exact supporting excerpts and identifies visible sources that did not provide applicable guidance.
What is simulated
The answer comes from a fixed script. There is no search and no model.
You can also
Select “Flag a problem” to describe a concern and open a review ticket. The confirmation explains that reporting an issue does not establish that the answer is incorrect.
- 02
Now ask something it cannot
Send the second suggestion, about a card belonging to someone else.
What it shows
It says the material does not settle it, and says so without claiming the answer does not exist. Four sources were reviewed; three are listed and the count says three. The fourth is not visible to this person, so it leaks through no list and no number.
What is simulated
The grades of each source are written into the scenario, not computed from a permission engine.
- 03
Create a request for a response
On that same answer, press “Create a request”, then confirm.
What it shows
Review the information to be submitted and its destination before confirming. The resulting ticket remains available after the conversation ends.
What is simulated
The ticket is stored in this browser session. It is not sent to a server.
- 04
Track the ticket
Open “My tickets”. The ticket you just raised is at the top.
What it shows
The person who raised the ticket can see its status, activity and next step.
What is simulated
Three fictional tickets are supplied as examples.
- 05
Change person and find it
The demo control at the bottom left is now Martín. Open the queue: the same ticket is there, unassigned. Take it, write an answer, sign and close.
What it shows
The same ticket offers different actions to its requester and handler. Closing it does not publish its response to the corpus.
What is simulated
Nobody is notified, and there is no assignment rule: that question is still open.
- 06
Turn an answer into knowledge
In the corpus, open “Guarantee on stays longer than ten nights”. Approve it. Then, and only then, publish it.
What it shows
Resolution, proposal, approval and publication are separate actions. Material cannot support answers before publication.
What is simulated
There is no document engine. Also try the protocol with a padlock: you can see it exists and its content is not delivered.
- 07
See the deployment
As Elena, open the deployment: people, profiles, scope, capabilities.
What it shows
The deployment declares its purpose, covered topics, exclusions and enabled capabilities.
What is simulated
Invitations, scope and capabilities change only this browser’s simulation: no email is sent and no real access changes. The three profiles belong to the demo scenario; the real split of powers is still an open question.
For implemented screens and planned features, see the Site map.