Skip to content
Maliru Help Center

Confirmations, declines and automatic reminders

Every published shift asks the worker to confirm — and Maliru chases silence for you before the start time.

Publishing a shift is half the story — you also want to know the worker has seen it. Maliru asks for a confirmation on every published assignment, and chases the ones that stay silent.

Shifts

When you publish, each person on the shift is notified: "New shift: {job}" — "Starts {when}. Confirm in Today." On their phone the shift has a Confirm button. To turn it down, they open the shift and tap Reject shift beside Confirm, which asks for a Reason — a refusal always says why. Both are offered only until the shift ends; a shift that is over has nothing left to answer. Publishing several shifts to the same person at once sends them one notice, "{count} new shifts", rather than one each.

Their answer shows next to their name in the shift detail:

  • confirmed — they have seen it and accepted.
  • declined — they have refused. The people who manage that job's schedule are told at once ("{name} declined: {job}", with the worker's reason), so a refusal never sits unnoticed.
  • not confirmed yet — published and delivered, with no answer so far. This is the state to watch.
  • wants to claim — on a shift open for claiming, someone has asked for a spot (see below).

Routes

A route is one card on the worker's phone, however many jobs it holds, with a single Confirm. Confirming once confirms the whole route for that person. On a shared route, each holder confirms for themselves — one crew member's answer doesn't confirm the others.

A route can't be turned down from the app. A holder who can't do it should tell the office, which can change the crew. Until they confirm, their card reads Awaiting confirmation.

A route card on the phone waiting to be confirmed, with its job count and progress

Publishing a route tells each holder once, "New route: {route}", and the card appears in Today and Work.

Repeating shifts

When a person's new work is all one repeat, they get one notice that names it: "New repeating shift: {job}", "{count} shifts from {when}. Confirm all in Today." In Today and Work, Confirm all ({count}) sits above their unconfirmed shifts in the repeat and confirms every one of them still to come. Each shift keeps its own Confirm and Reject shift, so one date can still be turned down. Confirm all works with no signal too: it waits on the phone and sends when it can. Each shift in a repeat also says where it sits, for example Repeats weekly on Mon to Fri · Shift 2 of 5.

On the iPhone and Android apps, Confirm all appears once their next version is installed. Until then each shift is confirmed on its own.

When confirmations reset

  • Moving a published shift's time puts everyone on it back to not confirmed yet. The dialog warns first: "The team is notified and asked to re-confirm."
  • Adding jobs or people to a published route puts the holders affected back to Awaiting confirmation. So does moving the route to another time. Changing only its title doesn't.

Automatic reminders

You don't have to chase silence yourself. Nothing is chased the moment you publish: people need a chance to look first. For work starting within 48 hours that is still not confirmed yet:

  1. Once the worker has had time to answer (two hours after they were asked, or half the time left before the start if that is sooner), they are reminded: "Please confirm: {job}. This assignment starts soon and is still unconfirmed."
  2. If the reminder goes unanswered for the same while, everyone with Manage schedule is alerted: "{name} has not confirmed: {job}. Starts {when}."

Each step happens once, so nobody is spammed with repeats. Moving a shift asks everyone on it to confirm again, and the chase starts over.

On a route, each holder is chased once for the whole route, "This route starts soon and is still unconfirmed.", however many jobs it holds. Only the people who haven't confirmed are reminded, and the alert to the office names them.

A repeat is chased once for the whole series, from the moment a person's first unconfirmed shift in it comes into the 48 hours: "Please confirm: {job}. Your repeating shifts start soon and are still unconfirmed. Confirm all in Today." If that goes unanswered too, the office is told once, with how many of their shifts are waiting.

Keeping an eye on it

The dashboard's Unconfirmed shifts and Overdue shifts cards open the Schedule's List on its Unconfirmed or Overdue window. You can also choose those windows yourself in the List (see Finding your way around the Schedule). The Unconfirmed window lists shifts only; check a route's confirmation on its calendar card.

Claims

A shift opened for claiming adds one more state, wants to claim. If you set Require my approval for each claim, pending claims appear in the shift detail — "{name} wants to claim this shift" — with Approve and Decline.

Tip: if a worker says they never got the ask, check they're signed in on their phone with notifications allowed. The in-app inbox holds every notification even when the phone's push permission was refused. See Not receiving notifications.