call

# Call

Call management system. Every conversation, fully leveraged.

## Critical Privacy & Safety

### Data Storage (CRITICAL)
- **All call data stored locally only**: `memory/calls/`
- **No call recording** (unless user explicitly enables separately)
- **No external CRM** connected
- **No sharing** of conversation data
- User controls all data retention and deletion

### Privacy Note
Call records contain sensitive information. All data stays local and private. You control what is captured and retained.

### Data Structure
Call data stored locally:
- `memory/calls/calls.json` - Complete call records
- `memory/calls/contacts.json` - Contact history and context
- `memory/calls/commitments.json` - Commitments made/received
- `memory/calls/followups.json` - Pending follow-ups
- `memory/calls/templates.json` - Follow-up message templates

## Core Workflows

### Prepare for Call
```
User: "I have a call with Acme Corp in 30 minutes"
→ Use scripts/prep_call.py --contact "Acme Corp" --purpose "negotiate contract"
→ Pull previous calls, open commitments, relevant context
```

### Capture During Call
```
User: "Note: They need the proposal by Friday, Sarah is decision maker, follow up on pricing"
→ Use scripts/capture_fragments.py --call-id "CALL-123" --fragments "proposal by Friday, Sarah decision maker, follow up pricing"
→ Build structured notes in real-time
```

### End Call & Generate Summary
```
User: "Call is done"
→ Use scripts/end_call.py --call-id "CALL-123"
→ Generate summary: decisions, action items, commitments
```

### Track Follow-ups
```
User: "What follow-ups do I owe?"
→ Use scripts/check_followups.py
→ Show all pending commitments with deadlines
```

### Draft Follow-up Message
```
User: "Draft follow-up to Sarah"
→ Use scripts/draft_followup.py --contact "Sarah" --call-id "CALL-123"
→ Generate personalized follow-up email with specific references
```

## Module Reference
- **Call Preparation**: See [references/preparation.md](references/preparation.md)
-...