Every problem, with an owner and a clock. Nothing slips through.
Meet Camelia.
Camelia is the OKmystay incident module. The guest reports a fault with a photo, artificial intelligence classifies it and assigns it to the least-loaded technician, and you see who owns each one and how long it's been stuck. A lost WhatsApp stops being a work order.
I want a demoHow it works
It opens with a photo
The guest reports the incident from their panel, with a photo and their booking already linked. Or your team opens it from theirs. It arrives untriaged, into Camelia's queue.
AI classifies it and shares it out
Camelia gives it a category and a priority, and assigns it to the person in charge of that category with the fewest open incidents. If it's high or urgent, it alerts them by Telegram, SMS or email.
It gets resolved, with tracking
The technician works, attaches photos, comments and closes with an outcome. Whoever raised it gets an email and can follow the status at a public URL —Received, In progress, Closed— without seeing anything internal.
Not one fault in no man's land
The question that ruins a rental isn't "what broke?", it's "who was looking at it?". Camelia gives each incident a single owner and two clocks — and whatever's been stuck too long, it paints red before it becomes a bad review.
Who owns it and how long has it been stuck?
Every incident has a single owner and two clocks: how long it's been open and how long it's been with whoever holds it now. Whatever stalls is painted red and pops up as an alert. Nobody falls through the cracks.
Real context, not a generic ticket
The incident is linked to the specific booking, smart lock, device or payment, with the history of what was replaced. The advantage a generic helpdesk will never have: Camelia knows your building.
AI triage, assignment without argument
Camelia classifies with artificial intelligence and shares out by workload automatically. The boss stops assigning by hand. And the AI never invents an owner: if in doubt, there's a deterministic backup assignment.
Why Camelia
It starts where the problem is
The guest, cleaner, owner or an admin opens the incident from their panel, with the photo and booking already attached. Not a message that gets buried in a chat: a traceable report from minute one.
Automatic assignment by workload
The AI classifies and assigns to the least-loaded technician in that category. No meetings to divvy things up, no one person ending up swamped while another sits free.
What's stalled, in red
One clock per incident and another per owner. When something sits on the same desk too long, it's marked stalled and raises an alert. No more incidents that quietly fall asleep.
Photos and conversation, kept in order
Photos and videos, a message thread visible internally or to whoever raised it, and everything audited. The full story of each incident, in one place.
Public tracking, without exposing anything
Whoever raised it follows their incident at a URL with clear stages —Received, In progress, Closed— without seeing internal data, team names or private notes.
Linked to your operation
Booking, smart lock, device, payment, another incident. Camelia links each case to whatever it actually touched, with its history. It's not a loose ticket floating in a vacuum.
Rosa collects the complaint, Camelia resolves it. Every fault with an owner, a clock and a photo.
How many faults get lost in your WhatsApp?
Tell us how you handle your properties' incidents today. We'll show you how Camelia gives them an owner, a clock and tracking.
mail@okmystay.com