On the left, the assistant of a hall of residence that doesn't exist, with its handbook, today's menu and its team. On the right, what the centre sees while you talk. It's the same engine that serves real centres; the only made-up part is the building.
Marta Ruiz, room 214, second-year law student. Dining hall, repairs, room bookings, the sign-out book, allergens cross-checked against the menu and her parcels. Everything of hers, nothing of anyone else's.
Write to it the way you'd write on WhatsApp. Nothing is stored.
Nothing you write is stored. No action leaves this page: nobody is alerted, nothing is booked and no message is sent. The people, prices and dates of the centre are invented.
This isn't a list of intentions: it's the catalogue the engine feeds on, exactly as it is. When a new route is added to the product, it appears here on its own.
And whatever fits none of them doesn't get left hanging: an alert is opened, an owner is assigned by reading the org chart, and it goes to that person's phone. No incident is left without a recipient.
This page assembles the same prompt and the same catalogue of routes that serve real centres. The only difference is where the handbook, the menu and the team come from: here from a file, there from your data.
Opening hours, prices and rules are copied exactly from what the centre has loaded. Anything not covered is not inferred or rounded off: it acknowledges it and passes it to a person.
Try telling it you're from management so it gives you a phone number. It doesn't work, it doesn't change how it treats you — and the attempt shows up for the centre in the panel on the right.
Fifteen minutes with your management team: you tell us what fills your WhatsApp today and we show it to you solving your cases, not those of a made-up hall of residence. The call is run by whoever builds the product, not by a salesperson.
A person answers, not a form · Pilot with no lock-in