[{"data":1,"prerenderedAt":1162},["ShallowReactive",2],{"search":3,"content-guide\u002Fteam-inbox":442,"surround-\u002Fguide\u002Fteam-inbox":1157},[4,8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156,160,164,168,172,176,180,184,188,192,196,200,204,208,212,216,220,224,228,232,236,240,244,248,252,256,260,264,268,272,276,280,284,288,292,296,300,304,308,312,316,320,323,327,331,335,339,343,347,351,355,359,363,367,371,375,379,383,387,391,395,399,403,407,411,415,419,423,426,430,434,438],{"path":5,"title":6,"description":7},"\u002Fguide","Guide","Product guides for Owlat — a modular, self-hosted email platform. Learn how to send campaigns, run a personal mailbox, manage a team inbox, and more.",{"path":9,"title":10,"description":11},"\u002Fguide\u002Fgetting-started","Welcome to Owlat","Set up your Owlat workspace and send your first email — from deploying the stack to verifying a domain, building your audience, and launching a campaign.",{"path":13,"title":14,"description":15},"\u002Fguide\u002Fcontact-properties","Contact Properties","Custom fields that extend built-in contact data with your own values for segmentation.",{"path":17,"title":18,"description":19},"\u002Fguide\u002Ftopics","Topics","Topics are explicit audience groups you manage by hand — ideal for opt-in subscribers, imported cohorts, and organized contact buckets you target with campaigns.",{"path":21,"title":22,"description":23},"\u002Fguide\u002Fsegments","Segments","Build dynamic, rule-based contact groups from properties, email activity, and topic membership, re-evaluated from current data each time they're used.",{"path":25,"title":26,"description":27},"\u002Fguide\u002Fforms","Forms","Form Endpoints collect new contacts from your website or landing pages by exposing a public endpoint that accepts submissions and feeds them into a topic.",{"path":29,"title":30,"description":31},"\u002Fguide\u002Fcampaigns","Campaigns & Reporting","Build and send marketing campaigns to a topic or segment with the five-step wizard, optional A\u002FB testing, and full delivery reporting.",{"path":33,"title":34,"description":35},"\u002Fguide\u002Fab-testing","A\u002FB Testing","Compare two variants of a campaign on a test group, then automatically or manually send the winning version to the rest of your audience.",{"path":37,"title":38,"description":39},"\u002Fguide\u002Fautomations","Automations","Send emails automatically based on triggers, delays, and conditions — build welcome series, trial flows, and follow-ups once and let Owlat run them.",{"path":41,"title":42,"description":43},"\u002Fguide\u002Ftransactional","Transactional Emails","One-to-one emails your application triggers in response to a user action — password resets, order confirmations, welcome emails, and similar notifications.",{"path":45,"title":46,"description":47},"\u002Fguide\u002Fcreate-campaign","Create a Campaign","Walk through Owlat's five-step campaign wizard: Basics, Audience, Content, A\u002FB Test, and Review & Send.",{"path":49,"title":50,"description":51},"\u002Fguide\u002Fsend-campaign","Send & Monitor a Campaign","How to send your campaign and track its performance with real-time metrics.",{"path":53,"title":54,"description":55},"\u002Fguide\u002Fquick-start","Quick Start","The fastest path from a blank Owlat workspace to a live email campaign, from your first template through sending and reviewing results.",{"path":57,"title":58,"description":59},"\u002Fguide\u002Ftransactional-setup","Transactional Email Setup","Set up and send transactional emails like password resets and order confirmations via the Owlat API and SDKs.",{"path":61,"title":62,"description":63},"\u002Fguide\u002Fdeliverability","Deliverability","Verify sending domains, manage your blocklist, monitor sending reputation, and stay compliant so your emails reach the inbox.",{"path":65,"title":66,"description":67},"\u002Fguide\u002Fapi-keys-webhooks","API Keys & Webhooks","Create API keys for programmatic access and set up outbound webhooks to receive real-time notifications for email and contact events.",{"path":69,"title":70,"description":71},"\u002Fguide\u002Ffeature-flags","Feature flags","Owlat is modular — every feature listed in this guide can be turned on or off. This page is the user-facing overview of how to do it.",{"path":73,"title":74,"description":75},"\u002Fguide\u002Fteam-permissions","Team & Permissions","Use role-based access to control what each member of your organization can do, with Owner, Admin, and Editor roles.",{"path":77,"title":78,"description":79},"\u002Fguide\u002Faudit-logs","Audit Logs","A chronological record of significant actions in your Owlat organization, so you can see who did what and when.",{"path":81,"title":82,"description":83},"\u002Fguide\u002Fshare-links","Share Links","Create temporary preview links to share email designs with stakeholders who don't have dashboard access.",{"path":85,"title":86,"description":87},"\u002Fguide\u002Fpostbox","Postbox — Personal Email","Per-user mailboxes with a webmail interface and native IMAP\u002FSMTP support. Run your own Gmail-equivalent personal mailbox on your Owlat instance.",{"path":89,"title":90,"description":91},"\u002Fguide\u002Fmigrate-from-google","Migrate from Google","Import your full Gmail history into Owlat over IMAP, and let your AI assistant learn from every imported conversation.",{"path":93,"title":94,"description":95},"\u002Fguide\u002Fteam-inbox","Team Inbox","Triage inbound email as a team: read AI-classified threads, approve, edit or reject agent drafts, work the review queue, and manage quarantine.",{"path":97,"title":98,"description":99},"\u002Fguide\u002Femail-editor","Email Editor","A block-based visual editor for building responsive emails that render consistently across desktop, mobile, Outlook, Gmail, and Apple Mail.",{"path":101,"title":102,"description":103},"\u002Fguide\u002Fai-agent","AI Agent & Autonomy","Configure the AI agent that classifies and drafts replies to inbound mail: auto-reply settings, the health dashboard, circuit breakers, autonomy rules, and the knowledge backfill.",{"path":105,"title":106,"description":107},"\u002Fguide\u002Fknowledge-graph","Knowledge Graph","Browse, search, and manage Owlat's typed organizational knowledge — the 7 entry types, source attribution, confidence decay, relations, and how entries are extracted from mail.",{"path":109,"title":110,"description":111},"\u002Fguide\u002Ffiles","Files","Upload, browse, search, tag, and version documents in the file library.",{"path":113,"title":114,"description":115},"\u002Fguide\u002Fchat","Team Chat","Use Owlat's built-in team chat: public and private channels, direct messages, mentions, attachments, and channels linked to an inbox conversation.",{"path":117,"title":118,"description":119},"\u002Fguide\u002Fcode-tasks","Code Tasks","Queue coding-agent tasks, watch them move from queued through review, and run the code-worker sidecar that opens the pull requests.",{"path":121,"title":122,"description":123},"\u002Fguide\u002Faudience-data","Audience Data: Identities, Relationships & Timeline","Unify a contact across email, phone, and messaging channels, merge duplicates, map relationships, and read the cross-channel interaction timeline.",{"path":125,"title":126,"description":127},"\u002Fguide\u002Fimporting-contacts","Importing & Exporting Contacts","Bring contacts into Owlat from a CSV or from Mailchimp and Stripe, export them back out, and run bulk operations on your audience.",{"path":129,"title":130,"description":131},"\u002Fguide\u002Faccount","Your Account & Data","Export your data as JSON or CSV, request account deletion with a 30-day grace period, and use the onboarding checklist and the public preference center.",{"path":133,"title":134,"description":135},"\u002Fguide\u002Fchannels","Communication Channels","Configure SMS, WhatsApp, and generic-webhook channels, monitor channel health, and understand which channels are fully live today.",{"path":137,"title":138,"description":139},"\u002Fguide\u002Fdesktop-app","Desktop App","Install the Owlat desktop app, connect one or more workspaces, switch between them, and use native notifications, tray badges, shortcuts, and deep links.",{"path":141,"title":142,"description":143},"\u002Fguide\u002Femail-templates","Email Templates","Reusable email designs that define the structure, content, and personalization of every campaign and transactional message you send in Owlat.",{"path":145,"title":146,"description":147},"\u002Fguide\u002Fai-assistant","AI Assistant","Owlat's multi-turn, streaming, tool-calling AI assistant — a private chat surface that can search your workspace and draft copy, plus @assistant replies inside team chat.",{"path":149,"title":150,"description":151},"\u002Fguide\u002Fsecurity-scanning","Sending Security & Scanning","Owlat's security scanning: a content check for spam and phishing, an attachment scan for malware, and a Google Safe Browsing URL check. Suspicious content goes to a review queue.",{"path":153,"title":154,"description":155},"\u002Fguide\u002Fsystem-updates","System & Updates","The owner-only System & Updates screen: your current Owlat version, container health, LLM spend, and the in-app one-click updater with history.",{"path":157,"title":158,"description":159},"\u002Fguide\u002Foperating-modes","Operating Modes","The different ways to run Owlat at a company — read external mailboxes over IMAP, send transactional or marketing email through a delivery provider, host your own mail server, or run a team inbox with AI — and the rules that keep each combination coherent.",{"path":161,"title":162,"description":163},"\u002Fguide\u002Fsaved-blocks","Saved Blocks","Create reusable, linked content blocks you can drop into any email — edit one and every email that uses it updates automatically.",{"path":165,"title":166,"description":167},"\u002Fguide\u002Fmedia-library","Media Library","Manage, organize, search, and reuse images and files across your emails from one centralized hub.",{"path":169,"title":170,"description":171},"\u002Fguide\u002Femail-theme","Email Theme","Set your organization's default colors, font, and email width so every new template starts from a consistent baseline.",{"path":173,"title":174,"description":175},"\u002Fguide\u002Ftranslations","Translations","Send one email in multiple languages: add per-language translations to a single template and Owlat picks the right version for each recipient.",{"path":177,"title":178,"description":179},"\u002Fguide\u002Fcontacts","Contacts","How to add, view, organize, and manage contacts in Owlat, including sources, the contact detail tabs, and subscription compliance.",{"path":181,"title":182,"description":183},"\u002Fapi","API Overview","Owlat exposes authenticated API endpoints under your Convex site URL.",{"path":185,"title":186,"description":187},"\u002Fapi\u002Fwebhooks","Webhooks","Owlat supports both outbound customer webhooks and inbound provider webhooks.",{"path":189,"title":190,"description":191},"\u002Fapi\u002Fpublic-endpoints","Public Endpoints","These routes are public-facing and usually accessed from email links or embedded forms.",{"path":193,"title":194,"description":195},"\u002Fapi\u002Fwebhook-payloads","Webhook Payloads","The authoritative wire contract for outbound webhooks: envelope, signature headers, per-event data shapes, and payload versioning.",{"path":197,"title":198,"description":199},"\u002Fapi\u002Finbound-channels","Inbound Channel Webhooks","Provider webhook reference for inbound SMS, WhatsApp, and generic-channel messages, plus the MTA mailbox and credential callbacks.",{"path":201,"title":202,"description":203},"\u002Fapi\u002Fauthentication","Authentication","Secure API access with organization-scoped API keys.",{"path":205,"title":206,"description":207},"\u002Fapi\u002Fsdk","TypeScript SDK","Typed client for the Owlat API, usable from Node.js, Bun, Deno, or any server-side JavaScript runtime.",{"path":209,"title":210,"description":211},"\u002Fapi\u002Fsdk-java","Java SDK","The official `owlat-sdk` package provides a typed client for interacting with the Owlat API from any JVM application. Requires Java 11+.",{"path":213,"title":214,"description":215},"\u002Fapi\u002Fcontacts","Contacts API","Manage contacts for your organization.",{"path":217,"title":218,"description":219},"\u002Fapi\u002Ftopics","Topics API","Manage topic membership through authenticated endpoints.",{"path":221,"title":222,"description":223},"\u002Fapi\u002Fevents","Events API","Send contact events to drive segmentation and automation triggers.",{"path":225,"title":226,"description":227},"\u002Fapi\u002Ftransactional","Transactional API","Send published transactional templates to a recipient.",{"path":229,"title":230,"description":231},"\u002Fapi\u002Fforms","Forms API","Capture subscribers through public form endpoints.",{"path":233,"title":234,"description":235},"\u002Fdeveloper","Developer Guide","Technical architecture, feature-flag model, and provider abstractions used by Owlat.",{"path":237,"title":238,"description":239},"\u002Fdeveloper\u002Fmta-system","MTA System","Owlat's custom Mail Transfer Agent for direct SMTP delivery with intelligent rate limiting, bounce processing, and IP warming.",{"path":241,"title":242,"description":243},"\u002Fdeveloper\u002Ffeature-flags","Feature flags — developer reference","How the Owlat feature flag system works: single source of truth, dependency resolution, docker profile mapping, and how to add a new flag.",{"path":245,"title":246,"description":247},"\u002Fdeveloper\u002Fhow-email-works","How Email Works","A technical deep-dive into how email actually works — from SMTP and DNS to authentication, deliverability, and the differences between marketing and private email.",{"path":249,"title":250,"description":251},"\u002Fdeveloper\u002Femail-security","Email Security","Content scanning, attachment validation, URL reputation checking, and malware detection for outbound emails.",{"path":253,"title":254,"description":255},"\u002Fdeveloper\u002Fpostbox-architecture","Postbox Architecture","How the Postbox personal-mail feature is wired — schema, IMAP server, app-password auth, outbound relay, inbound delivery, and external mailboxes.",{"path":257,"title":258,"description":259},"\u002Fdeveloper\u002Fproviders","Providers","Pluggable provider abstractions for LLM, email sending, notifications, vector stores, and analytics, selected per-deployment so self-hosters can swap implementations without code changes.",{"path":261,"title":262,"description":263},"\u002Fdeveloper\u002Fcampaign-internals","Campaign Internals","How the campaign backend works: two status machines, send pre-flight, the send orchestrator, emailSends records, and the priority workpools.",{"path":265,"title":266,"description":267},"\u002Fdeveloper\u002Faudience-internals","Audience Internals","Backend reference for contact resolution, the double opt-in lifecycle, topic subscription, the conditions registry, and segment evaluation.",{"path":269,"title":270,"description":271},"\u002Fdeveloper\u002Fautomation-internals","Automation Internals","How the automation run engine works: the step walker, the lifecycle state machine, trigger fanout, the three step types, and the resilience cron.",{"path":273,"title":274,"description":275},"\u002Fdeveloper\u002Fdeliverability-infrastructure","Deliverability Infrastructure","The Convex-side deliverability backend: provider routing, health-aware failover, sending reputation with auto-enforcement, IP warming cache, the blocklist, and the content-scan gate.",{"path":277,"title":278,"description":279},"\u002Fdeveloper\u002Farchitecture","Architecture Overview","Owlat follows a modern serverless architecture with real-time capabilities.",{"path":281,"title":282,"description":283},"\u002Fdeveloper\u002Fplatform-operations","Platform Operations","Operator reference for abuse status and the sending gate, the platform-admin roster, content review, org deletion, in-app self-update, dev endpoints, crons, and migrations.",{"path":285,"title":286,"description":287},"\u002Fdeveloper\u002Fscopes","Scopes","What each app and package in the Owlat monorepo is responsible for.",{"path":289,"title":290,"description":291},"\u002Fdeveloper\u002Fself-hosting","Self-Hosting","Deploy Owlat on your own infrastructure with Docker Compose. Complete guide from first boot to production.",{"path":293,"title":294,"description":295},"\u002Fdeveloper\u002Fself-hosting-config","Self-Hosting Configuration","Complete reference for Docker environment variables, Convex backend variables, service topology, and volume persistence.",{"path":297,"title":298,"description":299},"\u002Fdeveloper\u002Fself-hosting-dns-email","DNS & Email Setup","Configure DNS records, DKIM signing, SPF, DMARC, and bounce handling for reliable email delivery.",{"path":301,"title":302,"description":303},"\u002Fdeveloper\u002Fself-hosting-production","Production Deployment","Secure your self-hosted Owlat instance with TLS, firewall rules, backups, and monitoring.",{"path":305,"title":306,"description":307},"\u002Fdeveloper\u002Fself-hosting-maintenance","Maintenance & Updates","Keep your self-hosted Owlat instance up to date, manage backups, scale performance, and troubleshoot common issues.",{"path":309,"title":310,"description":311},"\u002Fdeveloper\u002Fself-hosting-desktop","Desktop Installer","Install Owlat on a bare Linux VPS straight from the desktop app over SSH — no terminal — with a live, animated provisioning timeline.",{"path":313,"title":314,"description":315},"\u002Fdeveloper\u002Fsetup-cli","Setup CLI & Installer","Operator reference for the Owlat self-host tooling: the install.sh one-liner, the owlat-setup CLI, the convex-deploy flow, and admin bootstrap.",{"path":317,"title":318,"description":319},"\u002Fdeveloper\u002Fconvex","Convex Backend","Owlat uses Convex as its serverless backend, providing real-time subscriptions, ACID transactions, and TypeScript-first development.",{"path":321,"title":202,"description":322},"\u002Fdeveloper\u002Fauthentication","Owlat uses BetterAuth with the Convex adapter for authentication and organization (team) management.",{"path":324,"title":325,"description":326},"\u002Fdeveloper\u002Femail-system","Email System","Owlat's email system consists of a visual editor, template management, and multi-provider sending infrastructure.",{"path":328,"title":329,"description":330},"\u002Fdeveloper\u002Femail-renderer","Email Renderer","The @owlat\u002Femail-renderer package converts editor JSON blocks into production-ready HTML emails with cross-client compatibility, CSS inlining, dark mode, and Outlook VML fallbacks.",{"path":332,"title":333,"description":334},"\u002Fdeveloper\u002Fenvironment-variables","Environment Variables","Reference for every environment variable Owlat reads across the Convex backend, web app, MTA, IMAP server, and mail-sync worker.",{"path":336,"title":337,"description":338},"\u002Fdeveloper\u002Fcomponents","Component Library","Reference for the reusable, auto-imported Vue UI components shipped in the packages\u002Fui layer.",{"path":340,"title":341,"description":342},"\u002Fdeveloper\u002Fdecisions","Architectural Decision Records","The architectural decision records for the Owlat project, each capturing the context, the decision, and the trade-offs involved.",{"path":344,"title":345,"description":346},"\u002Fdeveloper\u002Fdecisions\u002F009-model-routing","ADR-009: Task-Based Model Routing","Why Owlat supports per-task LLM model selection instead of using a single model for all pipeline steps.",{"path":348,"title":349,"description":350},"\u002Fdeveloper\u002Fdecisions\u002F010-listing-engine","ADR-010: Listing Engine","Why Owlat replaced four incompatible list-query contracts with one generic listing engine driven by per-entity descriptors.",{"path":352,"title":353,"description":354},"\u002Fdeveloper\u002Fdecisions\u002F001-custom-email-renderer","ADR-001: Custom Email Renderer Over MJML","Why Owlat built a custom table-based HTML email renderer instead of using MJML, gaining full control over VML, dark mode, and per-client rendering.",{"path":356,"title":357,"description":358},"\u002Fdeveloper\u002Fdecisions\u002F002-convex-backend","ADR-002: Convex as Backend","Why Owlat chose Convex over PostgreSQL and Firebase for real-time reactivity, co-located TypeScript logic, and zero-config scaling.",{"path":360,"title":361,"description":362},"\u002Fdeveloper\u002Fdecisions\u002F003-notion-like-builder","ADR-003: Notion-like Email Builder","Why Owlat replaced the traditional 3-panel email editor with a Notion-like single-column canvas for inline WYSIWYG editing.",{"path":364,"title":365,"description":366},"\u002Fdeveloper\u002Fdecisions\u002F004-monorepo-bun-workspaces","ADR-004: Monorepo with Bun Workspaces","Why Owlat uses a monorepo with Bun workspaces and Turborepo for fast installs, atomic cross-package changes, and cached CI.",{"path":368,"title":369,"description":370},"\u002Fdeveloper\u002Fdecisions\u002F005-custom-mta","ADR-005: Custom MTA","Why Owlat built a custom Mail Transfer Agent instead of relying solely on third-party email providers.",{"path":372,"title":373,"description":374},"\u002Fdeveloper\u002Fdecisions\u002F006-self-hosted-convex","ADR-006: Self-Hosted Convex","Why Owlat uses the open-source Convex backend for self-hosting instead of migrating to a different database.",{"path":376,"title":377,"description":378},"\u002Fdeveloper\u002Fdecisions\u002F007-pluggable-llm","ADR-007: Pluggable LLM Provider","Why Owlat uses the Vercel AI SDK with a provider abstraction layer instead of hardcoding a single LLM vendor.",{"path":380,"title":381,"description":382},"\u002Fdeveloper\u002Fdecisions\u002F008-process-architecture","ADR-008: Agent Process Architecture","Why Owlat processes inbound messages with a self-scheduling step walker plus a lifecycle coordinator instead of one sequential function.",{"path":384,"title":385,"description":386},"\u002Fexamples","Examples","Copy-pasteable integration patterns for common Owlat use cases.",{"path":388,"title":389,"description":390},"\u002Fexamples\u002Fwelcome-email","Welcome Email","Send a personalized welcome email when a new user signs up.",{"path":392,"title":393,"description":394},"\u002Fexamples\u002Fbilling-email","Billing Email","Send a billing receipt with an invoice PDF attached after a successful payment.",{"path":396,"title":397,"description":398},"\u002Fexamples\u002Fevent-automation","Event Automation","Trigger automations with custom events for trial lifecycle, feature adoption, and more.",{"path":400,"title":401,"description":402},"\u002Fexamples\u002Fcontact-sync","Contact Sync","Sync contacts from your database to Owlat using upsert patterns and bulk operations.",{"path":404,"title":405,"description":406},"\u002Fexamples\u002Fwebhook-handler","Webhook Handler","Handle Owlat delivery webhooks with signature verification and event routing.",{"path":408,"title":409,"description":410},"\u002Fexamples\u002Fmultilingual-email","Multilingual Email","Send emails in the recipient's preferred language using template translations.",{"path":412,"title":413,"description":414},"\u002Fvision","Vision","Where Owlat is heading — from email platform to unified communication intelligence powered by AI agents.",{"path":416,"title":417,"description":418},"\u002Fvision\u002Fself-hosting","Self-Hosting Architecture","How Owlat runs as a fully self-hosted stack using Docker Compose — open-source Convex backend, custom MTA, and a pluggable LLM provider.",{"path":420,"title":421,"description":422},"\u002Fvision\u002Fagent-pipeline","Agent Pipeline","Technical architecture for the inbound email agent pipeline — step modules, the walker, security scanning, threading, and human review.",{"path":424,"title":106,"description":425},"\u002Fvision\u002Fknowledge-graph","Technical architecture for Owlat's typed knowledge storage — how organizational knowledge is stored, searched, decayed, and maintained.",{"path":427,"title":428,"description":429},"\u002Fvision\u002Fmulti-channel","Multi-Channel & CRM","Technical architecture for channel adapters, unified messaging, contact identity unification, and the CRM hub.",{"path":431,"title":432,"description":433},"\u002Fvision\u002Ffile-system","Semantic File System","Technical architecture for Owlat's semantic file storage — version tracking with provenance today, plus the planned embedding-based retrieval and auto-tagging layer.",{"path":435,"title":436,"description":437},"\u002Fvision\u002Fdesktop-app","Desktop App & Advanced Agents","Architecture of the Owlat desktop shell, visualization agent, adaptive dashboard, agent health, graduated autonomy, and coding agents.",{"path":439,"title":440,"description":441},"\u002Fvision\u002Froadmap","Roadmap","What's planned next for Owlat — the documented-but-unbuilt pieces still being wired, and the enhancements on our radar.",{"id":443,"title":94,"body":444,"description":95,"extension":1151,"meta":1152,"navigation":1153,"path":93,"seo":1154,"stem":1155,"__hash__":1156},"content\u002F1.guide\u002F29.team-inbox.md",{"type":445,"value":446,"toc":1129},"minimark",[447,456,461,469,489,500,504,511,516,519,623,641,650,654,657,673,684,688,691,701,705,708,762,767,771,786,790,797,827,837,841,853,869,875,878,884,891,934,937,955,964,967,983,996,1000,1007,1060,1072,1076,1082,1098,1101,1105,1115,1119,1123,1126],[448,449,450,451,455],"p",{},"The Team Inbox is the shared mailbox where inbound email lands. Every reply, support request, or sales enquiry sent to one of your receiving addresses is stored, threaded by conversation, classified by the AI agent, and — depending on your ",[452,453,454],"a",{"href":101},"AI Agent"," settings — given a suggested draft reply. Owners and admins triage from a single dashboard: read the thread, approve or rewrite the agent's draft, work a focused review queue, and quarantine anything the security filter flags.",[457,458,460],"h2",{"id":459},"what-the-team-inbox-is","What the Team Inbox is",[448,462,463,464,468],{},"The inbox is a ",[465,466,467],"em",{},"shared"," surface, not a per-user mailbox. There is one inbox for the workspace, and threads stay visible to every owner and admin so anyone on the team can pick up a conversation.",[448,470,471,472,476,477,481,482,485,486,488],{},"The inbox is gated behind the ",[473,474,475],"strong",{},"Email inbox"," feature flag (",[478,479,480],"code",{},"inbox","), which is ",[473,483,484],{},"off by default",". Until an operator enables it, the inbox routes are hidden and the backend queries refuse to return data. See ",[452,487,70],{"href":69}," for how to turn it on, and note that receiving mail also requires the inbound MTA to be configured.",[490,491,494],"callout",{"title":492,"type":493},"Where mail comes from","info",[448,495,496,497,499],{},"Inbound email reaches the inbox through your configured receiving channel — typically the bundled MTA forwarding to Owlat. SMS and WhatsApp threads can also surface here, and those channels are bidirectional — replies (both agent completions and manual admin sends) go back out the same channel; see ",[452,498,134],{"href":133},".",[457,501,503],{"id":502},"the-inbox-dashboard","The inbox dashboard",[448,505,506,507,510],{},"The inbox landing page (",[473,508,509],{},"Inbox"," in the dashboard) gives you a stats overview, status filters, and the thread list.",[512,513,515],"h3",{"id":514},"stats","Stats",[448,517,518],{},"A row of counters summarises the current state of the pipeline:",[520,521,522,535],"table",{},[523,524,525],"thead",{},[526,527,528,532],"tr",{},[529,530,531],"th",{},"Counter",[529,533,534],{},"Meaning",[536,537,538,549,563,573,583,593,603,613],"tbody",{},[526,539,540,546],{},[541,542,543],"td",{},[473,544,545],{},"Total",[541,547,548],{},"All inbound messages ever received.",[526,550,551,556],{},[541,552,553],{},[473,554,555],{},"Open Threads",[541,557,558,559,562],{},"Conversations currently in the ",[478,560,561],{},"open"," status — your live backlog.",[526,564,565,570],{},[541,566,567],{},[473,568,569],{},"Drafts Ready",[541,571,572],{},"Messages with an agent draft waiting for human review.",[526,574,575,580],{},[541,576,577],{},[473,578,579],{},"Processing",[541,581,582],{},"Messages the agent is still working through.",[526,584,585,590],{},[541,586,587],{},[473,588,589],{},"Approved",[541,591,592],{},"Drafts approved and queued for sending.",[526,594,595,600],{},[541,596,597],{},[473,598,599],{},"Sent",[541,601,602],{},"Replies that have gone out.",[526,604,605,610],{},[541,606,607],{},[473,608,609],{},"Quarantined",[541,611,612],{},"Messages held by the security filter.",[526,614,615,620],{},[541,616,617],{},[473,618,619],{},"Failed",[541,621,622],{},"Messages whose processing failed after the automatic retries were exhausted.",[448,624,625,626,628,629,631,632,628,636,640],{},"The ",[473,627,609],{}," and ",[473,630,619],{}," counters are clickable, linking to the ",[452,633,635],{"href":634},"#quarantine","Quarantine",[452,637,639],{"href":638},"#failed-messages","Failed messages"," pages respectively.",[448,642,625,643,645,646,649],{},[473,644,569],{}," count also appears as a badge on the ",[473,647,648],{},"Review Queue"," button so you can see your review backlog at a glance.",[512,651,653],{"id":652},"filtering-the-thread-list","Filtering the thread list",[448,655,656],{},"The thread list shows one row per conversation, newest activity first, with the sender, subject, message count, status badge, and time of the last message. Two filters narrow it down:",[658,659,660,667],"ul",{},[661,662,663,666],"li",{},[473,664,665],{},"Status"," — All Statuses, Open, Waiting, Resolved, or Closed.",[661,668,669,672],{},[473,670,671],{},"Assigned to me"," — only threads assigned to you.",[448,674,675,676,679,680,683],{},"Use ",[473,677,678],{},"Clear filters"," to reset both. The list pages in batches; click ",[473,681,682],{},"Load More"," to fetch older threads.",[457,685,687],{"id":686},"reading-a-thread","Reading a thread",[448,689,690],{},"Click any thread to open it. The thread detail view has a message timeline on the left and a sidebar on the right.",[448,692,625,693,696,697,700],{},[473,694,695],{},"timeline"," shows each inbound message oldest-first, with the sender, timestamp, subject, and full text body. Each message also carries a ",[473,698,699],{},"processing status"," badge — Received, Processing, Classified, Draft Ready, Approved, Sent, Quarantined, or Failed — so you can see where the agent got to.",[512,702,704],{"id":703},"ai-classification","AI classification",[448,706,707],{},"When the agent has classified a message, a panel shows what it inferred:",[520,709,710,720],{},[523,711,712],{},[526,713,714,717],{},[529,715,716],{},"Field",[529,718,719],{},"What it tells you",[536,721,722,732,742,752],{},[526,723,724,729],{},[541,725,726],{},[473,727,728],{},"Category",[541,730,731],{},"The kind of message (e.g. support, sales, billing, feature request, complaint, spam, internal, other).",[526,733,734,739],{},[541,735,736],{},[473,737,738],{},"Priority",[541,740,741],{},"How urgent the agent judged it.",[526,743,744,749],{},[541,745,746],{},[473,747,748],{},"Sentiment",[541,750,751],{},"The tone it detected.",[526,753,754,759],{},[541,755,756],{},[473,757,758],{},"Confidence",[541,760,761],{},"How sure the agent is, as a percentage.",[448,763,764,765,499],{},"The displayed classification panel doesn't auto-send a reply, but the category does drive pipeline routing: messages classified as spam are archived, and complaints or urgent messages are escalated straight to human review (skipping the auto-drafter). Auto-reply decisions are governed separately by the agent's confidence threshold and auto-reply settings, covered in ",[452,766,102],{"href":101},[512,768,770],{"id":769},"the-sidebar","The sidebar",[448,772,773,774,777,778,781,782,785],{},"The right-hand sidebar shows the linked ",[473,775,776],{},"Contact"," (with a link to their full ",[452,779,780],{"href":177},"contact profile",") when Owlat could match the sender, plus thread ",[473,783,784],{},"Details",": status, message count, assignee, and the time of the last message.",[457,787,789],{"id":788},"the-agent-draft","The agent draft",[448,791,792,793,796],{},"When the agent has produced a reply and the message is in ",[473,794,795],{},"Draft Ready",", the draft appears below the original message with three actions:",[658,798,799,807,817],{},[661,800,801,804,805,499],{},[473,802,803],{},"Approve & Send"," — accept the draft as-is. It's queued for sending and the message moves to ",[473,806,589],{},[661,808,809,812,813,816],{},[473,810,811],{},"Edit"," — open the draft inline. You can rewrite the body and optionally set a subject, then ",[473,814,815],{},"Save & Approve"," to send your edited version.",[661,818,819,822,823,826],{},[473,820,821],{},"Reject"," — discard the draft. A dialog lets you add an optional reason, which is recorded to the ",[452,824,825],{"href":77},"audit log"," for your team's reference.",[490,828,831],{"title":829,"type":830},"Edits are sent, not just saved","tip",[448,832,833,834,836],{},"Editing a draft uses ",[473,835,815],{}," — your revised text is what goes out. There's no separate \"save draft for later\" step in the thread view.",[457,838,840],{"id":839},"review-queue","Review queue",[448,842,625,843,845,846,849,850,852],{},[473,844,648],{}," (reachable from the inbox header) is a focused list of ",[465,847,848],{},"only"," the messages in ",[473,851,795],{}," across all threads — the work that actually needs a human decision right now. Each card shows the sender, a two-line excerpt of the original message, the classification category and confidence, and the full agent draft.",[448,854,855,856,858,859,861,862,864,865,868],{},"From the queue you can ",[473,857,803],{}," or ",[473,860,821],{}," in place, or jump to the full thread via ",[473,863,811],{}," \u002F ",[473,866,867],{},"View thread"," if you want to rewrite the draft before sending. When the queue is empty you'll see an \"All caught up!\" state.",[490,870,872],{"title":871,"type":493},"One at a time",[448,873,874],{},"The review queue processes drafts individually — there's no bulk \"approve all\" action. Approving or rejecting acts on a single message.",[457,876,635],{"id":877},"quarantine",[448,879,880,881,883],{},"Inbound mail passes through a security filter before the agent ever drafts a reply. Anything that trips the filter — prompt-injection attempts, suspected phishing, or other abuse — is held in ",[473,882,635],{}," instead of being processed, so a poisoned message can never drive the agent.",[448,885,886,887,890],{},"Each quarantined message shows a ",[473,888,889],{},"Security Alert"," panel with:",[658,892,893,923,928],{},[661,894,895,898,899,902,903,906,907,910,911,914,915,918,919,922],{},[473,896,897],{},"Type"," — what the scanner matched. The security scanner combines pattern matching with an LLM guard and emits three type values: ",[478,900,901],{},"prompt_injection"," (deterministic instruction-override patterns — a direct instruction-override attempt, a delimiter attack, or role impersonation in the message text), ",[478,904,905],{},"llm_prompt_injection"," (the guard-tier LLM classifier flagged it), and ",[478,908,909],{},"smuggling:…"," (hidden instructions inside the HTML body — e.g. ",[478,912,913],{},"smuggling:html_comment",", ",[478,916,917],{},"smuggling:invisible_text",", or ",[478,920,921],{},"smuggling:zero_width_chars",").",[661,924,925,927],{},[473,926,758],{}," — how sure the scanner is, as a percentage. Messages are only quarantined above a high-confidence threshold.",[661,929,930,933],{},[473,931,932],{},"Flagged content"," — the specific snippet that tripped the filter.",[448,935,936],{},"You have two actions:",[658,938,939,945],{},[661,940,941,944],{},[473,942,943],{},"Release (False Positive)"," — return the message to the pipeline. It re-enters at the start and is re-scanned and processed normally.",[661,946,947,950,951,954],{},[473,948,949],{},"Block Sender"," — add the sender's address to the suppression\u002Fblocklist and archive the message. Inbound mail from that address is not currently auto-rejected on receipt; the blocklist suppresses future ",[465,952,953],{},"outbound"," mail to that address.",[490,956,959],{"title":957,"type":958},"Release with care","warning",[448,960,961,962,499],{},"Releasing a quarantined message hands its content to the agent. Only release messages you've confirmed are genuine — the quarantine exists precisely to keep untrusted content away from the model. For background on the scanning engine, see ",[452,963,250],{"href":249},[457,965,639],{"id":966},"failed-messages",[448,968,969,970,972,973,975,976,978,979,982],{},"Processing can fail — a transient model error, a downstream timeout, or a bad payload. The pipeline retries automatically (up to three times), but a message that still can't make progress lands in a terminal ",[473,971,619],{}," state and drops out of the workflow. The ",[473,974,639],{}," page (reachable from the ",[473,977,619],{}," stat card) surfaces every such message with its ",[473,980,981],{},"failure reason"," so an operator can read what went wrong.",[448,984,985,986,989,990,993,994,499],{},"Once the cause is resolved, ",[473,987,988],{},"Retry processing"," re-enqueues the message: it routes back to ",[473,991,992],{},"Received"," and the pipeline re-runs from the security scan. Retries are recorded in the ",[452,995,825],{"href":77},[457,997,999],{"id":998},"assigning-and-resolving-threads","Assigning and resolving threads",[448,1001,1002,1003,1006],{},"Each thread carries a ",[473,1004,1005],{},"status"," that you change from the status dropdown in the thread header:",[520,1008,1009,1018],{},[523,1010,1011],{},[526,1012,1013,1015],{},[529,1014,665],{},[529,1016,1017],{},"Use it for",[536,1019,1020,1030,1040,1050],{},[526,1021,1022,1027],{},[541,1023,1024],{},[473,1025,1026],{},"Open",[541,1028,1029],{},"An active conversation that needs attention.",[526,1031,1032,1037],{},[541,1033,1034],{},[473,1035,1036],{},"Waiting",[541,1038,1039],{},"You've replied and are waiting on the customer.",[526,1041,1042,1047],{},[541,1043,1044],{},[473,1045,1046],{},"Resolved",[541,1048,1049],{},"The issue is handled.",[526,1051,1052,1057],{},[541,1053,1054],{},[473,1055,1056],{},"Closed",[541,1058,1059],{},"Archived \u002F done.",[448,1061,1062,1063,1066,1067,1069,1070,499],{},"Threads can also be ",[473,1064,1065],{},"assigned"," to a specific team member, which pairs with the ",[473,1068,671],{}," filter on the inbox list so each person can see their own queue. Status changes and assignments are recorded in the ",[452,1071,825],{"href":77},[457,1073,1075],{"id":1074},"discussing-a-thread-in-chat","Discussing a thread in chat",[448,1077,1078,1079,1081],{},"If ",[452,1080,114],{"href":113}," is enabled, you can pull a conversation into a channel for internal discussion without exposing it to the customer. From the thread header:",[658,1083,1084,1091],{},[661,1085,1086,1087,1090],{},"If a channel already references this thread, it appears as a ",[473,1088,1089],{},"#channel"," link — click to jump straight there.",[661,1092,1093,1094,1097],{},"Otherwise, ",[473,1095,1096],{},"Discuss in channel"," lets you spin up a new channel and link it to the thread.",[448,1099,1100],{},"A linked channel shows a pinned, read-only panel of the email thread so teammates can talk it over internally; customer-facing replies still go out through the inbox approval flow described above. The discuss controls only appear when the chat feature flag is on.",[457,1102,1104],{"id":1103},"access-control","Access control",[448,1106,1107,1108,1111,1112,1114],{},"The Team Inbox is restricted to ",[473,1109,1110],{},"owners and admins",". The inbox queries use soft authentication: if you're signed in without one of those roles, the views load but stay empty rather than erroring. Members and other roles don't see inbox data at all. See ",[452,1113,74],{"href":73}," for the full role model.",[457,1116,1118],{"id":1117},"related","Related",[1120,1121],"link-card",{"description":1122,"title":102,"to":101},"How drafts are generated, the confidence threshold, auto-reply, and tone settings.",[1120,1124],{"description":1125,"title":134,"to":133},"How inbound email, chat, and other channels feed the inbox.",[1120,1127],{"description":1128,"title":118,"to":117},"Manually create developer tasks, optionally linked to an inbound message.",{"title":1130,"searchDepth":1131,"depth":1131,"links":1132},"",2,[1133,1134,1139,1143,1144,1145,1146,1147,1148,1149,1150],{"id":459,"depth":1131,"text":460},{"id":502,"depth":1131,"text":503,"children":1135},[1136,1138],{"id":514,"depth":1137,"text":515},3,{"id":652,"depth":1137,"text":653},{"id":686,"depth":1131,"text":687,"children":1140},[1141,1142],{"id":703,"depth":1137,"text":704},{"id":769,"depth":1137,"text":770},{"id":788,"depth":1131,"text":789},{"id":839,"depth":1131,"text":840},{"id":877,"depth":1131,"text":635},{"id":966,"depth":1131,"text":639},{"id":998,"depth":1131,"text":999},{"id":1074,"depth":1131,"text":1075},{"id":1103,"depth":1131,"text":1104},{"id":1117,"depth":1131,"text":1118},"md",{},true,{"title":94,"description":95},"1.guide\u002F29.team-inbox","leR6WiRNKT4oMW6HpFqzlo99254YFfq5zBcSRaf9_go",[1158,1160],{"title":90,"path":89,"stem":1159,"children":-1},"1.guide\u002F28.migrate-from-google",{"title":98,"path":97,"stem":1161,"children":-1},"1.guide\u002F3.email-editor",1782846430724]