Notifications¶
What Lupa tells you about, how it reaches you, and how to clear it — for admins and technicians, in a browser and in the field app.
Every signed-in person has a notifications bell. In Lupa Dash and Lupa Tech it is Notifications in the left rail, below your tabs. In the field app it is the bell at the top right of the Agenda tab.
Read what needs your attention¶
How it works. The bell opens a feed of your unacknowledged notifications, newest first. Each item carries its level — alarm, warning or info — a one-line subject, a detail line naming the customer and date where there is one, and the time it was raised. In a browser the time is shown in UTC.
The badge on the bell counts what is waiting:
- In a browser, a red badge counts alarms only. When there are no alarms, an amber badge counts warnings and info items together. A red badge always means at least one alarm.
- In the field app, the badge is always red and counts everything unacknowledged, up to 99+. Read the level on each item rather than the badge colour.
To read your notifications in a browser
- Choose Notifications in the left rail.
- Read down the feed.
- Choose an item's text to go to what it is about.
What you'll see. Choosing an item closes the feed and moves the page behind it:
| The item names… | In Lupa Dash | In Lupa Tech |
|---|---|---|
| a date | the Dispatch board on that date | your Schedule on that date |
| a customer but no date | that customer on the Clients tab | that customer on the Clients tab |
| neither | the Dispatch board | your Schedule |
It does not open the individual visit or schedule.
To read your notifications in the field app
- On the Agenda tab, tap the bell.
- Read down the list. Pull down to refresh it.
Items in the field app do not lead anywhere: read them, clear them, and go to the day yourself.
If the feed is empty. It reads Inbox zero and No unacknowledged notifications in a browser, and You're all caught up. in the field app.
Clear an item¶
How it works. The feed shows only items you have not cleared, so Ack (Acknowledge in the field app) and Dismiss have the same visible effect: the item leaves the feed and the badge count falls. There is no view of cleared items and no undo. Clearing an item changes nothing about the work it refers to — acknowledging a missed-visit alarm does nothing to the visit.
To clear an item
- Open the feed.
- Choose Ack (or Acknowledge) on an item you have taken in, or Dismiss on one you are finished with.
What you'll see. The item disappears and the badge count falls.
Before you clear. Read the detail line first, and in a browser follow the item through to the board or schedule. Once cleared, it is gone from the feed.
Make sure alarms reach you away from the screen¶
How it works. The level decides how Lupa reaches you:
| Level | In the app | |
|---|---|---|
| alarm | yes | yes |
| warning | yes | yes |
| info | yes | no |
Email goes to the address on your profile, so alarms and warnings reach you even when Lupa is closed. Keep that address current — see Signing in and your account.
Admins also get an end-of-day digest email at 18:00 company time. It lists visits recorded as missed that day, today's carried-forward visits still unclaimed in the open pool, and visits that raised a "Visit running late" alarm. On a day with none of these, no digest is sent.
What raises a notification¶
How it works. Lateness is watched per visit: when a one-off visit is booked with a time on it, Lupa sets two checks against that time. A nightly sweep at 02:00 UTC catches visits whose day passed with nothing recorded. Everything else is raised by the action that causes it.
| What happened | Level | Who gets it |
|---|---|---|
| A one-off visit's booked time arrived and the visit was still untouched | warning | the assigned technician — "You're running late" |
| Its estimated duration then ran out with the visit still untouched | alarm | every admin — "Visit running late" |
| The nightly sweep found missed visits | alarm | every admin, as one item with a count |
| A technician rejected a recurring visit already confirmed on their schedule, or a visit they had claimed from the open pool | warning | every admin — "Tech rejected a confirmed visit" |
| A committed arrival time shifted for a customer who expects to be told | warning | the technician holding the visit |
| A visit was assigned to you, or reassigned away from you | info | the technician concerned |
| A visit you held moved back to the open pool | info | the technician who held it |
| A customer was assigned to you | info | the technician |
| You became, or stopped being, the default technician on a recurring schedule | info | the technician concerned |
| A team member was deactivated | info | every other active technician |
Which visits are watched for lateness. Only visits booked one-off, and only when they carry a time. A visit that comes onto the board from a recurring schedule is not watched, so neither lateness item fires for it. For recurring work, the only notification is for a visit already missed. If most of your work is recurring, use the board, not the bell, to see that a visit is running late.
If a technician is working without updating status. Both lateness checks fire only while the visit is still in its booked state. Once it has been confirmed, marked on my way or in progress, or finished, neither item is raised.
If a visit is moved after it is booked. Lateness checks follow the time the visit was first booked with. For a visit you have moved, judge lateness from the board.
If a visit has no scheduled time. Open-pool work with no time on it is not checked for lateness.
If a recurring schedule is cancelled or paused. No notification is raised. The change shows on the board and in the schedule's own history.