> ## Documentation Index
> Fetch the complete documentation index at: https://docs.connie.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Inbox Overview

> One inbox across Gmail, Outlook, LinkedIn, and WhatsApp — with AI replies, shared assignments, and saved views.

## What is the Inbox?

The Inbox is Connie's unified messaging surface. Every conversation from every channel you've connected lands here — Gmail, Outlook, LinkedIn DMs, and WhatsApp — alongside the people, deals, and pages they're related to.

It's built for two situations:

1. **Solo operators** running multi-channel outreach who don't want to swivel-chair between five tabs.
2. **Teams** who need shared visibility on who's talking to whom, with assignments and read-status sync.

<Note>
  The Inbox provides unified access across all your connected channels. Each platform has small quirks — they're called out in the channel-specific guides.
</Note>

***

## Channels

<CardGroup cols={2}>
  <Card title="Gmail" icon="google">
    Connect via Google OAuth. Full thread sync, scheduled send, attachments, and reply-chain awareness.
  </Card>

  <Card title="Outlook" icon="microsoft">
    Connect via Microsoft OAuth. Same composer and sync surface as Gmail.
  </Card>

  <Card title="LinkedIn" icon="linkedin">
    DMs and InMail through the Connie Chrome extension. Includes connection search and profile auto-link.
  </Card>

  <Card title="WhatsApp" icon="whatsapp">
    Connect via QR-code scan. Reactions, group chats, and media all supported.
  </Card>
</CardGroup>

***

## What you can do with a conversation

Each thread in the Inbox supports a full set of triage actions:

* **Read / reply / forward** with a unified composer that adapts per channel
* **Schedule send** for a future date and time
* **Draft** messages (saved per conversation, synced across tabs)
* **Snooze** via reminders that surface the thread back when needed
* **Assign** to a teammate — they get a notification, read-status stays per-user
* **Label** — apply AI-suggested labels (e.g. `interested`, `meeting requested`) or create your own
* **Star, pin, react, bookmark** with optional notes
* **Mark as spam** — moves out of your view and into the provider's spam folder when applicable

Read status is **per-user**, so a thread you've opened won't auto-mark as read for the rest of your team.

***

## AI in the Inbox

The AI copilot is wired directly into the Inbox composer.

### Reply suggestions

When a message gets auto-classified as `interested`, Connie generates a 1–3 sentence reply suggestion that appears as ghost text in the composer. Press <kbd>Tab</kbd> to accept. Suggestions expire after 24 hours so they don't go stale.

### Summarization

Open any thread and click **Summarize** for a Claude-generated digest of the conversation. Summaries are cached per message — repeated opens are free.

### Classification

Inbound messages are auto-classified using a zero-shot model. Labels with ≥50% confidence are applied automatically. The label set is configurable per workspace.

### Message actions

Quick AI actions (one-click prompts like "draft a follow-up", "extract action items", "schedule a call") run inline on the active message and post their output back into the composer.

***

## Views & search

There's no enforced default view — the Inbox is a workspace of **custom views** you build to match how your team works.

Each view is a saved filter on:

| Filter | Example |
| - | - |
| Name / email | "From anyone at acme.com" |
| Subject / content | Contains "demo" |
| Date | This week, last 30 days, custom range |
| Platform | LinkedIn-only |
| Status | Unread, replied, starred |
| Labels | Tagged `interested` |
| Assignee | Assigned to me |

Search runs across all the same fields, plus full-text search of message bodies and a fast attendee/contact lookup for tagging people into a thread.

***

## Collaboration

The Inbox is multi-user from day one.

* **Account visibility** — admins choose whether each connected account is visible to everyone, the creator only, or a specific set of users
* **Assignments** — assign a thread to a teammate; they get a notification and the assignment broadcasts to all open clients in real-time
* **Per-user read status** — opening a thread doesn't mark it read for your teammates
* **Real-time sync** — labels, assignments, reactions, and message actions all broadcast across tabs and devices

***

## Common workflows

### Build a "Hot leads" view

1. Open the Inbox sidebar and click **+ New view**
2. Filter: `Label is "interested"` AND `Status is unread`
3. Save as **Hot leads** — pin it to the top of your sidebar

Any new inbound message auto-classified as interested now lands in this view with a 1-click reply suggestion ready.

### Route inbound by team

1. Create labels for each team (`sales`, `support`, `partnerships`)
2. Build a workflow that watches `inbox.message.received` and applies a label based on content
3. Build per-team views filtered on that label

### Schedule a follow-up sequence

1. Send the first message
2. In the composer, set a reminder for 3 days
3. When the reminder fires the thread comes back into focus — write the next message or hand off to a workflow

***

## API reference

<CardGroup cols={2}>
  <Card title="Conversations" icon="comments" href="/api-reference/conversations/list-conversations">
    List, retrieve, and bulk-action conversations.
  </Card>

  <Card title="Messages" icon="message" href="/api-reference/messages/list-messages">
    Fetch message bodies, attachments, and read status.
  </Card>

  <Card title="Compose" icon="paper-plane" href="/api-reference/compose/send-email">
    Send email, start chats, manage drafts and scheduled sends.
  </Card>

  <Card title="Views & search" icon="magnifying-glass" href="/api-reference/search/search-inbox">
    Saved views, filtered search, and attendee lookup.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.