This is the full list of notifications PSS can send, grouped the same way the Notification Preferences page groups them. Each entry says what the notification means and when it fires; notes call out anything non-obvious.
9.13.1 My Work (the technician’s own copies)
My Work notifications are the assigned technician’s personal copy of an event. They carry the same facts as the office-facing version but are addressed to the tech, so a technician can follow their own day without seeing the whole company’s activity.
- Job Assigned To Me — a job has been assigned to you.
- Route Assigned To Me — a service route has been assigned to you.
- Shopping Item Assigned To Me — a shopping (purchase) item has been assigned to you.
- Shopping Item Assigned To Me Updated — the status of a shopping item assigned to you has changed.
- Control Center Readings Rule Triggered On My Stop — a chemical reading you recorded met or exceeded one of your company’s Control Center rules (any of the value, present-or-not, or percent-change rule types).
- Control Center Dosages Rule Triggered On My Stop — a chemical dosage you recorded met or exceeded one of your company’s Control Center rules (same three rule types).
Note: Because these are personal to the technician, adding other recipients to a My Work event on the Allowed Recipients tab makes those people receive messages written as if addressed to the tech. PSS warns you when you do this.
9.13.2 Service Routes
- Route Assigned — a service route has been assigned to a technician.
- Route Visit Started — a technician has checked in at a route stop.
- Route Visit Completed — a technician has finished and uploaded a route stop, or the office recorded a completed visit in Visit History.
- Route Visit Updated — someone in the office edited a route visit after it was completed (times, comments, readings, dosages, checklist, or media). This fires only when something actually changed, so it never doubles up with Route Visit Completed.
9.13.3 Jobs
- Job Assigned — a job has been assigned to a technician: created with a tech in Scheduled status, reassigned to a different tech, or moved from a draft/quote status to a committed one with a tech attached.
- Job Client Approved — a client approved a job or quote (from the emailed quote link or the Client Portal).
- Job Client Disapproved — a client declined a job or quote.
- Job Viewed — a client opened the job or quote on the web for the first time.
- Job Completion Viewed — a client opened the completed-job report.
- Job Request Submitted — a technician submitted a request for new work from the field.
- Job Visit Started — a technician checked in to a job visit.
- Job Visit Completed — a technician finished and uploaded a job visit, or the office marked it done in Visit History.
- Job Visit Updated — the office edited a completed job visit. Like the route equivalent, it fires only on a real change and doesn’t double up with Job Visit Completed.
9.13.4 Missed Work
Missed-work notifications tell the office that scheduled work has not been done when it should have been. Because “should have been” depends on the day’s plan, this is the most involved logic in the system—see 9.13.5 for exactly how PSS decides.
- Route Stop Missed — a scheduled route stop appears to have been skipped over.
- Job Stop Missed — a scheduled job appears to have been skipped over.
- Route Visit Skipped — a scheduled route visit was explicitly marked as skipped, by the technician in the app or by an office user in Visit History (this is a deliberate action, not an inference).
- Purchased Item Not Installed — a shopping item in Purchased status that is linked to the route or job was still not installed when the visit was completed.
9.13.5 How “missed work” is decided
Missed work is inferred, not entered, so it’s worth understanding what PSS is actually checking. A technician’s day is a single ordered list of stops—route stops and jobs interleaved in the sequence shown on their route. PSS watches that sequence three ways at once:
Out-of-order check (immediate). Each time a stop is completed, PSS looks backward at every earlier stop in the day’s order. If an earlier stop has no completed visit, it’s flagged missed right away. This is what catches a technician who jumps ahead and skips a property.
-
Sliding-window check (per stop). After a stop is completed, PSS starts a timer for the next stop. If that next stop isn’t completed within the expected time, it’s flagged. The window is twice the expected time to get to and finish the stop:
window = 2 × ( estimated drive time + estimated on-site time )
End-of-day check (catch-all). Anything still not done by end of day is flagged once, as a backstop, in case the day didn’t end cleanly.
The estimates that feed the sliding window are:
- On-site time — route stop: the average on-site time of the last 5 completed visits to that property by that technician (skipped visits are ignored). With no history, PSS falls back to 30 minutes.
- On-site time — job stop: the duration set on the job. If the job has no duration set, PSS falls back to 180 minutes (3 hours).
- Drive time: the straight-line distance between the two properties, driven at an assumed 25 mph. If either property has no saved GPS location, drive time is treated as 0.
When a technician checks in to a stop, the window for that stop is reset to 2 × on-site time (drive time is zero—they’ve already arrived).
The end-of-day time is adaptive per company: PSS looks at the latest stop-completion time over the last 14 days, rounds it to the nearest half hour, and never sets it earlier than 6:00 PM or later than 11:30 PM (it defaults to 6:00 PM for a brand-new account). If every scheduled stop is already done, the end-of-day check runs immediately instead of waiting.
Several conditions deliberately prevent a missed-work alert, to avoid false alarms:
- The stop was completed (by anyone—coverage by another technician still counts), or explicitly skipped.
- The property isn’t due this service week (for routes serviced every 2, 3, or 4 weeks), or a weekly stop was already serviced somewhere else in the same Monday–Sunday week.
- The visit belongs to a past date that synced late (the “today” gate).
- The stop was already flagged earlier the same day.
Note: The timers are checked by a scheduled task that runs every 30 minutes, so a sliding-window or end-of-day alert can arrive up to half an hour after its window closes. The immediate out-of-order check is not affected.
9.13.6 Control Center notifications
Control Center notifications are rule-based: they fire only when a completed (or edited) visit meets a threshold your company has configured in Control Center (see Section 10). Nothing here fires on its own—if you’re not receiving a Control Center alert, the first thing to check is whether the matching rule is turned on and set to a sensible value.
Readings and dosages come in three flavors each:
- Readings / Dosages — Value Comparisons — a recorded value crosses a number you set (for example, free chlorine greater than a limit).
- Readings / Dosages — Present Or Not Present — a reading or dosage was, or wasn’t, recorded (optionally, wasn’t recorded for N days).
- Readings / Dosages — Percent Changes Up Or Down — a value jumped up or down by more than a set percentage versus the previous visit.
Visit-length and location rules (the preferences page spells the first four out in full, as Short Visits – Configured Rules With Numerical Comparison and … Against The Work Estimate):
- Short Visits — an on-site time below your limit, either as a flat number of minutes or as a percentage of the work estimate.
- Long Visits — an on-site time above your limit, again as a flat value or a percentage of the estimate.
- Too Far Away — Check-In / Check-Out — the technician’s GPS location at check-in or check-out was farther from the property than your configured distance.
Inventory and media rules:
- Low Inventory Detected — a tracked catalog item’s on-hand count dropped below its threshold (for example, when a shopping item install is marked done).
- Visit Media — All / Before / After / Review — the number of photos or videos on a visit met your configured count rule for that media type.
Note: The thresholds and on/off state for all of these live in your company’s Control Center settings, not in Notification Preferences. Notification Preferences only decides who receives an alert once a rule has fired, and on which channel.
Note: Too Far Away checks compare real GPS check-in/out locations, so they’re skipped for visits an administrator creates or edits by hand in Visit History (there’s no field GPS to measure). When the office edits a completed visit, the readings, dosages, and visit-length rules are re-checked only if those particular values changed.
9.13.7 Clients, Client Reviews, Equipment, Shopping, and Extra Items
These notifications track record-keeping changes so the office has a trail of who changed what.
Clients:
- New Client Added — a client record was created.
- Client Info Updated — a client record was edited. This does not fire when a client is deleted, when a deleted client is reactivated, or when only the client’s saved payment method changes.
- Client Deleted — a client was deleted (which also marks the client inactive).
- Client Submitted Work Request — a client asked for new work from the Client Portal (see Section 21). View Details opens the request in a pop-up where the office can add a job or service route for it.
Client Reviews:
- Client Submits A Review — a client left a Happy / Neutral / Unhappy rating on a service visit, a job, or an invoice. One notification type covers all three sources; the detail fields change to match. There is no Follow control on these.
Equipment:
- Equipment Added — a piece of equipment was added to a property.
- Equipment Status Changed — an equipment item’s status changed.
- Equipment Deleted — an equipment item was removed.
Shopping Items:
- New Shopping Item Added — a shopping (purchase) item was created.
- Shopping Item Assigned — a shopping item was assigned to a technician.
- Shopping Item Status Changed — a shopping item’s status changed.
- Shopping Item Removed — a shopping item was deleted.
Extra Items:
- New Extra Item Added — an extra billable item was added to a route or job.
- Extra Item Removed — an extra billable item was removed.
9.13.8 General
- Technician Sent Notification To Office — a technician sent the office a note (with optional photos) from the field. When the technician picks who to notify in the app, only those managers receive it (plus anyone following the property).
- Technician On My Way — a technician sent an “on my way” message toward a property or job. Like most events, this one is off by default (see 9.12); a recipient must enable it.
- Attention Item Marked — a technician flagged an attention item on a route or job visit.
- Auto-Payment Failed — a client’s scheduled automatic payment failed during the daily billing run (including card-authentication failures). It defaults to Web only, and View Details opens the invoice.
9.13.9 System Notifications
- System Broadcast — a platform-wide message from the PSS team, shown with a PSS: prefix and a Contact Support button. Broadcasts bypass Notification Preferences entirely: they do not appear on the preferences page and reach every user on Web and Mobile.