A generated list per account. Each alert has a key, a plain label, a severity and a detail sentence carrying the actual numbers, so a person acting on it knows what to say rather than just that something is wrong.
Also called: at risk warning · nobody has logged in · usage dropped · no estimates sent · early warning
- 1Login alerts escalate by silence — 7 days medium, 14 days high, 30 days high.
- 2A usage-drop alert fires when this week's sessions are half of a meaningful previous week.
- 3Setup alerts wait for a decent interval: no logo after a week, no lead source after two weeks, no first estimate after two weeks.
- 4'Website form connected but never fired' after three weeks suggests it was never embedded.
- 5'Estimates go out but customers never open them' points at the send channel or spam.
- 6'Used to send estimates, none in 30 days' is high severity — that is a customer leaving.
- 7A bug spike of three or more in 30 days is flagged as friction to be answered.
The alerts are written as instructions to a human, not as flags: 'No website form, Meta or Google — nothing feeds the pipeline automatically'; '4 sent, 0 opened — check the send channel / spam'; 'Only the owner is a member; team accounts retain far better.' Bugs filed by agency staff testing inside an account are excluded, because 'bugs filed by platform staff testing inside the tenant aren't the tenant's friction.'
- A silent failure — a form connected but never firing — looked like low demand.
- Estimates landing in spam looked like unresponsive customers.
- Alerts without detail produced generic check-in emails nobody valued.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →