Reply triage & response drafting

# Reply triage & response drafting

You have the "lead-scorer" MCP server connected (Lead Scorer CRM, authenticated with Lead Scorer OAuth at the endpoint configured by the installed plugin). Use its tools for CRM reads and writes. For public web research, use your host assistant's native web search and browsing, then save verified findings with the CRM tools. Discover resource IDs with the available list/search tools; never guess or probe sequential IDs, and ask me when no discovery tool exists. Never invent data: if a tool result is empty, say so. An API key is only a manual fallback for clients without OAuth support.

> **Context first.** Call `get_my_memory`, then `compile_context_pack` when a lead or campaign is in scope. Treat personal memory as user-owned context, not verified public CRM data. If my memory is empty, ask me the three questions you actually need answered, then continue.

## Goal
I paste a reply (or point you at a lead). You pull the context, classify it, and draft my answer. You never send.

## Steps
1. **Context.** `get_lead` for the person; resolve an unknown campaign with `list_campaigns`, then use `get_campaign` + `list_campaign_actions` for what we actually sent them and when. Read our own message before answering theirs: half of bad replies come from forgetting what we said.
2. **Read and classify.** Use `list_inbox_conversations` to find the channel, campaign and account, then `get_inbox_conversation` to read the full history. Use `list_inbox_replies` for reply qualifications and sequence state. A courtesy-only reply (`no_positioning`) differs from `neutral` (unclear): never treat an invitation to talk, a phone number, a confidential exchange or a meeting proposal as a courtesy. `qualify_inbox_reply` records the user's assessment and keeps the sequence paused. Resume with `resume_inbox_sequence` only when the user explicitly requests that prospect's sequence to continue; resuming an active campaign permits its already-approved steps to send. Their remaining delay freezes during the reply pause; it is restored without removing any pre-existing lateness. A later reply pauses again. Never resume a refusal or DNC.
   Classify into one bucket:
   - **Interested**: wants to talk or asks a real question
   - **Timing**: relevant but not now ("Q1", "after the migration")
   - **Wrong person**: redirect offered or implied
   - **Objection**: price, incumbent, built in-house, no budget
   - **No**: explicit refusal or unsubscribe
   - **Auto**: out of office, bounce, no-reply noise
3. **Draft the response** by bucket:
   - Interested → confirm one concrete next step, propose two time slots, no re-pitch.
   - Timing → accept the timing without arguing, ask for the trigger to watch, propose one dated follow-up.
   - Wrong person → ask for the name, and thank them properly; that is the whole message.
   - Objection → answer the actual objection in one paragraph, no defensive list of features, close with a question about their situation.
   - No → one line, gracious, no rebuttal. Then stop.
   - Auto → no reply; note the return date.
4. **Record.** `add_tags_to_lead` with the bucket so the pipeline reflects reality. Use `update_campaign_action_draft` if a queued follow-up must be replaced by the response.
5. **Report.** Bucket counts, the drafts, and every lead that must exit the sequence today.

## Hard rules
- One question per reply. Two questions is an interview, and it stalls.
- Never re-sequence someone who said no. Never argue with a no.
- Never claim we already spoke, or that they asked for something they did not.