Live now · Add-on to any plan

Arrivo Intelligence

Two things it does: answers, and actions. Both as you.

It isn't a chatbot bolted onto the side. It's a colleague with your login. Every answer comes from calling the same permission-checked APIs the Portal uses, signed in as you. Every action is shown to you before it happens and logged under your name after.

Book a demo Watch a question become an action
Ask

Plain-English questions about your site, roster and leave.

Anything you'd otherwise open three tabs to find out. It reads live data, not a nightly copy.

Who's on site right now? Who's rostered Saturday morning? How much leave does Kate have left? Who hasn't signed out? Any leave requests waiting on me? Visitors from Fletcher last month?
What an answer looks like Who's on site, who's on Saturday, whose leave is waiting. It reads the same live data you'd see in the Portal, by calling the same permission-checked APIs as you.
Who's on Saturday morning?
Emma and Jack, 8am to 1pm, at Newmarket. Lucy has asked for Saturday off and that's still waiting on you.
Who hasn't signed out?
One visitor: Ben Carter, signed in 10:31 for James. Everyone else is out.
Signed in as the manager. A staff member asking the same thing would see only their own shifts and leave.
Act

Tell it what to do. It shows you the exact change first.

Approve, swap, sign out, publish. It never acts on its own and never does anything your login couldn't.

  1. 1You ask. “Approve John's leave for Friday.”
  2. 2It checks. Coverage on Friday, John's balance, your permission to approve.
  3. 3It proposes. An action card: what, who, when, and what happens next.
  4. 4You confirm. It does it. Logged under your name, visible in the Portal like any other change.
What an action looks like Approve leave, sign a visitor out, publish a roster. It proposes the exact change, waits for your yes, then does it and logs it under your name.
Approve Lucy's Saturday off.
Arrivo action · needs your OK
ActionApprove leave request WhoLucy Bennett WhenSat 13 Sep · Annual leave · 1 day CheckSaturday still has Emma and Jack. Lucy has 4 days left. ThenTell Lucy in Go, update Saturday's roster
ConfirmNot now
Nothing happens until Confirm is pressed. The change then appears in the Portal's history like any other, under the name of the person who confirmed it.
Where the lines are

It has your login and nothing more.

The assistant is not a separate system with its own access. It is a way of using the access you already have.

It can
  • ✓Read the live roster, leave requests and balances, the visitor log and who is signed in right now, for the sites you can see
  • ✓Answer in plain English, with the names, times and numbers from your account
  • ✓Propose an action, show you exactly what will change, and carry it out once you confirm
  • ✓Tell the people affected through Arrivo Go, the same way the Portal would
It can't
  • ✕See anything your own login can't. There is no service account and no separate data store
  • ✕Reach patient or clinical information. There is no API path to it, in the code, not in a setting
  • ✕Change anything without your confirmation, or approve something your role can't approve
  • ✕Work from a copy. It reads live data, so an answer is as current as the Portal
Signed in as youNo separate data store, no back door. If your login can't see it or change it, neither can the assistant.
Health data excluded in codeThere is no API path from the assistant to patient or clinical information. Not a setting, not a policy. It isn't wired in.
Add-on to any planAsk and Actions come together. Turn it on per user, so only the people who approve things can approve things.
Every action loggedAnything it does appears in the Portal's history under the name of the person who confirmed it.

Turn it on for the people who approve things.

Arrivo Intelligence is an add-on to any plan, switched on per user. Ask and Actions come together. Everyone else keeps using Arrivo exactly as before.