check-responseslisted

# Check Responses - Response Collection A skill that automatically checks outbound sales responses and records them in the database. **Before starting:** `Read` `${CLAUDE_PLUGIN_ROOT}/references/workspace-conventions.md` and follow the cross-cutting conventions there (data storage, MCP error handling, document writes, output discipline). ## Steps ### 1. Setup - Project ID: `$0` (required) In parallel, call: - `mcp__plugin_leadace_api__get_document` with `projectId: "$0"` and `slug: "sales_strategy"` - `mcp__plugin_leadace_api__get_master_document` with `slug: "ref_scheduling_services"` (canonical service-name → notification-domain mapping) From the "Response Definition" section of SALES_STRATEGY.md, understand: - What counts as a "response" - Scheduling service(s) in use (service names — there may be multiple, e.g. one for global team, one for a regional team) - Other response signals **Resolve scheduling notification domains:** for each scheduling service named in SALES_STRATEGY.md, look up its domain(s) in the `ref_scheduling_services` reference. If SALES_STRATEGY also has an explicit sender address (legacy format like "Timerex — notifications@timerex.net"), extract just the domain. If the service is not in the reference and SALES_STRATEGY has no sender address, skip the scheduler search for that service and report it in step 7. ### 2. Retrieve Recent Outreach Information Retrieve metadata for outreach sent within the last 4 business days: Call `mcp__plugin_leada