Confirmations, declines and automatic reminders

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

Rufineous Emmanuel

Last Update a day ago

Publishing a shift is half the story — you also want to know the worker actually saw it. Maliru builds confirmation into every published assignment.
How confirmation works
When you publish, each assignee is notified: "Starts {when}. Confirm in My Day." In their app, the work carries a Confirm button and a decline option. Their answer shows up in your shift detail next to each name:
  • confirmed — they've seen it and accepted.
  • declined — they've refused. Everyone who manages dispatch is notified immediately ("Assignment rejected: {job}", with the worker's note), so a refusal never sits unnoticed.
  • not confirmed yet — published and delivered, but no answer yet. This is the state to watch.
Routes confirm once. A route of many jobs is one card in the worker's app with a single Confirm — answering once confirms the whole route. Workers never have to confirm each job on a route separately.
Automatic reminders (escalation)
You don't have to chase silence yourself. Within 48 hours of a shift's start, any published assignment still not confirmed yet is escalated automatically:
  1. The worker gets a reminder — "Please confirm: {job}. This assignment starts soon and is still unconfirmed."
  2. Everyone with the Manage dispatch permission gets an alert — "{name} has not confirmed: {job}. Starts {when}."
Each assignment is chased once — you won't be spammed by repeats. Routes follow the same rule at route level: one reminder for the whole route to the worker ("This route starts soon and is still unconfirmed.") and one alert to dispatch, no matter how many jobs the route contains.
Keeping an eye on it
The Dashboard gives dispatch two live tiles, both of which jump straight to the Schedule:
  • Unconfirmed shifts — published, upcoming, still waiting for an answer.
  • Overdue shifts — published shifts whose window has passed without being completed.
Claims
Shifts opened for claiming add one more state: wants to claim. If you set Require my approval for each claim, pending claims appear in the shift detail with Approve and Decline buttons.
Tip: if a worker says they never got the ask, check they're signed in on their phone and have notifications enabled — the in-app inbox always holds every notification even if the phone's push permission was refused. See Not receiving notifications in Troubleshooting.

Was this article helpful?

0 out of 0 liked this article