Commitment Ledger

Overview

Commitment Ledger answers a question that comes up before every follow-up: who owes what, and to whom. It reads your recent conversations with an account or contact and produces a two-sided accounting. One column holds what your team promised. The other holds what they promised. A third view surfaces what is still open.

The skill draws its evidence from conversation intelligence, the same source that captures your calls and meetings. You point it at an account, a contact, or a specific set of calls. It extracts commitments by side, marks each one open, done, or unclear based on what later conversations show, and attributes every line to the meeting where the promise was made. Nothing lands in the ledger that the conversations do not support.

This is a recent-commitments view, not a full-history audit. Conversation intelligence reasons over the last few engagements, so the ledger reflects what has been said lately rather than every promise ever made. If no conversation data exists for the scope you name, the skill tells you that plainly instead of presenting an empty table as proof that no commitments exist.

What It Does

• Two-sided accounting: Separates promises your team made from promises the account made, so accountability runs in both directions.
• Source attribution: Ties every line back to the specific meeting where the commitment surfaced, giving you the receipt behind each entry.
• Status reconciliation: Marks each commitment open, done, or unclear by checking whether later conversations confirmed, completed, or contradicted it.
• Overdue flagging: Calls out the items most in need of chasing and names who owns each one.
• Flexible scope: Runs against a whole account, a single contact, or a hand-picked set of calls, resolved by ZoomInfo ID or by name.
• Honest gaps: Reports when conversation data is missing rather than reading absence as agreement.

Use Cases

Accountability Check Before a Follow-Up

You are about to email a prospect after three calls and want to lead with substance. Run Commitment Ledger on the account. It returns what you promised (a security questionnaire, a reference customer intro), what they promised (looping in their VP of Engineering, sharing their current contract terms), and which of those are still open. Your follow-up now opens with the two things they still owe you, each tied to the call where they agreed to it.

Confirming What a Prospect Still Owes You

A deal has gone quiet and you suspect the ball is in their court. Scope the ledger to the contact and add the emphasis to show just what they owe us. The output isolates their outstanding items and marks anything overdue against what was said on the last call. That gives you a clean, evidence-backed reason to re-engage without sounding like you are nagging.

Auditing Contract Promises After a Negotiation

Following a pricing and terms discussion, you need to be sure both sides remember the same commitments. Point the skill at the specific negotiation calls and add the emphasis on anything tied to the contract. It reconciles what was agreed against later conversations and flags any point where the record is unclear. You can then close the gap before it becomes a dispute.

---
name: commitment-ledger
description: Build a ledger of what we promised versus what they promised, and what is still outstanding, across the last few engagements with an account or contact. Uses conversation_intelligence as the primary source. Identify the account or contact by ZoomInfo ID (preferred) or name (triggers a lookup), or point it at specific calls. Use when someone asks "what did we commit to", "what are they supposed to send us", "what's still outstanding with this account", or wants an accountability check before a follow-up. Covers the last few engagements only, not full history.
---

# Commitment Ledger

A two-sided accounting of promises across recent conversations: ours, theirs, and what is still open.

## Prerequisites

`conversation_intelligence` requires at least one connected email or meeting source and consumes AI credits. `browse_engagements` (used to scope or pick engagements) requires an active integration and is free. If no conversation data exists, say so rather than presenting an empty ledger as "no commitments".

## Input

Provided via `$ARGUMENTS`:

- **Scope** (required) — an account (company ID or name/domain), a contact (contact ID or name + company), or specific calls to review.
- **Emphasis** (optional) — e.g. "just what they owe us", "anything tied to the contract". Shapes the output.

## Workflow

1. **Resolve scope.** Use a ZoomInfo ID directly, or resolve a name via `search_companies` / `search_contacts`. If the user wants specific calls and none are named, present a `browse_engagements` shortlist to pick from before spending credits.
2. **Extract commitments.** Run `conversation_intelligence` scoped to the account, contact, or chosen engagement. Ask it to list commitments by side (what we said we would do; what they said they would do), with status and the source meeting. Keep CI scoped to one ID per call; it sees only the last few engagements and cannot count or topic-search, so frame this as a recent-commitments ledger, not an exhaustive audit.
3. **Reconcile.** Mark each commitment open, done, or unclear based on later conversations. Flag anything overdue or contradicted. Attribute every line to a source meeting; do not list a commitment the conversation does not support.

## Output Format

### Commitment Ledger — [Account / Contact]

*Covers the last few engagements (through [date]). Not a full-history audit.*

**We owe them**
| Commitment | Made on | Status |
|------------|---------|--------|

**They owe us**
| Commitment | Made on | Status |
|------------|---------|--------|

**Outstanding / overdue** — a short list of what most needs chasing, with who owns it.

### When there is no data

If no conversation data is available for the scope, report that the ledger cannot be built from conversations and point the user to their ZoomInfo admin to confirm integration coverage.