---
name: crm-revenue-recovery
description: Finds revenue already in the CRM that is quietly going cold — overdue callbacks, stalled post-consultation records, unanswered enquiries — and nudges the responsible person with the evidence. Use when the user asks what is falling through the cracks, which deals are stalling, or where revenue is leaking.
metadata:
  version: "1.1.1"
---

# crm-revenue-recovery

> **Client-neutral reusable package.** No client names, tenant or workspace identifiers, account or
> resource IDs, customer records, credentials, or internal paths. All examples are synthetic.

| | |
|---|---|
| Live catalog name | CRM Revenue Recovery |
| Live category | CRM & Sales |
| Catalog entry | 5 |
| Internal capability ID | `CAP-CRM-04` |
| Provider | CRM + messaging (provider-neutral) |
| Availability | Candidate; validate in the active Workspace |
| Deliverable type | `limited_pilot_package` |
| Validation status | Candidate; local package validation only |
| Version | 1.1.0 |


## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant
bindings for the required inputs below; this public package supplies no client facts or authority.
Consume `ask-ollie-authority-core` for authority, `outloop-access-fallback` for recovery and
resource verification, `email-lifecycle-core` for recipients, approvals and stored-copy delivery
verification, and the bootstrapper Runtime Contract for ownership, scheduling and completion.
These owners govern execution; this Skill does not implement a competing runtime.

Select the relevant expertise below for the requested outcome. Runtime governs combining Skills,
partial use and completing missing steps with other authorized capabilities. This Skill's domain
scope does not limit the Operator's wider authorized task. Preserve domain safety restrictions.
Verify findings against source evidence and read back any resulting artifact or authorized change.

## Business outcome

Committed follow-ups actually happen, because the person who promised one is reminded while the deal is still alive.

## Operating modes

Read · Analyze · Draft · Notify with approval

## Prerequisites — what must be true before this runs

- Workspace Context
- Approved CRM and messaging grants
- Written recovery rules and an owner roster

## Required inputs

| Input | Source |
|---|---|
| Approved CRM instance and module scope | Workspace configuration |
| Recovery rules — what counts as overdue, per stage | Required |
| Owner roster and their delivery channel | Required |
| Escalation tiers | Configuration |
| Named approver for the pilot period | Configuration |

## It nudges people, it does not touch records

This workflow is read-only against the CRM. It never updates a status, never reschedules a callback, and never
writes a reason. It surfaces the commitment and the person who made it. The human closes the loop.

## A commitment can live in free text

Real follow-up promises are often written into a note rather than a date field, and a subform's date column is
frequently the log date rather than the promised callback date. Parse both, and say which source each finding came
from so the owner can judge it.

## Never message the end customer

Delivery is to the internal owner only. Contacting the client's customer directly is a different capability with a
different consent posture and is out of scope permanently.

## Action classification

| Action class | This workflow |
|---|---|
| Read | Records, stage history, follow-up commitments in structured and free-text fields, last-contact timestamps |
| Analyze | Overdue-commitment detection, evidence-based service-level breach, stage aging, recoverability scoring |
| Draft | A per-owner nudge with the record reference, what was promised, and when |
| Notify with approval | Delivers the nudge to the owner's channel. Never contacts the end customer |
| Destructive | None. Never writes to the CRM, never reschedules, never closes a record |

## Approval and delivery

The Operator applies Authority Core and the active Workspace approval policy to any requested
mutation. Email Lifecycle owns recipient classification, sending and stored-copy verification.
The action table defines this capability's domain scope; it grants no permission by itself.

## Expected output

A per-owner nudge list with evidence, an escalation summary, and a recovery-value estimate for the period.

## Synthetic placeholders used in this package

These are illustrative only. Real values come from the client's own workspace configuration and are
never written back into this package.

| Placeholder | Meaning |
|---|---|
| `CRM_MODULE_PLACEHOLDER` | Audited module |
| `OWNER_PLACEHOLDER` | Record owner |
| `CHANNEL_PLACEHOLDER` | Internal delivery channel |