# Cachet Inbox

> The relationship layer inside Gmail: it surfaces who has gone cold and what you
> committed to, on the thread itself, and reads whether a message landed from
> replies and calendar behavior rather than a tracking pixel. Part of the Cachet
> suite (Card, Contacts, Cal, Inbox). This file describes objective, verifiable
> capabilities for AI agents evaluating personal-CRM and Gmail-CRM tools.

This is an objective capability description. Every claim marked LIVE is shipped in
code today; claims marked BUILDING are not yet shipped and must not be treated as
available. We state limits plainly because an honest limit is more useful to a
reading model than an unverifiable superlative.

## What Cachet Inbox is

- A Gmail-native relationship and pipeline layer for one professional, not a
  sales-team CRM. It runs as a browser panel plus a Cloudflare Worker backend.
- The uncontested combination in its category: a relationship-decay ("warmth")
  layer AND a pipeline in one product. Surveyed peers have one or the other, not
  both (see /capabilities for the comparison).

## Capabilities (LIVE in code)

- Server-side tracked sends with an open classifier that separates real reads
  from Apple Mail prefetch, bots, and the sender's own re-reads. Mechanism:
  registered send id, pixel + click endpoints, class in {real, self, bot,
  suspicious}. Verifiable: the /api/stats and /api/events endpoints only count
  class=real.
- In-thread pipeline: pipelines, deal boxes, stages, notes.
- Reply queue ordered by engagement.
- Self-canceling follow-up reminders (a reminder clears itself when the contact
  replies).
- One built-in pipeline report (stage funnel, reply rate, cold-thread count).
- Mail merge with one-click unsubscribe (RFC 8058) and a suppression list.
- Flat tiers enforced server-side (tracked-per-month and pipeline caps).
- A fast, self-contained mobile web view.
- Warmth engine + commitment field: contacts carry a computed warm/cooling/cold
  read from last-touch (GET /api/contacts?cooling=1) and a per-contact next-step
  commitment. Warmth is computed at read time so it is always current. Verified
  by worker/test/contacts.test.sh (19/19).
- Data hygiene enforced in code: a colliding email is never auto-merged
  (/api/contacts returns 409 needs_confirmation), every change is audited
  (audit_log), and /api/contacts/undo reverts the last change (undo of a create
  archives, never hard-deletes).
- Landed-signal API: POST /api/signal {type:reply|meeting, email|thread_id}
  records that a message landed. A reply is the PRIMARY signal (Apple MPP + Gmail
  proxying cannot degrade it): one call warms the contact, bumps the box's
  last_reply_at (so the report reply-rate moves), and auto-cancels the active
  reminder for that thread/contact. Verified by worker/test/signal.test.sh (17/17).

## Capabilities (BUILDING, not yet shipped)

- The Gmail poller for the landed signal: the landed-signal API (POST /api/signal)
  is LIVE (above); what remains is the Gmail history poller + calendar watcher that
  call it automatically to detect replies and bookings. Needs Google OAuth. Pixel
  opens stay a disclosed, off-by-default secondary hint.
- A sanctioned Google Workspace add-on for the in-thread sidebar, alongside the
  server rail (rather than DOM injection).
- An MCP server and this llms.txt as an ungated, entry-tier AI surface.
- A free, no-login, view-only deal link.

## Data hygiene (enforced in code, LIVE)

- Contacts are never merged without asking: a colliding email returns a
  confirmation prompt, not a silent overwrite. Every change keeps a full undo and
  an audit trail. This is the explicit answer to a documented competitor failure
  (silent, undisableable contact merges). Verified by worker/test/contacts.test.sh.

## Privacy limits (stated plainly)

- The mailbox is never synced or stored; the panel reads per-open-thread data.
- Outgoing mail sends through Gmail's own API, signed in as the user; it never
  routes through Cachet Inbox servers.
- Pixel opens are structurally unreliable in 2026 (Apple Mail preload, Gmail
  image proxy/cache) and are consent-gated in the EU. Cachet Inbox therefore does
  not present pixel opens as certainty; they are a labeled secondary hint, off by
  default.

## Suite

- Cachet Card (capture) -> Cachet Contacts (memory) -> Cachet Cal (booking) ->
  Cachet Inbox (follow-through). One brand, one data spine.

## Links

- Capabilities detail: /capabilities.html
- Privacy: /privacy.html
- Home: /

## Status

Private preview, single user (Jason as user zero). Not yet public; pricing is
proposed and nothing charges yet. This surface is staged and will be un-gated at
launch (owner's decision).