Skill

Account Relationship Recap

Recap where things stand with an account from recent conversations, with a read on whether the relationship is warming, steady, or cooling, tied to evidence.

Overview

Account Relationship Recap tells you where things stand with an account and, more importantly, which direction the relationship is moving. It blends account research for deal and firmographic context with company-scoped conversation intelligence for what has actually been said recently. The result is a short, evidence-backed read you can trust before a check-in.

The skill is built for account executives and customer success managers who manage ongoing relationships and need a fast, honest picture without reopening every thread by hand. You can pass an optional lens, such as renewal risk, expansion, or post-exec-change, to frame the recap around the question you care about most. Every claim ties back to a source, whether that is a specific meeting, the account research, or CRM.

The recap reasons over the last few engagements only. Conversation intelligence cannot search by topic or count mentions, so the skill keeps it scoped to a single account and treats its output as recent signal. It decides whether the relationship is warming, steady, or cooling and says why, without asserting momentum or risk the data does not support. When no conversation data exists, it produces the research-based read and notes plainly that the trajectory call is limited.

What It Does

Trajectory call: States in one line whether the relationship is warming, steady, or cooling, with the supporting evidence attached.
Recent conversations: Summarizes what has actually been discussed lately in three to five bullets, each tied to its source meeting.
Change detection: Flags the shifts that matter, such as new or departed stakeholders, a change in responsiveness, or momentum gained or lost.
Open threads and risks: Lists what is unresolved or worth watching, drawn from the conversations rather than assumed.
Cadence anchor: Pulls the recent engagement rhythm and the gap since last contact when that framing adds to the read.
Suggested next step: Recommends a single evidence-based move, and only when the data points to one.

Use Cases

Read Before a Check-In

An account executive has a check-in tomorrow and wants to know where the relationship actually sits. The recap returns a trajectory call, three to five bullets on what has come up in recent conversations, and any open threads to close. Because each point cites its source meeting, the AE can reference specifics on the call rather than speaking in generalities.

Trajectory After an Executive Change

A customer success manager learns the account's main sponsor has moved on and wants to understand the fallout. Passing a post-exec-change lens, the skill surfaces whether new people have entered the conversation, how tone and responsiveness have shifted, and what threads the departure left open. The read makes clear whether the relationship is cooling or holding steady.

Expansion-Readiness Read

An AE eyeing an expansion wants to confirm the relationship can carry the conversation. With an expansion lens, the recap highlights warming signals, active stakeholders, and open threads that could support or stall the motion, then suggests a next step only if the evidence backs one.

Skill Definition

The raw markdown Claude uses when this skill is invoked.

---
name: account-relationship-recap
description: Recap where things stand with a company across recent conversations, with emphasis on how the relationship is evolving. Identify the account by ZoomInfo company ID (preferred) or by name or domain (triggers a lookup). Blends account_research for deal and firmographic context with company-scoped conversation_intelligence for what has actually been said recently. Use when someone asks "where are we with Acme", "how is the relationship trending", "recap our recent conversations with this account", or wants a relationship read before a check-in. Reasons over the last few engagements only.
---

# Account Relationship Recap

Where we stand with an account, read from recent conversations: the current state, and the direction it is moving.

## Prerequisites

Company-scoped `conversation_intelligence` requires at least one connected email or meeting source; `account_research` and `conversation_intelligence` consume AI credits (`browse_engagements`, used for optional cadence, is free). If no conversation data exists for the account, produce the `account_research`-based read and note that conversation context was unavailable, pointing the user to their ZoomInfo admin.

## Input

Provided via `$ARGUMENTS`:

- **Account** (required) — ZoomInfo company ID (preferred), or a name/domain to resolve via `search_companies`.
- **Lens** (optional) — e.g. "renewal risk", "expansion", "post-exec-change". Frames the recap.

## Workflow

1. **Resolve the company.** Use the ZoomInfo ID directly; otherwise resolve a name/domain via `search_companies` and confirm an ambiguous match before spending credits.
2. **Read the relationship.** Run `account_research` (deal status, history, stakeholders) and company-scoped `conversation_intelligence` in parallel. Ask CI what has been discussed recently, how sentiment and engagement have shifted, which threads are open, and whether new people have entered the conversation. Keep CI scoped to this one account; it cannot search by topic or count mentions, and sees only the last few engagements.
3. **Anchor cadence (optional).** If useful, call `browse_engagements` (company-scoped, `-chronological`) for the recent engagement cadence and the gap since last contact.
4. **Synthesize the trajectory.** Decide whether the relationship is warming, steady, or cooling, and say why with evidence. Tie every claim to a source (CI, account_research, CRM). Do not assert momentum or risk the data does not support.

## Output Format

### Where we stand — [Company]

**Trajectory** — one line: warming / steady / cooling, with the evidence in a clause.

**Recent conversations** — 3-5 bullets on what has actually been discussed lately (from CI, with source meetings).

**What's changed** — the relationship shifts that matter: new or departed stakeholders, a change in tone or responsiveness, momentum gained or lost. Each tied to evidence.

**Open threads / risks** — what is unresolved or worth watching.

**Suggested next step** — one evidence-based move (only if the data points to one).

### When there is no data

If conversation data is unavailable, give the `account_research` view and state plainly that the relationship-trajectory read is limited without connected conversation history.

Install Plugin

This skill runs via the ZoomInfo MCP plugin for Claude Code.

Get Plugin on GitHub

Created by

Rowan Bailey

Senior Director, Product

Provided by

ZoomInfo ↗

Capabilities

Trajectory read (warming, steady, or cooling) with the evidence in a clause
Recent-conversation summary drawn from company-scoped conversation intelligence
Stakeholder shifts such as new or departed people in the conversation
Open threads and risks worth watching
Optional lens to frame the recap around renewal, expansion, or an exec change
Research-based fallback when conversation data is unavailable