# Keep people and context together

Recall saved conversations and record only what you know.

Canonical page: https://jobhunt.app/support/using/people-and-interviews/keep-people-with-the-role
Updated: 2026-11-16
Audience: using
Topic: People & interviews
Type: best-practice
Catalog revision: f77de0f4803debf8c5aaac1702865d976a380e994ea7f572d4e571c044d5495f
Contract SHA-256: acfda93724db1a3f53160a30bc5891f447ad14601f26b02ff4cacd7c17d0812e

## Steps

1. **Find the right person**

   Search your saved contacts and companies. If names are ambiguous, choose the right record before opening its history or making a change.

2. **Read saved conversation history**

   Open the person’s record and follow any additional history pages. Keep the saved dates and record identities; an incomplete page is not a complete history.

3. **Record what happened**

   When you ask to save a conversation, JobHunt records only the facts you provide on the selected contact. Keep when the conversation happened separate from when you recorded it. If you do not know when it happened, the agent asks or saves it as an explicitly undated note, because a recorded interaction always carries a date. Recording a conversation does not send a message.

## Expected result

Your saved history stays connected to the selected person and job-search work.

## Troubleshooting and recovery

Saving a contact does not email them or find private contact details. Check for an existing contact before adding a duplicate.

## API operations

### list_workspace_crm_v2

Read one owned CRM page. Counts and filters apply to this page; follow has_more.

- Interface: GET /api/v1/journey/list_workspace_crm_v2
- Access: read
- Destructive: no
- Availability: connected-journey
- Required permissions: read:contacts, read:companies, read:applications
- [Operation and exact schemas](https://jobhunt.app/support/operations/list_workspace_crm_v2.json)
- [Operation Markdown](https://jobhunt.app/support/operations/list_workspace_crm_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)

### 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)

## Related guides

- [Draft outreach with your agent](https://jobhunt.app/support/using/people-and-interviews/draft-outreach-with-your-agent.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.
