Every change, on the record.
When an onboarding rep moves a ticket — a status change, a new at-risk reason, a risk flag — that change is copied onto the matching deal automatically, so you don’t have to go and find the ticket. This page is the running record of every one of those changes, including the ones where nothing needed updating.
Start with Owner and pick your name: you’ll see only your accounts, grouped by where they stand. Click any account for its full history.
Owner
Pick your name to see only your accounts, grouped by where they stand — At Risk first. The onboarding rep on each ticket is usually someone else, so their name is shown alongside yours.
Feed
Every change across every account, in the order it happened, with a link straight to the deal and the ticket. Filter by what fired it, or search for an account.
Alerts
What went out, to whom, and whether it landed. Two engines drive this — the owner DM on entry and again on day 7, and the channel escalation at 14 days, 28 days and past SLA.
Cron & health
The sync reacts to webhooks; one scheduled scan a day does the escalations and day-7 nudges. If that scan stops firing nothing looks broken — no errors, no alerts, just silence. This page is where that silence becomes visible, and a watchdog posts to #revops-systems-outage-alerts when it isn't.
That scan runs weekdays only, so a quiet Saturday and Sunday are expected. Everything below is judged against the last weekday it was due, not against the clock — see Schedules.
Reporting
The other tabs answer the questions this system was built for. This one answers the ones nobody anticipated — pick a starting point, then change the grouping, the filters or the columns until it says what you need.
Ask about your accounts
Ask in plain English and this looks it up in the same event store the other tabs read — it runs a real query and tells you which one it ran. It can only read: it cannot change a deal, send a Slack message, or fix anything.
Funnel
Where events stop on the way from a ticket move to a deal write. Each row is a place something ended, so the counts read top-to-bottom as attrition.