# Email Views — Structure Example
# TheVibeFounder · Session 29 · Creative Series 2

## What this is

An example of how to structure email views so Claude can parse,
categorize, and act on your inbox. Download this, fill in your
own emails, and upload it back to your Claude project.

---

## Format

Each email block follows this structure:

```
---
id: [unique id]
from: [sender name] <email>
to: [your email]
date: [YYYY-MM-DD HH:MM]
subject: [subject line]
labels: [comma-separated tags]
status: [unread | read | replied | waiting | archived]
priority: [high | normal | low]
thread_id: [group related emails]
---
[body text]
---
action_needed: [yes | no]
next_step: [what to do next]
draft_reply: [optional — Claude can fill this in]
```

---

## Example emails

```
---
id: em-001
from: Sarah Chen <sarah@ottoai.com>
to: hello@thevibefounder.com
date: 2026-04-08 14:22
subject: Partnership opportunity — Otto x TVF
labels: brand-deal, inbound, otto
status: read
priority: high
thread_id: thread-otto-001
---
Hey!

Loved your last Build Live session. We're building Otto — an AI
assistant for small teams — and think there's a natural fit with
your audience.

Would you be open to exploring a sponsored session or integration?
We're flexible on format. Budget is approved.

Happy to chat whenever works.

Sarah
Head of Partnerships, Otto AI
---
action_needed: yes
next_step: Reply with rate card and available session slots
draft_reply: |
  Sarah,

  Thanks for reaching out. Otto looks solid — the small team angle
  maps well to what our builders care about.

  I can do a Build Live integration where I use Otto in a real
  session. Not a pitch — actual usage. Here's what that looks like:

  - Live build session mention + demo: $X,XXX
  - Optional carousel recap: $X,XXX
  - Bundle: $XX,XXX

  Next available session: Apr 27. Want to jump on a 10-min call
  this week to scope it?

  [Name]
```

```
---
id: em-002
from: Dev Patel <dev@polarsh.com>
to: hello@thevibefounder.com
date: 2026-04-09 09:15
subject: Re: Polar.sh billing integration
labels: tool, partner, polar
status: replied
priority: normal
thread_id: thread-polar-002
---
Here's the API key and docs link you asked for.
Let me know if you hit anything weird during the session.

Rooting for you Sunday.

Dev
---
action_needed: no
next_step: Use in session 29. Follow up post-session with feedback.
draft_reply:
```

```
---
id: em-003
from: Priya Sharma <priya@gmail.com>
to: hello@thevibefounder.com
date: 2026-04-10 11:30
subject: Application — Build community
labels: community, application, whatsapp
status: unread
priority: normal
thread_id: thread-community-003
---
Hi,

I'm a product designer at a Series A startup in Bangalore. I've
been following Build Live since session 12. I want to join the
WhatsApp community.

I'm currently building an AI tool for design handoffs and would
love to learn from how you approach live builds.

Thanks,
Priya
---
action_needed: yes
next_step: Review application. If approved, send WhatsApp invite link.
draft_reply: |
  Priya,

  Thanks for applying. Design handoffs + AI is a solid space.

  You're in. Here's the WhatsApp link: [LINK]

  Ground rules: share what you build, help others, no lurking.
  See you Sunday.

  [Name]
```

---

## How to use

1. Download this file
2. Replace the example emails with your real ones (or keep the format)
3. Upload to your Claude project
4. Ask Claude: "What needs a reply?" or "Draft responses for high priority"
5. Claude will parse the structure and act on each email
6. Update `status` and `next_step` as you go

---

## Tips

- Keep `thread_id` consistent so Claude groups conversations
- Use `labels` for filtering: "show me all brand-deal emails"
- The `draft_reply` field is optional — Claude fills it if empty
- Add new emails at the bottom. Claude reads top-to-bottom.

---

## Session 29 — Creative Series 2
Built live. No edits. TheVibeFounder.