Oversight

Built-in checks across departments. When one spots an anomaly, it alerts, stops or fixes.

Checkout throws a payment error at eight in the evening. Who finds out before a customer calls?

Works with

A day of checks

Quiet most of the day.For some problems, a message.

Each check runs on its own clock. Most stay quiet until they find something. Some only run when you open a screen.

Demo data

Invoices

On screen

A possible duplicate invoice

Invoice flagged

Service

Phone and email

A customer waiting for a rep

Customer waiting for a rep

People

Stop

A broken clock-in on the hours report

Report fixed and sent

Orders

Phone

Paid personalized poster, no print file

Paid poster, no file

Customers

Resend

A text rejected after "sent"

QuietOn every delivery report

Website

Phone and email

A new checkout error

Payment error at checkout

Shipping

Auto-closes

A lost delivery update

QuietEvery 5 to 15 minutes

Finance

On screen

Profit on paper, negative cash flow

When the screen opens

Quiet only means no message went out. No screen yet shows that every check actually ran.

1 of 3

Some checks only flag.

Open the invoices screen, and an invoice that may have been recorded twice gets flagged.

Demo data

Invoices screen

On screen

Worth knowing

Packaging supplier₪1,240Aug 29
Glass supplier₪860Sep 4
Packaging supplier₪1,240Sep 17

Same amount, worth a check

Same supplier, same amount, within 45 days.

The flag stays on screen. You check with the supplier.

2 of 3

Some checks block.

An hours report with a broken clock-in won't send until it's fixed or an override is explicitly marked.

Demo data

Monthly hours report

To the accountant

Send to accountant

Send blockedFix

A shift in this report has no clock-out.

Shift fixed on screen. The fix was logged.

Report sent to the accountant.

An override has to be explicitly marked.

3 of 3

And some send a message.

Each one goes to the phone set for it in code.

Demo data

Website20:04

Payment error at checkout

Page and fault type. Details in the email too.

More customers hit it. No new message went out.

Orders17:25

Poster with no print file

The order is paid. The link in this message regenerates the file.

A note was added to the order

Service13:40

Customer waiting for a rep

No reply for five minutes.

Summary and draft in the email.

Phones set for each check

Live todaySee exactly what runs

Every two minutes, the system checks for a new error logged in checkout, payment, the cart or the payment processor. If it finds one, the owner gets an email and a text. Each fault gets a signature and goes out as one message, even when many customers hit it, with at most eight alerts per run. When the server fails to create an order, it's counted per hour, so a lasting fault sends at most one message an hour, and a browser error that's already been reported isn't sent again. The check only sees errors that were logged. It can't see a checkout that doesn't load at all.
LIVEcheckout-error-alert
Every five minutes, the system checks for chat customers who asked for a person and got no reply. Each conversation gets at most three alerts a day per urgency level: an email with a conversation summary and a draft reply, and a short text to the phone.
LIVEchat-wait-alert
Every fifteen minutes, the system looks for paid personalized-poster orders that have the customer's uploaded photos but no print file. If a file is missing, a text goes out with a link that regenerates it, and a note is added to the order. The check covers one product.
LIVEposter-sketch-watchdog
The monthly hours report only goes to the accountant when it has no broken clock-ins. The server itself refuses to send it, the screen lists each broken clock-in with a Fix button, and an override has to be explicitly marked.
LIVEaccountant-send-gate
When you open the invoices screen, it flags an invoice that may have been recorded twice: same supplier, identical amount, within 45 days. The flag stays on screen and doesn't stop a payment.
LIVEexpense-insights-panel
If the SMS provider says a message was sent but the delivery report then shows it was rejected, the message goes out again on WhatsApp, once only, and never for a marketing blast.
LIVEsms-whatsapp-rescue
Every 5 to 15 minutes, depending on the carrier, the system itself asks the carrier what happened to each parcel from the last two weeks that's still marked as shipped. When the carrier reports it delivered, the order closes and the customer gets an email, even if the carrier's own update got lost. The owner isn't notified, and a parcel stuck in transit doesn't trigger an alert.
LIVEdelivery-confirmation-poll
When operating profit is positive but cash flow is negative, the profitability screen shows an alert with the two break-even points side by side. It appears only on that screen, and only while it's open. The alert is based on the commitments and expenses entered on the screen, not on the bank account.
LIVEcash-vs-paper

The checks run. The alerts haven't been captured yet.

Messages go to the phones and inboxes set for each check.

Most include order numbers, customer and employee names, and amounts, so they haven't been published yet. The first one that can be cleaned up is the evening check's message, which holds only times and counts. Until then, the demo above is an illustration.

What the Oversight department does

New checkout errors reach your phone in about two minutes
Live todayHow it works
- Every two minutes, the system checks for a new error logged in checkout, payment, the cart or the payment processor. If it finds one, the owner gets an email and a text with the page and the fault type. Each fault gets a signature and goes out as one message, even when many customers hit it, with at most eight alerts per run. When the server fails to create an order, it's counted per hour, so a lasting fault sends at most one message an hour, and a browser error that's already been reported isn't sent again. The check only sees errors that were logged. It can't see a checkout that doesn't load at all.
  LIVEcheckout-error-alert
Unanswered requests for a person trigger an alert
Live todayHow it works
- Every five minutes, the system checks for chat customers who asked for a person and got no reply. Each conversation gets at most three alerts a day per urgency level: an email with a conversation summary and a draft reply, and a short text to the phone. Drafts that promise an amount, a discount or an arrival time are thrown out, and financial or legal cases get no draft at all. When more than three customers are waiting at once, one combined message goes out, and no alerts are sent between 23:00 and 08:00.
  LIVEchat-wait-alert
Paid personalized posters with no print file get caught
Live todayHow it works
- Every fifteen minutes, the system looks for paid personalized-poster orders that have the customer's uploaded photos but no file to print from. It skips orders less than 20 minutes old, and it reads the order itself, not a table derived from it, so a broken connection can't pass for a clean result. When a file is missing, a text goes out with a link that regenerates it from the photos, and a note goes on the order. The check covers one product: the personalized poster.
  LIVEposter-sketch-watchdog
A broken clock-in holds the hours report back from the accountant
Live todayHow it works
- The monthly hours report only goes to the accountant when it has no broken clock-ins: a missing clock-out, a zero-length shift, or a shift over 16 hours. The server itself refuses to send it, and the screen lists each broken clock-in with a Fix button. The check catches broken clock-ins. It doesn't verify that the hours themselves are right, and an override is possible when explicitly marked.
  LIVEaccountant-send-gate
A text rejected after "sent" goes out again on WhatsApp
Live todayHow it works
- The SMS provider says a message was sent before it has even processed it. The real status arrives in a delivery report about 45 seconds later. If that report shows a rejection, the exact same message goes out on WhatsApp, once only, and never for a marketing blast. In a live test, the WhatsApp message landed about two seconds after the rejection. This only works for messages whose delivery report comes back, and a failed resend is logged without anyone being notified.
  LIVEsms-whatsapp-rescue
Every evening: was the store fast today?
Live todayHow it works
- Every evening at 21:45, the server reads that day's logs: how many requests were slow, how many crashes there were, the load, and the state of the disk. It sends itself the same query twice to confirm the cache really responds, and times the orders screen's query. The message goes out every evening, either all clear or a list of what crossed a threshold, so you know the check ran.
  LIVEnightly-healthcheck
Possible duplicate invoices get flagged on screen
Live todayHow it works
- When you open the invoices screen, it checks the invoices already received for ones that may have been recorded twice: same supplier, an identical amount above ₪300, within 45 days, credits excluded. If the invoice number's digits match too, the flag goes from possible to certain. The same panel also flags a regular supplier who stopped sending invoices and VAT that doesn't add up. The flag stays on screen. It doesn't stop a payment, and the system doesn't pay anyone.
  LIVEexpense-insights-panel
WordPress checks run even with no visitors
Live todayHow it works
- WordPress only runs scheduled tasks when someone visits the site. So every fifteen minutes, an outside request forces it to run them, which keeps the evening check and the carrier follow-ups running even when nobody's on the site. If this clock stops, nobody gets notified.
  LIVEwp-cron-tick
One place for every alert is where this is going
Where it's headedHow it works
- Today each check works on its own, through its own channel, and some keep no record of what they sent. Nothing yet shows, in one place, which alert went out, to whom, when, and whether it arrived. That's where this is headed.
  VISION

Who the Oversight department talks to

What they decide together

Each row is one department and the decision their conversation leads to. Pick a row to see the conversation.

Oversight

Website

A payment error hits checkout one evening. About two minutes later, the phone buzzes.

Illustration

WebsiteA payment error was logged on the checkout page.
OversightWithin about two minutes: an email and a text with the page and the kind of error.
OversightMore customers hit the same error that hour? No more messages. The phone doesn't get flooded.

Checkout gets fixed while customers are still on the site, not after someone calls to complain.

Live todaySee exactly what runs

Every two minutes the system checks for new errors at checkout, in payment, in the cart or at the payment processor, and if it finds one, the owner gets an email and a text. Each fault is identified by a signature and sent once, even when many customers hit it, with at most eight alerts per run. A server-side failure to create an order is counted per hour, so an ongoing fault sends at most one message an hour, and a browser error that's already been reported isn't sent again. The check sees errors that were logged, not a checkout that fails to load at all.
LIVEcheckout-error-alert

Open Website

The question we get about this department

Another system that beeps all day?

The opposite. Most checks stay quiet until they find something, because people stop reading alerts that fire about everything. A checkout fault that hits many customers goes out as one message, at most once an hour while it lasts. When more than three customers are waiting for a rep at once, you get one combined message. The evening check reports every evening, even when all is well, so you know it ran.

Live todaySee exactly what runs

Each checkout fault gets a signature and goes out as one message, even when many customers hit it, with at most eight alerts per run. When the server fails to create an order, it's counted per hour, so a lasting fault sends at most one message an hour.
LIVEcheckout-error-alert
Each conversation gets at most three alerts a day. When more than three customers are waiting at once, one combined message goes out, and no alerts are sent between 23:00 and 08:00.
LIVEchat-wait-alert
The evening check sends a message every day at 21:45, even when everything's fine, so you know it ran.
LIVEnightly-healthcheck