Turn every risk into a named person's job, automatically.

No. Nineteen workflows ship in Start from a template and each installs as a draft you switch on. Four risk plays fire on a CRM event alone from day one, and close on Recovered, Saved, Churned or False positive.

The company owner gets a root-cause call task due in two days at priority urgent. If the play asks for a concession, it waits on an approval gate with a 24-hour SLA, decided in Triage. An action left idle for five days escalates to the owner's manager, once.

No. One open run per play per account is held by a database constraint, so a second trigger while the run is open is a silent no-op. Cooldown and reapplication settings control when it may re-enroll.

Not at the same time. An exclusion group typed on both plays suppresses the expansion play while the risk run is open.

Yes. Describe it in a sentence, such as when health drops below 40, task the company owner. Test this flow then resolves real fields and fires no emails, Slack, webhooks or tasks.

Built in, and it runs on a clock rather than on somebody remembering. Tier one is the account owner, who gets the dated task. Tier two is that owner's manager: an action left idle for five days nudges the owner first, then notifies the manager with the company, its ARR, the stuck action and how many days it has been idle. A concession sits at its own tier, an approval gate with a 24-hour SLA decided in Triage, which branches to approved, rejected with an exec escalation, or no decision, which chases the approval.

Three tiers and two clocks, and every row is a real field rather than a document. Tier one, the account owner, holds the dated task from the moment the risk fires. Tier two, the owner's manager, is resolved at run time by walking the reporting line on the workspace record, so the notice lands on a real person rather than a name typed into a template. Tier three is the approval gate for anything that costs money. The clocks are 24 hours on an approval and five days on an idle action, and each stuck action escalates exactly once, so an escalation cannot turn into a daily reminder the team mutes.

The document stops being the thing that has to be remembered. Every row in a typical escalation template, who owns it, who it goes to next, how long before it moves, what closes it, becomes a field on the play: the owner, the reporting line, the SLA in hours or days, and a closing disposition of Recovered, Saved, Churned or False positive rather than a bare done. The process runs whether or not anyone opens the document.