Evening Scan
Run at 6 PM daily via cron. Checks all channels for responses to outreach via Chrome DevTools MCP, updates lead statuses, and sends EOD report via Telegram.
Prerequisites
agency.config.json populated (tools, CRM)
- Active leads in outreach cadence
- Chrome Beta logged in: Zoho webmail, LinkedIn, Instagram
- Chrome DevTools MCP available
Capabilities Used
inbox-scanner -- check all channels for replies via Chrome DevTools MCP
reply-analyzer -- classify response sentiment and intent (8 categories)
crm-writer -- update statuses, pause cadences
Step 1.1: Check Email Replies
SKILL: inbox-scanner
TOOL: Zoho MCP (being integrated) + Chrome DevTools MCP (Zoho webmail)
AUTH: Already signed in via Chrome Beta
mcp__chrome-devtools__navigate_page to Zoho webmail inbox
- Scan for new replies to outreach emails (since last scan)
- Extract: sender, subject, reply text, timestamp
- Match to CRM leads by email address
Step 1.2: Check LinkedIn Messages
SKILL: inbox-scanner
TOOL: Chrome DevTools MCP → LinkedIn messaging
AUTH: Already signed in via Chrome Beta
mcp__chrome-devtools__navigate_page to LinkedIn messaging
- Scan for new/unread messages from outreach contacts
- Check for accepted connection requests at invitation manager
- Extract: sender name, company, message text, timestamp
Step 1.3: Check Instagram DMs
SKILL: inbox-scanner
TOOL: Chrome DevTools MCP → Instagram DMs
AUTH: Already signed in via Chrome Beta
mcp__chrome-devtools__navigate_page to Instagram Direct inbox
- Scan for new/unread DM replies
- Extract: sender username, message text, timestamp
Step 2.1: Match Replies to CRM Leads
SKILL: crm-writer (READ)
TOOL: Google Sheets webhook
Match each reply to CRM leads by:
- Email address (exact match) for email replies
- Company name (fuzzy match) for LinkedIn/Instagram
- Contact name (fuzzy match) as fallback
Pull lead context: cadence_day, last_action, lead_status, tier, score
Step 3.1: Classify Reply Sentiment (8 Categories)
SKILL: reply-analyzer
TOOL: None (LLM classification)
Categories:
| Category |
Action |
| Positive + wants demo |
Mark DEMO_BOOKED, send cal link, pause cadence |
| Positive + interested |
Mark REPLIED, send more info, pause cadence |
| Neutral + questions |
Mark REPLIED, answer questions, pause cadence |
| Negative + not interested |
Mark NOT_INTERESTED, send polite close, pause cadence |
| Negative + angry/rude |
Mark DO_NOT_CONTACT, no further outreach |
| Out of office |
Note OOO, adjust cadence timing |
| Unsubscribe request |
Mark DO_NOT_CONTACT, remove from all sequences |
| Referral |
Mark REFERRED, follow up with referred contact |
Step 3.2: Update CRM -- Pause Cadence, Set New Status
SKILL: crm-writer (UPDATE)
TOOL: Google Sheets webhook
For each responded lead:
- Set
response_received = "Yes"
- Set
response_channel = channel
- Set
response_date = today
- Set
response_summary = summary from analyzer
- Update
lead_status based on classification
- Clear
next_action and next_action_date (pause cadence)
- If demo booked: add to calendar (if Google Calendar MCP available)
Step 3.3: EOD Report + Telegram Notification
TOOL: Telegram Bot API
Send via Telegram:
EOD SCAN -- [Date]
---
RESPONSES RECEIVED: N
- Email replies: N
- LinkedIn messages: N
- LinkedIn connections accepted: N
- Instagram DM replies: N
RESPONSE DETAILS:
1. [Company] via [Channel]: [Summary] → [Action Taken]
2. ...
DEMOS BOOKED TODAY: N
NOT INTERESTED: N
DO NOT CONTACT: N
PIPELINE UPDATE:
- Total active leads: N
- In cadence: N
- Responded (awaiting follow-up): N
- Demo booked (total): N
- Breakup sent: N
RESPONSE RATE (trailing 7 days):
- Emails sent: N → Replies: N (X%)
- LinkedIn sent: N → Replies: N (X%)
- Overall: X%
ACTION ITEMS FOR TOMORROW:
- Follow-ups due: N
- Calls scheduled: N
- New leads to process: N
Example Usage
Trigger phrases:
- "Run the evening scan"
- "Check for responses"
- "It's 6 PM, any replies?"
- "Update the pipeline with today's responses"
1---2name: evening-scan3description: End-of-day response check and pipeline update. Run at 6 PM via cron. Checks all channels for replies via Chrome DevTools MCP + Zoho MCP, updates lead statuses, pauses cadence for responded leads, sends EOD report via Telegram.4---56# Evening Scan78Run at 6 PM daily via cron. Checks all channels for responses to outreach via Chrome DevTools MCP, updates lead statuses, and sends EOD report via Telegram.910## Prerequisites1112- `agency.config.json` populated (tools, CRM)13- Active leads in outreach cadence14- Chrome Beta logged in: Zoho webmail, LinkedIn, Instagram15- Chrome DevTools MCP available1617## Capabilities Used18191. `inbox-scanner` -- check all channels for replies via Chrome DevTools MCP202. `reply-analyzer` -- classify response sentiment and intent (8 categories)213. `crm-writer` -- update statuses, pause cadences2223---2425## Step 1.1: Check Email Replies2627SKILL: `inbox-scanner`28TOOL: Zoho MCP (being integrated) + Chrome DevTools MCP (Zoho webmail)29AUTH: Already signed in via Chrome Beta30311. `mcp__chrome-devtools__navigate_page` to Zoho webmail inbox322. Scan for new replies to outreach emails (since last scan)333. Extract: sender, subject, reply text, timestamp344. Match to CRM leads by email address3536## Step 1.2: Check LinkedIn Messages3738SKILL: `inbox-scanner`39TOOL: Chrome DevTools MCP → LinkedIn messaging40AUTH: Already signed in via Chrome Beta41421. `mcp__chrome-devtools__navigate_page` to LinkedIn messaging432. Scan for new/unread messages from outreach contacts443. Check for accepted connection requests at invitation manager454. Extract: sender name, company, message text, timestamp4647## Step 1.3: Check Instagram DMs4849SKILL: `inbox-scanner`50TOOL: Chrome DevTools MCP → Instagram DMs51AUTH: Already signed in via Chrome Beta52531. `mcp__chrome-devtools__navigate_page` to Instagram Direct inbox542. Scan for new/unread DM replies553. Extract: sender username, message text, timestamp5657## Step 2.1: Match Replies to CRM Leads5859SKILL: `crm-writer` (READ)60TOOL: Google Sheets webhook6162Match each reply to CRM leads by:63- Email address (exact match) for email replies64- Company name (fuzzy match) for LinkedIn/Instagram65- Contact name (fuzzy match) as fallback6667Pull lead context: cadence_day, last_action, lead_status, tier, score6869## Step 3.1: Classify Reply Sentiment (8 Categories)7071SKILL: `reply-analyzer`72TOOL: None (LLM classification)7374Categories:75| Category | Action |76|----------|--------|77| Positive + wants demo | Mark DEMO_BOOKED, send cal link, pause cadence |78| Positive + interested | Mark REPLIED, send more info, pause cadence |79| Neutral + questions | Mark REPLIED, answer questions, pause cadence |80| Negative + not interested | Mark NOT_INTERESTED, send polite close, pause cadence |81| Negative + angry/rude | Mark DO_NOT_CONTACT, no further outreach |82| Out of office | Note OOO, adjust cadence timing |83| Unsubscribe request | Mark DO_NOT_CONTACT, remove from all sequences |84| Referral | Mark REFERRED, follow up with referred contact |8586## Step 3.2: Update CRM -- Pause Cadence, Set New Status8788SKILL: `crm-writer` (UPDATE)89TOOL: Google Sheets webhook9091For each responded lead:921. Set `response_received` = "Yes"932. Set `response_channel` = channel943. Set `response_date` = today954. Set `response_summary` = summary from analyzer965. Update `lead_status` based on classification976. Clear `next_action` and `next_action_date` (pause cadence)987. If demo booked: add to calendar (if Google Calendar MCP available)99100## Step 3.3: EOD Report + Telegram Notification101102TOOL: Telegram Bot API103104Send via Telegram:105```106EOD SCAN -- [Date]107---108RESPONSES RECEIVED: N109- Email replies: N110- LinkedIn messages: N111- LinkedIn connections accepted: N112- Instagram DM replies: N113114RESPONSE DETAILS:1151. [Company] via [Channel]: [Summary] → [Action Taken]1162. ...117118DEMOS BOOKED TODAY: N119NOT INTERESTED: N120DO NOT CONTACT: N121122PIPELINE UPDATE:123- Total active leads: N124- In cadence: N125- Responded (awaiting follow-up): N126- Demo booked (total): N127- Breakup sent: N128129RESPONSE RATE (trailing 7 days):130- Emails sent: N → Replies: N (X%)131- LinkedIn sent: N → Replies: N (X%)132- Overall: X%133134ACTION ITEMS FOR TOMORROW:135- Follow-ups due: N136- Calls scheduled: N137- New leads to process: N138```139140## Example Usage141142Trigger phrases:143- "Run the evening scan"144- "Check for responses"145- "It's 6 PM, any replies?"146- "Update the pipeline with today's responses"