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

# Inbox

> Smart, AI-categorized inbox for sales replies — route to an agent or a teammate, never miss a hot lead

The **Inbox** is your sales reply hub. Connect Gmail or Outlook once — every reply is auto-categorized, linked to its contact and campaign, and (optionally) auto-routed to an agent or teammate.

You stay in control. Komo drafts; you approve before send.

## Three-pane layout

| Pane          | What it shows                                         |
| ------------- | ----------------------------------------------------- |
| **Left rail** | Accounts, categories, Archived folder                 |
| **Middle**    | Email list, filtered by category and account          |
| **Right**     | Open thread — conversation, contact context, reply UI |

Category counts update in real time.

## Connect your inbox

<Steps>
  <Step title="Open Inbox Settings">
    Gear icon top-right, or `/inbox/settings`.
  </Step>

  <Step title="Click Connect">
    Pick **Gmail** or **Outlook** → OAuth.
  </Step>

  <Step title="Authorize">
    Komo stores only short-lived OAuth tokens — never plain-text credentials.
  </Step>

  <Step title="Optional: connect more accounts">
    Many teams connect 2–3 inboxes per rep to distribute send volume and warming.
  </Step>
</Steps>

Disconnect or pause any inbox from the same page.

## Eight default categories

| Category                | Means                                                        | Example subjects             |
| ----------------------- | ------------------------------------------------------------ | ---------------------------- |
| **Hot Lead**            | High-intent inbound, signal-triggered lead, or warm referral | "Inbound from your website"  |
| **Interested**          | Engaging positively, wants to continue                       | "Tell me more about pricing" |
| **Meeting Request**     | Scheduling, rescheduling, confirming                         | "Can we meet next week?"     |
| **Objection**           | Pricing, fit, timing, security, competitor concern           | "Too expensive for us"       |
| **Renewal & Expansion** | Existing customer renewing or upselling                      | "Renewal coming up"          |
| **Not Now**             | Pause or follow up later                                     | "Circle back next quarter"   |
| **Unsubscribe**         | Remove from outreach                                         | "Stop emailing me"           |
| **Other**               | Doesn't fit primary categories                               | "Quick question"             |

Re-classify any thread manually — Komo learns from corrections.

Create **custom categories** from Inbox Settings for verticals (`legal_review`, `partner_intro`, etc.).

## Routing rules

Map a category to an agent or workflow that runs automatically.

<Steps>
  <Step title="Inbox Settings → Routing rules → Add">
    Click **Add routing rule**.
  </Step>

  <Step title="Pick the trigger category">
    e.g. `Meeting Request`.
  </Step>

  <Step title="Pick the execution target">
    **Agent** (custom or default) or **Workflow** (saved [playbook](/product/playbooks)).
  </Step>

  <Step title="Save">
    Live immediately. Future replies in that category trigger the agent. Drafted responses appear for you to approve, edit, or send.
  </Step>
</Steps>

### Common patterns

* **Interested → reply-drafting agent** — "great, let me share more" + calendar link
* **Meeting Request → scheduling agent** — propose times via Calendar availability
* **Objection → objection-handler agent** — draft pricing/security/timing response
* **Unsubscribe → suppression workflow** — remove from all campaigns + add to do-not-contact
* **Not Now → reminder workflow** — schedule follow-up touch in X weeks
* **Hot Lead → notification workflow** — Slack DM to the owning rep

## Compose

Top-right **Compose** opens a new email dialog — sender, recipient, subject, body. Useful for one-off outbound outside a campaign.

## Thread view

Right pane shows:

* Full conversation
* Linked [Contact](/product/contacts) and parent [Account](/product/accounts)
* Campaign context (if it came from one)
* Inline reply composer
* Actions: archive, change category, mark read, link to different contact

Replies go out from the original sender, preserving threading.

## Archive vs. delete

* **Archive** — out of active view, keeps thread + contact link + analytics. Default for "done."
* **Delete** — removes Komo's copy entirely. Use rarely.

## Connected to

[Campaigns](/product/campaigns) (produce replies) · [Contacts](/product/contacts) (timeline entries) · [Signals](/product/signals) (monitored-lead replies) · [Playbooks](/product/playbooks) (triggered by routing) · [New Task](/product/new-task) (agent can answer "what objections came up this week?")

## Tips

<Tip>
  Set up routing rules for **Hot Lead, Meeting Request, Unsubscribe** before your first campaign. The others can stay manual until volume justifies automation.
</Tip>

<Tip>
  Use custom categories for vertical motions. Default 8 cover B2B SaaS — verticals win by extending.
</Tip>

<Tip>
  Re-classify misrouted threads weekly. After a few weeks, expect 95%+ accuracy on your motion.
</Tip>