MisarReach

View saved version →

---
name: audit-autopilot-and-agent
description: Check what MisarReach autopilot and the AI sales agent have been doing, and whether they should keep running. Use when asked to review automation, autopilot, or agent behaviour.
---

# Audit autopilot and the sales agent

Automation that sends on your behalf needs periodic review — the failure mode is
silent, and it compounds.

## Steps

1. `get_autopilot_status` and `list_autopilot_runs` — what has it sent?
2. `get_sales_agent_config` and `get_sales_agent_actions` — what is the agent
   configured to do, and what did it actually do?

## Report

- Volume sent, reply rate, bounce rate, complaint rate.
- Any action you would not have taken, and why.

If bounce or complaint rates are unhealthy, recommend pausing plainly rather
than burying it. Do not call `start_autopilot` or `update_sales_agent_config`
without explicit approval.

View saved version →

---
name: build-and-qualify-a-lead-list
description: Find companies matching an ICP, enrich and verify the contacts, score them, and save a qualified list. Use when asked to find leads, build a prospect list, or research a target market in MisarReach.
---

# Build and qualify a lead list

Never send outreach to a list that has not been through verification. Unverified
addresses drive bounces, and bounce rate is what gets a sending domain blocked.

## Steps

1. **Clarify the ICP** — industry, company size, geography, job titles. Ask if
   any are missing; a vague ICP produces an expensive, useless list.
2. `discover_companies` — find matching companies.
3. `search_leads` — find contacts. This is asynchronous: poll
   `get_search_job_status` until it reports completion. Do not assume results
   are ready.
4. `enrich_lead` — fill in missing fields.
5. `verify_emails` — **mandatory before any send.** Report how many failed.
6. `score_leads` — rank by fit.
7. `create_lead_list` — save the qualified set.

## Report honestly

Say how many were found, how many survived verification, and how many were
dropped. A list that shrinks by 60% is normal and worth stating plainly — hiding
it leads to a campaign sized against numbers that were never real.

Do not start outreach here. That is `run-an-outreach-sequence`, and it needs
explicit approval.

View saved version →

---
name: review-the-sales-pipeline
description: Report deal pipeline health and recommend next actions. Use when asked about deals, pipeline, forecast, or sales performance in MisarReach.
---

# Review the sales pipeline

## Steps

1. `get_pipeline` — value and count by stage.
2. `list_deals` — find deals that have not moved recently.
3. Report: total value, distribution by stage, stalled deals, win rate.

## Recommend, then ask

Give the three highest-impact next actions, each naming a specific deal and why.

Do not call `move_deal_stage` or `update_deal` on your own. Stage changes feed
reporting and can trigger automations; the user decides when a deal has actually
moved.

View saved version →

---
name: run-an-outreach-sequence
description: Design, preview and send a multi-channel outreach sequence. Use when asked to run a campaign, start outreach, or message a lead list in MisarReach.
---

# Run an outreach sequence

`send_to_campaign` reaches real people and cannot be recalled. Everything before
it is reversible; it is not.

## Steps

1. `list_lead_lists` / `list_leads` — confirm the audience and its real size.
2. `get_channels_status` — only build steps on channels that are connected. A
   step on a disconnected channel silently never sends.
3. Draft the sequence: how many touches, on which channels, how far apart.
4. `preview_message` for **every** step, and show the user every preview.
5. Wait for explicit approval.
6. `send_to_campaign`.

## Rules

- Never call `send_to_campaign` to "test". Use `preview_message`.
- If verification has not run on this list, stop and run it first.
- If the audience is far larger than the user seems to expect, say so before
  sending rather than after.