deal-desk-workflow-management

Route deal submissions to approval tiers with SLA escalation and CRM logging.

58|21|Updated May 15, 2026
One-click install
npx skills add https://github.com/t0ddc3by/claude-for-customer-success --skill deal-desk-workflow-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deal-desk-workflow-management
Source: https://github.com/t0ddc3by/claude-for-customer-success/tree/main/rev-ops/skills/deal-desk-workflow-management
Command: npx skills add https://github.com/t0ddc3by/claude-for-customer-success --skill deal-desk-workflow-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Deal Desk approval routing breaks down when deals need the right approver, complete context, and SLA-based escalation without accidentally approving or committing revenue.

Core Features & Use Cases

  • Approval routing workflow: Routes deal submissions through standard stages to the correct approval tier (standard/elevated/executive/legal/finance) based on configured thresholds.
  • Context brief assembly: Builds a Deal Desk brief from CRM fields and sub-signal outputs (discount thresholds, non-standard terms, revenue leakage, and Tier 1 churn risk signal).
  • SLA enforcement and logging: Tracks SLA deadlines (24h standard, 4h final 2 weeks of quarter), escalates on breach, creates Linear issues for auditability, and records outcomes.

Quick Start

Submit a deal for deal desk review by saying “deal desk” and include the deal link so the skill generates the context brief, routes to the correct tier, and sets the SLA-backed approval request.

Frequently Asked Questions about deal-desk-workflow-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route deal desk approvals to the correct tier based on discount thresholds?

Deal desk approval routing assigns the correct approver tier—standard, elevated, executive, legal, or finance—by reading CRM deal fields and evaluating discount thresholds alongside risk signals. It ensures deals reach the right approver without manual routing.

How does SLA monitoring work for deal desk workflows?

SLA monitoring tracks deal desk approval deadlines using standard 24-hour windows and 4-hour windows during the final two weeks of a quarter. It automatically escalates on breach and creates Linear issues to maintain auditability.

Can I use CRM governance constraints to prevent accidental revenue commitments during deal approval?

CRM governance constraints enforce G-code guardrails during deal desk workflows, running discount and risk signal sub-steps to prevent accidental approvals or revenue leakage. The workflow logs outcomes back to the CRM.

What is the best way to assemble a decision-ready context brief for deal desk submissions?

A decision-ready deal desk context brief is assembled by reading CRM deal fields and combining sub-signal outputs like discount thresholds, non-standard terms, revenue leakage, and Tier 1 churn risk signals into a single routing package.

Do I need pre-flight config validation before submitting a deal for approval routing?

Pre-flight config validation is required before deal desk submission to verify configured thresholds, governance constraints, and CRM field readiness. This ensures the workflow can correctly assign approver tiers and enforce SLA escalation rules.

How do I handle deal desk re-routes and outcome logging for non-standard terms?

Deal desk re-routes and outcome logging are handled by re-evaluating discount tiers and non-standard terms, then applying gated write actions to record the final outcome in the CRM. Linear issue creation maintains the audit trail.