# Prospect Desk

Find a small number of suitable prospects and prepare outreach that a person can send.

Category inspiration: The Outbound Crew, from the supplied @unicodef1wn chart.
Cabinet treatment: New crew; keep separate from Sales Meeting Desk's meeting work.
Version: 0.1 · October 6, 2026.
Status: Published manual setup instructions with Codex text-only exercise evidence. Native imports, tools, and Bot-to-Bot handoffs remain untested.

Category-chart inspiration: [unicodef1wn’s grokbot field notes](https://github.com/unicodef1wn/grokbot-field-notes). These are original Bot Cabinet instructions inspired by the categories, not exact ports of the chart’s templates.

## Bots and jobs

| Bot | Treatment | Job |
|---|---|---|
| [Researcher](https://botcabinet.com/bots/researcher/) | Existing Cabinet Bot | Verify the approved accounts and offer-relevant facts. |
| [Lead Qualifier](../specialists/lead-qualifier.md) | Published manual role | Apply fit rules and contact restrictions. |
| [Writer](https://botcabinet.com/bots/writer/) | Existing Cabinet Bot | Draft short messages from verified facts. |
| [Outreach Coordinator](../specialists/outreach-coordinator.md) | Published manual role | Check duplicates and stage a limited, unsent batch. |

Known introductions belong in Lead Qualifier's supplied relationship notes. A title, hiring advert, or webpage visit alone does not prove buying intent. Sales Meeting Desk takes over when a meeting is booked.

## When a crew helps

Research, qualification, writing, and duplicate-contact checks matter for repeated batches. For one warm introduction, a single supplied-context draft may suffice.

## Bring these inputs

Offer, target criteria, approved account list and relationship notes, current conversations, suppression list, contact log, batch limit, and sender.

## Set up and run

1. Select only the roles this job needs. Existing role links lead to Cabinet's current setup pages; new role links contain full manual-test instructions.
2. Put each selected role in its own conversation or Bot. Paste the new role's Role instructions section, or add the task extension below to an existing role. These files are not native import archives or add-to-app links.
3. Start with the fictional first task below. Supply the same approved source records to each role that needs them. A copied handoff alone is not evidence for a factual claim.
4. Pass reviewed results in the order below. If your app lacks Bot-to-Bot handoff, copy the small handoff yourself. Do not assume a shared folder, tool connection, or group conversation creates separate security boundaries.
5. Record each actual answer and failed attempt. Review before connecting real accounts or adding a schedule. Set read-only access and service-side cost caps where available; these written limits cannot enforce a billing cap.

## Who passes what to whom

1. Researcher provides verified account records and unknowns.
2. Lead Qualifier labels fit, hold, or exclude, retaining reasons.
3. Writer drafts only for approved fit accounts.
4. Outreach Coordinator checks the newest contact log and presents unsent drafts to the person.

Use this handoff:

- Task and current version:
- Approved source records:
- Result and its status: draft, checked, or approved:
- Unresolved questions:
- Next owner and action:
- External action awaiting specific approval:

If a role cannot finish, it returns the missing input or failed attempt. The next role must not manufacture a success record.

## Task extensions for existing Bots

### Researcher

Keep the existing Bot's role and boundaries. For this crew: Verify the approved accounts and offer-relevant facts. Check a defined question against the original approved records. Return evidence, source references, and gaps. Label supplied snapshots separately from current live research. Use only the input assigned to you for this task. Return the result, supporting records, unresolved questions, and next owner. A handoff does not approve an external action.

### Writer

Keep the existing Bot's role and boundaries. For this crew: Draft short messages from verified facts. Draft for the named audience using the approved brief. Preserve meaning and claims; never invent quotations or evidence. Keep drafts unsent. Use only the input assigned to you for this task. Return the result, supporting records, unresolved questions, and next owner. A handoff does not approve an external action.

## First task

Fictional target: tutoring firms with ten or more tutors. A has twelve but opted out. B has six. C is Cedar Tutors, with eighteen tutors and no prior contact; its supplied contact is Riley. D has fifteen but is in an active sales conversation. Approved offer and sole product claim: software that sends appointment reminders. Sender: Avery. Channel: email draft in this conversation, with no email address supplied and no external sending. Batch cap: two. Draft only for eligible accounts.

## Check the result

- Excludes A and B and holds D.
- Returns only C, even though the limit permits two.
- Invents no contact address, relationship, or intent.
- All messages remain unsent and no live sequences change.

Save the app, model if shown, date, answers, actual external actions, and pass/fail/not-checked against each item. A written checklist or a favorable review does not prove a runtime pass.

## Limits for this sample

Maximum ten supplied accounts and two draft messages in the sample. No paid enrichment, outbound sending, or CRM changes.

Stop when the task finishes, a required input is missing, a tool fails, or an action needs new approval. No automatic retries. No new credentials, private connectors, external messages, purchases, publishing, or deployment are part of the sample.

## Finished output

A qualified shortlist, exclusion reasons, and a small unsent message set.


## Exercise evidence

The [collection record](../specialists/collection.json) preserves the original Codex text answer, checks, failures, limitations, and any revised attempt. These records are instruction exercises, not native-app validation. Proposed operational tests remain unrun where the record says so.