SALES
Risk-tier escalation router from Snowflake to Slack or PagerDuty
Watches for accounts whose renewal-risk tier worsens between scoring runs and routes each escalation by severity and value — standard moves go to the AE Slack channel.
How it runs
The automated pipeline, trigger to output.
- TriggerPost-scoring scheduled run
- ActionFetch current vs previous risk tierSnowflake
- LogicKeep accounts whose tier worsened
- LogicRoute by severity and contract value
- ActionPost standard downgrades to AE channelSlack
- OutputPage account director on critical high-valuePagerDuty
What it does
This workflow acts as a severity-aware router for risk changes. It detects when an account's risk tier degrades, then decides where the alert should land based on contract value and how critical the new tier is, so urgent cases get human attention fast.
When to use it
Use it when a flat alert channel buries the accounts that truly matter. It separates routine downgrades from existential ones, paging on-call leadership only for high-value accounts entering critical risk.
How it works
- 1A scheduled trigger runs after each risk-scoring pass.
- 2A Snowflake query returns each account's current and previous risk tier plus contract value.
- 3A logic step keeps only accounts whose tier worsened this run.
- 4A routing branch evaluates severity and ARR: standard downgrades are batched, while high-value critical entries are isolated for escalation.
- 5Standard downgrades post to the AE Slack channel, and an output step pages the account director via PagerDuty for high-value critical escalations.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Sales workflows
API-Usage Surge PQL Router
When an account's API call volume surges past a rolling baseline in the product DB, it qualifies the account as a product-qualified expansion lead.
Seat-Limit Approaching Upsell Alert
Fires the moment an account's active-seat count crosses 90% of its contracted limit in the product database.
Enrich new MAP steps with Salesforce deal context on creation
When a new card is added to the mutual action plan Trello board, it looks up the linked Salesforce opportunity and writes deal owner, amount, and close date onto the card…
Power-Feature Adoption Expansion Digest
Each Monday, finds accounts that started heavily using a premium or add-on feature in BigQuery, ranks them by expansion potential.
Send buyers a weekly mutual action plan health recap
Each week it reads the MAP Trello board, computes completed, on-track, and overdue steps, and emails the buyer champion a clean recap of progress and what is due next.
Escalate to the deal team when the buyer side of a MAP stalls
Detects when buyer-owned mutual action plan steps have been idle past their due date and escalates with a Slack alert to the AE plus an email summary to the account executive's…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.