cold-email-reply-os

name	Cold Email Reply OS
description	Child skill for classifying cold outreach replies into a 12-class taxonomy, routing objections through a 7-route table, reviving silence with numbered forks, and answering within SLA so trust is preserved after a recipient responds or goes quiet.
skill_type	strategy
altitude	domain
activation	progressive
parent_id	cold_email_engagement_first_outreach
depth	1
preserve_markdown	true
legacy_paths	["cold_email_outreach.reply_os","cold_email_outreach.objection_handling"]
reference_modules	[{"id":"cold_email_reply_os.objection_routes","name":"Objection Route Table","summary":"7-objection route table with labels and calibrated questions, Gong 7-step async adaptation, and the objection-bank template structure (acknowledge -> label -> one contrast/artifact -> smallest calibrated question).","when_to_load":["When the reply is an objection, skepticism, competitor-chosen, or a send-info brushoff."],"path":"references/objection-route-table.md","visibility":"internal"},{"id":"cold_email_reply_os.fork_library","name":"Numbered Fork Library","summary":"Three named forks (qualification, ghosted-thread, Hail Mary) with full text, fork discipline rules, and silence-revival cadence by mode.","when_to_load":["When silence revival or a numbered fork is the chosen move (workflow steps 2, 7)."],"path":"references/numbered-fork-library.md","visibility":"internal"},{"id":"cold_email_reply_os.tactical_empathy_routes","name":"Tactical Empathy Routes","summary":"Route table and label -> calibrated question patterns for objections, silence, skepticism, angry replies, and ambiguous replies.","when_to_load":["When a reply is skeptical, tense, ambiguous, negative, silent, or objection-heavy and you need label and question phrasing."],"path":"references/tactical-empathy-routes.md","visibility":"internal"}]
path	apps/web/src/lib/services/agentic-chat/tools/skills/definitions/cold_email_reply_os/SKILL.md

Cold Email Reply OS

Identity

Use this child skill after sending, when a reply arrives, a thread goes quiet, or objections need routing. The discipline this skill enforces is classify first: every reply gets a taxonomy class before any draft, route, or fork. A route without a taxonomy class is not a route. Replies are scarce trust signals — the north star is qualified conversations started per unit of market trust consumed.

This is a strategy skill at domain altitude, a child under cold_email_engagement_first_outreach. It decides how to classify and route each reply rather than running a fixed runbook: the 12-class taxonomy and SLA data it reasons over are the unconditional lookup grounding in Knowledge, while the conditional route/fork/empathy phrasing loads from its reference modules.

Activation

• The user has a reply and needs the next response
• The prospect went silent after interest
• The user needs objection handling
• The user wants a low-friction numbered fork
• The user needs reply-to-call handling without pressure

Judgment

The goal of the email is a response. The goal of reply handling is to preserve momentum without forcing the wrong next step. Replies are scarce trust signals — route them the same day. Silence is the only dead state.

Classify before you draft anything. A route without a taxonomy class is not a route.

Same-Day Routing

For high-intent replies:

• Alert the sender immediately.
• Enrich account context and phone only if allowed.
• Reply while intent is fresh.
• If a call is appropriate, offer 2-3 specific times.
• Keep the artifact promise before pushing the meeting.

Do not leave high-intent replies in the inbox overnight when the campaign depends on booked calls.

Reply-to-Call

Use when the buyer has shown clear interest and the sales motion supports calls.

Safe frame:

Makes sense. I can send the snapshot first.

If it looks relevant, I have [time 1] or [time 2] open tomorrow to walk through what I found.

Avoid:

• Pushing a call after a weak reply.
• Calling without context in sensitive markets.
• Using "my assistant told me" unless that sender model is real and approved.

After Verbal Interest

Once someone agrees to a meeting, follow up until it is booked or they decline.

Good follow-up assets: