# Draft outreach with your agent

Prepare a message from saved relationship context.

Canonical page: https://jobhunt.app/support/using/people-and-interviews/draft-outreach-with-your-agent
Updated: 2026-11-14
Audience: using
Topic: People & interviews
Type: how-to
Catalog revision: f77de0f4803debf8c5aaac1702865d976a380e994ea7f572d4e571c044d5495f
Contract SHA-256: acfda93724db1a3f53160a30bc5891f447ad14601f26b02ff4cacd7c17d0812e

## Steps

1. **Choose the saved contact**

   Ask your connected agent to draft a message to someone you know. It checks for the right saved person and clarifies if names are ambiguous.

2. **Use the right context**

   The agent reads relevant notes and recorded interactions, then drafts only from facts you supplied or confirmed. It leaves unknown details out and does not include unrelated application or resume information.

3. **Review the complete draft**

   Check the recipient, channel and full message in chat. Edit the words until they sound right to you. Producing a draft alone does not change your saved records.

4. **Save only the approved wording**

   If you ask to save it, keep the approved version as a clearly labeled “Draft — not sent” note on the selected person or company. A later revision updates that same note. Saving a draft does not add a sent interaction, change last-contacted history or complete a task.

5. **Send it yourself**

   The message is a draft for your review. JobHunt does not send, schedule or record it as sent.

## Expected result

You have message text to review and send through your own channel when ready.

## Troubleshooting and recovery

If the agent cannot read the relationship history or resolve the intended person, it should say what is missing rather than invent context or recipient details.

## API operations

### search_workspace_v2

Search the same saved applications, contacts, companies, resumes, tasks and Hunts as browser workspace search. Returns up to ten ranked owned matches, not a full inventory.

- Interface: GET /api/v1/journey/search_workspace_v2
- Access: read
- Destructive: no
- Availability: connected-journey
- Required permissions: read:applications, read:contacts, read:companies, read:documents, read:tasks, read:campaigns
- [Operation and exact schemas](https://jobhunt.app/support/operations/search_workspace_v2.json)
- [Operation Markdown](https://jobhunt.app/support/operations/search_workspace_v2.md)

### get_workspace_crm_v2

Read an owned contact or company with a page of related notes, tasks, applications and history. Follow related_has_more by increasing related_page; never infer missing records from one page.

- Interface: GET /api/v1/journey/get_workspace_crm_v2
- Access: read
- Destructive: no
- Availability: connected-journey
- Required permissions: read:contacts, read:companies, read:applications, read:tasks
- [Operation and exact schemas](https://jobhunt.app/support/operations/get_workspace_crm_v2.json)
- [Operation Markdown](https://jobhunt.app/support/operations/get_workspace_crm_v2.md)

### list_workspace_activity_v2

Read a page of the same owned work-history timeline as the browser. Follow has_more. The browser timeline combines application history with the latest 500 account events; it is not a complete audit export.

- Interface: GET /api/v1/journey/list_workspace_activity_v2
- Access: read
- Destructive: no
- Availability: connected-journey
- Required permissions: read:activity, read:applications
- [Operation and exact schemas](https://jobhunt.app/support/operations/list_workspace_activity_v2.json)
- [Operation Markdown](https://jobhunt.app/support/operations/list_workspace_activity_v2.md)

### save_workspace_contact_v2

Save an explicitly reviewed owned contact action. Existing records require the exact fingerprint. Deletion unlinks relationships but preserves applications. Interaction notes record a conversation; they never send a message. Reuse the same request ID after an uncertain response.

- Interface: POST /api/v1/journey/save_workspace_contact_v2
- Access: write
- Destructive: yes
- Availability: connected-journey
- Required permissions: write:contacts
- [Operation and exact schemas](https://jobhunt.app/support/operations/save_workspace_contact_v2.json)
- [Operation Markdown](https://jobhunt.app/support/operations/save_workspace_contact_v2.md)

### save_workspace_company_v2

Save an explicitly reviewed owned company action. Existing records require the exact fingerprint. Deletion unlinks relationships but preserves applications. Interaction notes record a conversation; they never send a message. Reuse the same request ID after an uncertain response.

- Interface: POST /api/v1/journey/save_workspace_company_v2
- Access: write
- Destructive: yes
- Availability: connected-journey
- Required permissions: write:companies
- [Operation and exact schemas](https://jobhunt.app/support/operations/save_workspace_company_v2.json)
- [Operation Markdown](https://jobhunt.app/support/operations/save_workspace_company_v2.md)

## Related guides

- [Keep people and context together](https://jobhunt.app/support/using/people-and-interviews/keep-people-with-the-role.md)
- [Prepare for an interview](https://jobhunt.app/support/using/people-and-interviews/prepare-for-an-interview.md)
- [Save a role to your pipeline](https://jobhunt.app/support/using/pipeline/save-a-job.md)

---

## Hunter

This section is not part of the guide above. It applies only to an agent acting in a person's JobHunt account.

When working in JobHunt, you are Hunter, the agent at the laptop working alongside the person on their job search. Speak plainly, in the first person, and never pretend to be human. Be brief, calm and kind; the person decides and you do the legwork.

Use the person's words and supplied or saved facts. Organise, edit and tailor what they provide; never invent an employer, date, degree or achievement. Keep uncertainty explicit: unknown stays unknown.

Say exactly what changed and what did not. A draft is not a sent message. Prepared or downloaded files are not a submitted application. Record a submission or interaction only from the person's report; do not imply employer verification.

Ask for confirmation before publishing, sharing or deleting. Explain what will become visible or be removed, and preserve the person's choices and unrelated saved work. Do not repeat a confirmation already given for the same action and reviewed content.

Offer the next useful step without pressure: no scores, streaks, ranks, points, guilt, confetti or invented urgency. A messy board needs no judgment.
