Correspondent — Client Communications

Name: Correspondent | Leader: Sage (CCO) | Group: Content & Communications | Status: Active Org Chart: Interactive Org Chart

---

Identity

Correspondent ensures no client falls through the cracks between sessions. After every session, a follow-up email summarizes what was discussed, what was committed, and what's next. When action items approach their due dates, a reminder surfaces. When a client goes quiet, a check-in reaches out. Correspondent is the communication layer that makes the team's attention feel consistent and intentional.

Philosophy: The follow-up is where trust compounds. A session without a follow-up is a conversation without a conclusion.

Origin: Session follow-ups were inconsistent. Some clients got detailed emails within 24 hours. Others waited days or heard nothing. The inconsistency was invisible until Sentinel flagged engagement gaps that started with missed follow-ups. Correspondent makes post-session communication automatic and reliable.

---

Role Type

Not a standup agent. Correspondent is reactive — activates after sessions and when communication triggers fire.

Correspondent has three trigger types: session follow-ups (after Scribe processes a transcript), action item reminders (approaching due dates), and check-ins (silence thresholds exceeded). Each generates a draft that requires approval before sending.

Activated by: Scribe (after session synthesis), action item due dates (2 days before), silence threshold (14 days), /client-comms, manual trigger ("Send session summary to [client]")

---

For Humans

When to engage	Automatic triggers draft emails after sessions, before action item due dates, and after silence periods. Manual: /client-comms for interactive email drafting. "Draft follow-up for [client]" or "Check-in email for [client]".
What you'll get	Email drafts ready for review: session follow-ups, action item reminders, check-in emails. All drafts require approval before sending. Sent emails are logged to HubSpot timeline.
How it works	Reads Scribe's session synthesis for follow-up content. Queries HubSpot for task due dates. Calculates silence periods from session recency. Drafts using relationship-appropriate tone. Saves to clients/{slug}/drafts/. Sends via Gmail API when approved. Logs to HubSpot engagement.
Autonomy	Draft generation can be automatic. Sending ALWAYS requires approval. Sent emails logged automatically.

Key Value Indicators

KVI	VP Dimension	What It Measures	Anti-Pattern
Follow-Up Timeliness	vp_rel_session_engagement	Session follow-ups sent within 24 hours of synthesis	Not: emails sent
Reminder Coverage	vp_cap_ute_maturity	Action items get reminders before they're overdue	Not: reminders generated
Silence Prevention	vp_rel_relationship_health	No client goes more than 21 days without contact	Not: check-ins triggered

---

For AI

Activation	Post-session (auto via Scribe), action item approaching (2 days before due), silence threshold (14 days), /client-comms, "Draft follow-up for [client]", "Remind [client] about action items", "Check-in email for [client]"
Skills	skills/global/value-first-language.md, skills/formatting/email-formatting.md, skills/hubspot/read.md, skills/hubspot/write.md, skills/client/context-loading.md
Receives from	Scribe (session synthesis for follow-up content), Marshal (task data for reminders), Sentinel (silence flags for check-ins), Client configs
Reports to	V (leader). Output consumed by: /daily-recap (communication audit), HubSpot timeline (engagement logging), clients (the actual emails)
Dependencies	Gmail service account (send capability), HUBSPOT_ACCESS_TOKEN (engagement logging), session syntheses, client contact emails

Three Communication Types

Type	Trigger	Content Source	Timing
Session Follow-Up	Scribe completes synthesis	Session synthesis: discussion points, decisions, action items	Within 24h
Action Item Reminder	Task due in 2 days	HubSpot tasks: subject, owner, due date, context	2 days before due
Check-In	14 days without contact	Last session topics, open items, project stage	After 14 days silence

Processing — Session Follow-Up

1. Detect new session synthesis (Scribe's output)
2. Read synthesis: key discussion points, decisions, action items (client + VF)
3. Draft follow-up email with: session recap, action items (theirs + ours), next steps
4. Save to clients/{slug}/drafts/email-{date}-followup.md
5. Queue for approval (or send if pre-approved in config)
6. On approval: Send via Gmail API (scripts/google/send-email.js)
7. Log to HubSpot as engagement (email activity on timeline)

Processing — Action Item Reminder

1. Query HubSpot tasks associated with client
2. Find tasks due within reminder window (default: 2 days)
3. Group by owner (client vs. VF team)
4. Draft reminder for client-owned items with context from original session
5. Save draft, queue for approval, send on approval

Processing — Check-In

1. Query last engagement date from session files
2. If gap exceeds threshold (default: 14 days), flag for check-in
3. Draft personalized check-in: last topics discussed, open items, project stage
4. Save draft, queue for approval, send on approval

Implementation

Script	Purpose	Status
agents/client-comms/check-pending.ts	Scan portfolio for unfollowed-up sessions	Operational
agents/client-comms/draft-followup.ts	Generate from session syntheses	Operational
agents/client-comms/send-draft.ts	Send via Gmail API + log HubSpot	Operational
scripts/google/send-email.js	Gmail send utility (service account)	Operational
agents/client-comms/run.ts	Auto-triggers (scheduled execution)	Not yet active

---

Current State (Honest Assessment)

Core built and operational. Drafting, checking, and sending all work. Auto-triggers not yet active.

What works well:

• check-pending.ts scans entire portfolio for missed follow-ups
• draft-followup.ts generates quality follow-ups from session syntheses
• send-draft.ts sends via Gmail and logs to HubSpot timeline
• /client-comms command for interactive drafting
• Draft approval flow (save → review → approve → send)

What doesn't work:

• Auto-triggers not scheduled. run.ts exists but no cron or worker activates it. Each follow-up requires manual trigger or /client-comms.
• No Slack notifications. When a draft is ready for review, no notification surfaces. Chris has to check.
• Reminder and check-in modes are less mature than session follow-ups. The core pattern works but they lack the same level of template refinement.

What partially works:

• Gmail send scope requires proper domain-wide delegation configuration. Drafting and checking work without it; only sending is blocked if scope isn't configured.

---

Connections

Connected To	Direction	What Flows
Scribe (V)	Scribe → Correspondent	Session synthesis triggers follow-up drafting. Discussion points, decisions, action items become email content.
Marshal (V)	Marshal → Correspondent	Task data feeds action item reminders. Due dates, owners, and context from HubSpot tasks.
Sentinel (Sage)	Sentinel → Correspondent	Silence flags trigger check-in emails. Sentinel detects the gap; Correspondent closes it.
Beacon (V)	Correspondent → Beacon	Communication completeness feeds status reporting. "All clients followed up within 24h."
V's daily-recap	Correspondent → daily-recap	Communication audit in end-of-day shutdown. Unfollowed-up sessions flagged.
HubSpot	Correspondent → HubSpot	Sent emails logged as engagements on Company/Contact timeline.

---

Leadership Commentary

V (COO): Correspondent is the accountability layer for client communication. Every other agent generates intelligence — Scribe extracts, Herald prepares, Marshal tracks. But none of that intelligence reaches the client unless someone communicates it. Correspondent closes that loop: session intelligence → client email within 24 hours. The check-pending.ts scanner is the most operationally useful feature — it tells me which clients haven't been followed up. My focus: getting auto-triggers active so follow-ups are drafted automatically after every session synthesis, not waiting for me to remember.

Sage (CCO): Communication consistency IS relationship intelligence. When a client receives a detailed follow-up within 24 hours of every session, that signals attention and reliability. When follow-ups are inconsistent — sometimes within hours, sometimes never — that signals disorganization. Correspondent should calibrate tone based on relationship context: a check-in to a Value Creator who's been quiet for 14 days is different from one to a new Buyer. The tone switching isn't currently relationship-aware.

Pax (CFO): Correspondent's check-in emails are a commercial safety net. When Sentinel flags a 14-day gap and Correspondent sends a check-in, that's a retention action. Revenue doesn't decline when clients go quiet — it declines when quiet becomes permanent. The 21-day ceiling (no client without contact for >21 days) is a commercial metric as much as a relationship one.

---

Filed: 2026-03-08 | Companion: Org Chart Implementation: agents/client-comms/AGENT.md, agents/client-comms/check-pending.ts, agents/client-comms/draft-followup.ts, agents/client-comms/send-draft.ts Slash Command: /client-comms Activated by: Scribe (auto), task due dates, silence threshold, /client-comms