A named team owns every request from the moment the practice assigns it.
District nursing · Riverside
Every request gets an ending.
When a carer raises a concern, Aurly gives it a named owner and a deadline, chases it until someone answers, and keeps a record of what was decided.
AUR-000042RaisedNeeded today · 6 hour window
Not startedClock starts on assignment
- Oak Lodge Care Home raised it
Window09:56
11:30text13:00call14:30escalate16:00due
A synthetic example. Nobody named here is a real person or place.
A concern leaves the home as a phone call. Then what?
The home rings the practice. The practice passes it to district nursing, probably. After that, nobody can say for sure who has it or when it will happen.
Care homeNotices a change
Phone
GP practiceTakes a message
Email
Community teamHas it, probably
No more ringing round to find out.
The care home, the practice and the community team look at the same request and see the same answer.
The carer says how soon. That sets a deadline the server keeps, day and night.
Due 16:00 · 3h 32m left
A request only closes with an outcome, and the home is asked whether the need was met.
Completed · need met
Requests cannot just go quiet.
Busy means offering a time.
A team without capacity says when it can do it. It cannot simply refuse.
A decline goes back to the practice.
It stays on the queue until someone else takes it.
The clock keeps running out of hours.
Escalations go to whoever is on duty.
People make the decisions.
Nothing automated can assign a request or close one.
Bell
Bell does the chasing, so nobody has to.
If nobody answers, Bell texts, then calls, then escalates. Messages carry a reference number, never a resident's name.
If a carer raised a request now
What Aurly will not do
Replace 999
If someone is in danger, Aurly sends nothing and tells you to call 999.
Replace your systems
Your care planning and clinical systems stay as they are. Aurly sits between them.
Make clinical decisions
No agent answers a clinical question. People decide.
See it working in twenty minutes.
We raise a request, answer it, then let the clock run out so you can see what happens. We will also tell you what is not built yet.