[{"data":1,"prerenderedAt":1236},["ShallowReactive",2],{"search":3,"content-guide\u002Fchannels":442,"surround-\u002Fguide\u002Fchannels":1231},[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":134,"body":444,"description":135,"extension":1225,"meta":1226,"navigation":1227,"path":133,"seo":1228,"stem":1229,"__hash__":1230},"content\u002F1.guide\u002F38.channels.md",{"type":445,"value":446,"toc":1208},"minimark",[447,465,502,507,537,544,548,619,624,639,643,653,689,865,871,875,886,947,971,995,998,1001,1065,1072,1119,1129,1138,1141,1144,1198],[448,449,450,451,455,456,459,460,464],"p",{},"Owlat models every conversation medium — email, native chat, SMS, WhatsApp, and a catch-all webhook — as a ",[452,453,454],"em",{},"channel",". Inbound messages from all of them land in the shared ",[457,458,94],"a",{"href":93}," on a unified timeline. This page covers the ",[461,462,463],"strong",{},"Channels"," settings screen where owners and admins enable channels, store provider credentials, and watch health status.",[466,467,470],"callout",{"title":468,"type":469},"What is actually live today","warning",[448,471,472,475,476,479,480,483,484,487,488,491,492,496,497,501],{},[461,473,474],{},"Email"," and ",[461,477,478],{},"native chat"," send and receive end-to-end. Owlat can also send outbound over ",[461,481,482],{},"SMS",", ",[461,485,486],{},"WhatsApp",", and the ",[461,489,490],{},"generic webhook",", but only as an AI-agent reply (auto-send or approved draft) when the AI agent (",[493,494,495],"code",{},"ai.agent",") is enabled. An owner\u002Fadmin can also manually send over SMS, WhatsApp, or the generic webhook from a contact's Unified Timeline (Contacts page) using the per-contact composer; there is no per-message reply button inside the Team Inbox itself. See ",[457,498,500],{"href":499},"#current-limitations","Current limitations",".",[503,504,506],"h2",{"id":505},"where-to-find-channels","Where to find Channels",[448,508,509,510,513,514,517,518,521,522,525,526,529,530,533,534,536],{},"Open ",[461,511,512],{},"Settings → Channels"," in the dashboard (route ",[493,515,516],{},"\u002Fdashboard\u002Fsettings\u002Fchannels","). The page itself only requires being signed in, but ",[461,519,520],{},"changing"," anything — enabling\u002Fdisabling a channel or saving credentials — is restricted to ",[461,523,524],{},"owners and admins",": the underlying ",[493,527,528],{},"updateChannelConfig"," mutation requires the ",[493,531,532],{},"organization:manage"," permission (see ",[457,535,74],{"href":73},"). A non-admin who reaches this screen can read the channel list but their save and toggle actions are rejected.",[448,538,539,540,543],{},"The screen lists one card per channel. Each card shows the channel's icon and name, an enable\u002Fdisable toggle, a health badge, and a ",[461,541,542],{},"Configure"," panel that expands to a credential form. A sidebar summarises totals: how many channels exist, how many are enabled, and how many are healthy, degraded, or down.",[503,545,547],{"id":546},"what-the-channels-are","What the channels are",[549,550,551,564],"table",{},[552,553,554],"thead",{},[555,556,557,561],"tr",{},[558,559,560],"th",{},"Channel",[558,562,563],{},"What it does today",[565,566,567,581,591,600,609],"tbody",{},[555,568,569,574],{},[570,571,572],"td",{},[461,573,474],{},[570,575,576,577,580],{},"Send and receive via the built-in ",[457,578,579],{"href":237},"MTA",". Fully live. No credentials to enter here — email delivery is managed by the MTA.",[555,582,583,588],{},[570,584,585],{},[461,586,587],{},"Chat",[570,589,590],{},"Native in-app chat powered by the built-in messaging system. Fully live. No credentials required.",[555,592,593,597],{},[570,594,595],{},[461,596,482],{},[570,598,599],{},"Receive inbound texts via Twilio. Outbound send works only via AI-agent replies (no manual reply UI), when the AI agent is enabled.",[555,601,602,606],{},[570,603,604],{},[461,605,486],{},[570,607,608],{},"Receive inbound messages via the WhatsApp Business (Meta Cloud) API. Outbound send works only via AI-agent replies (no manual reply UI), when the AI agent is enabled.",[555,610,611,616],{},[570,612,613],{},[461,614,615],{},"Generic webhook",[570,617,618],{},"Receive inbound messages from any HTTP source via a shared secret. Outbound send works only via AI-agent replies (no manual reply UI), when the AI agent is enabled.",[620,621,623],"h3",{"id":622},"what-enabled-really-means","What \"enabled\" really means",[448,625,626,627,630,631,633,634,638],{},"The enable toggle controls whether a channel is included in the periodic health check and surfaced as active in the overview counts. For email and chat it reflects a fully working channel. For SMS, WhatsApp, and the generic webhook, the toggle only governs health monitoring and the overview — it does ",[461,628,629],{},"not"," turn on outbound sending, and it does ",[461,632,629],{}," gate inbound: inbound webhooks are accepted purely on a valid signature plus the matching backend secret (see ",[457,635,637],{"href":636},"#inbound-channel-webhooks","Inbound channel webhooks","), whether or not the channel is toggled on.",[503,640,642],{"id":641},"configuring-sms-whatsapp-and-the-generic-webhook","Configuring SMS, WhatsApp, and the generic webhook",[448,644,645,646,648,649,652],{},"Click ",[461,647,542],{}," on a channel card to open its form. Every channel accepts an optional ",[461,650,651],{},"Display Name"," (shown in the UI in place of the default channel name). Beyond that, the credential fields differ per channel.",[466,654,657],{"title":655,"type":656},"Where each credential is used","info",[448,658,659,660,663,664,667,668,670,671,674,675,678,679,682,683,686,687,501],{},"The form fields below are display\u002Fcontext for ",[452,661,662],{},"inbound"," verification only — ",[452,665,666],{},"inbound webhook verification"," secrets are read from Convex environment variables, ",[461,669,629],{}," from these form fields, so the environment variables (not the form) are what make inbound requests succeed. The same form fields ",[461,672,673],{},"are"," used for ",[452,676,677],{},"outbound"," dispatch, though: they are encrypted at rest (",[493,680,681],{},"channels.outbound.encryptAndPersistConfig",") and decrypted by ",[493,684,685],{},"channels.outbound.dispatchOutbound"," when the AI agent replies on the channel. See ",[457,688,637],{"href":636},[690,691,692,696,699,747,754,758,761,804,815,819,858],"steps",{},[620,693,695],{"id":694},"configure-sms-twilio","Configure SMS (Twilio)",[448,697,698],{},"Enter your Twilio credentials:",[549,700,701,711],{},[552,702,703],{},[555,704,705,708],{},[558,706,707],{},"Field",[558,709,710],{},"Example",[565,712,713,725,735],{},[555,714,715,720],{},[570,716,717],{},[461,718,719],{},"Account SID",[570,721,722],{},[493,723,724],{},"ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",[555,726,727,732],{},[570,728,729],{},[461,730,731],{},"Auth Token",[570,733,734],{},"your Twilio auth token (masked in the form)",[555,736,737,742],{},[570,738,739],{},[461,740,741],{},"Phone Number",[570,743,744],{},[493,745,746],{},"+1234567890",[448,748,749,750,753],{},"For inbound SMS verification, also set the ",[493,751,752],{},"TWILIO_AUTH_TOKEN"," environment variable on the Convex backend.",[620,755,757],{"id":756},"configure-whatsapp-meta","Configure WhatsApp (Meta)",[448,759,760],{},"Enter your WhatsApp Business \u002F Meta Cloud API credentials:",[549,762,763,772],{},[552,764,765],{},[555,766,767,769],{},[558,768,707],{},[558,770,771],{},"Description",[565,773,774,784,794],{},[555,775,776,781],{},[570,777,778],{},[461,779,780],{},"Business Account ID",[570,782,783],{},"your WhatsApp Business Account ID",[555,785,786,791],{},[570,787,788],{},[461,789,790],{},"Access Token",[570,792,793],{},"Meta Cloud API access token (masked in the form)",[555,795,796,801],{},[570,797,798],{},[461,799,800],{},"Phone Number ID",[570,802,803],{},"the phone number ID from Meta",[448,805,806,807,810,811,814],{},"For inbound WhatsApp, also set ",[493,808,809],{},"META_APP_SECRET"," (for signature verification) and ",[493,812,813],{},"META_VERIFY_TOKEN"," (for Meta's subscription challenge) on the Convex backend.",[620,816,818],{"id":817},"configure-the-generic-webhook","Configure the generic webhook",[549,820,821,829],{},[552,822,823],{},[555,824,825,827],{},[558,826,707],{},[558,828,771],{},[565,830,831,848],{},[555,832,833,838],{},[570,834,835],{},[461,836,837],{},"Endpoint URL",[570,839,840,843,844,847],{},[493,841,842],{},"https:\u002F\u002Fexample.com\u002Fwebhook"," — the destination Owlat POSTs AI-agent replies to (via ",[493,845,846],{},"WebhookAdapter",")",[555,849,850,855],{},[570,851,852],{},[461,853,854],{},"Secret Key",[570,856,857],{},"a shared secret, sent as the outbound signing secret",[448,859,860,861,864],{},"For inbound generic messages, set the ",[493,862,863],{},"GENERIC_WEBHOOK_SECRET"," environment variable, which Owlat compares against the incoming request's secret.",[448,866,645,867,870],{},[461,868,869],{},"Save Configuration"," to persist. A toast confirms the save. Token fields are masked by default with a show\u002Fhide toggle.",[503,872,874],{"id":873},"channel-health-monitoring","Channel health monitoring",[448,876,877,878,881,882,885],{},"A background cron runs ",[461,879,880],{},"every 5 minutes"," and updates the health status of each ",[452,883,884],{},"enabled"," channel. Each card shows a coloured badge plus, when available, the time of the last check, the last successful send, and the last error.",[549,887,888,898],{},[552,889,890],{},[555,891,892,895],{},[558,893,894],{},"Status",[558,896,897],{},"Meaning",[565,899,900,911,922,933],{},[555,901,902,908],{},[570,903,904,907],{},[461,905,906],{},"Healthy"," (green)",[570,909,910],{},"The channel passed its last check.",[555,912,913,919],{},[570,914,915,918],{},[461,916,917],{},"Degraded"," (amber)",[570,920,921],{},"The channel is reachable but reporting problems.",[555,923,924,930],{},[570,925,926,929],{},[461,927,928],{},"Down"," (red)",[570,931,932],{},"The channel failed its last check.",[555,934,935,944],{},[570,936,937,940,941],{},[461,938,939],{},"Disabled"," \u002F ",[461,942,943],{},"Unknown",[570,945,946],{},"The channel is turned off, or no check has run yet.",[466,948,950],{"title":949,"type":656},"How the check works today",[448,951,952,953,955,956,959,960,963,964,967,968,970],{},"Email and chat are always reported as healthy by this cron (email deliverability is tracked separately by the provider-health system, see ",[457,954,62],{"href":61},"). For SMS, WhatsApp, and the generic webhook, the periodic check now makes a live provider probe for ",[452,957,958],{},"configured"," channels — a configured SMS channel fetches the Twilio account and a configured WhatsApp channel fetches the Meta graph, so revoked or invalid credentials report ",[461,961,962],{},"degraded"," or ",[461,965,966],{},"down",". An unconfigured channel still reports ",[461,969,966],{}," with \"No credentials configured\". Only the generic webhook remains credential-presence only.",[448,972,973,974,979,980,983,984,483,987,990,991,994],{},"A separate ",[461,975,976],{},[493,977,978],{},"poll channel delivery status"," cron runs every 5 minutes so outbound SMS, WhatsApp, and generic messages do not sit at ",[493,981,982],{},"sent"," forever: it polls the provider for each message accepted in the last 24 hours and advances it to ",[461,985,986],{},"delivered",[461,988,989],{},"read",", or ",[461,992,993],{},"failed"," on the contact's unified timeline as the carrier reports back.",[503,996,637],{"id":997},"inbound-channel-webhooks",[448,999,1000],{},"This is where messages from SMS, WhatsApp, and generic sources arrive. Point your provider at the matching Owlat HTTP endpoint:",[549,1002,1003,1015],{},[552,1004,1005],{},[555,1006,1007,1009,1012],{},[558,1008,560],{},[558,1010,1011],{},"Endpoint",[558,1013,1014],{},"Method",[565,1016,1017,1032,1051],{},[555,1018,1019,1022,1027],{},[570,1020,1021],{},"SMS (Twilio)",[570,1023,1024],{},[493,1025,1026],{},"\u002Fwebhooks\u002Fsms",[570,1028,1029],{},[493,1030,1031],{},"POST",[555,1033,1034,1037,1042],{},[570,1035,1036],{},"WhatsApp (Meta)",[570,1038,1039],{},[493,1040,1041],{},"\u002Fwebhooks\u002Fwhatsapp",[570,1043,1044,1046,1047,1050],{},[493,1045,1031],{}," (inbound), ",[493,1048,1049],{},"GET"," (Meta verification challenge)",[555,1052,1053,1056,1061],{},[570,1054,1055],{},"Generic",[570,1057,1058],{},[493,1059,1060],{},"\u002Fwebhooks\u002Fchannel",[570,1062,1063],{},[493,1064,1031],{},[448,1066,1067,1068,1071],{},"Every inbound request is verified before it is accepted — the channel webhooks ",[461,1069,1070],{},"fail closed"," if their secret is not configured:",[1073,1074,1075,1088,1105],"ul",{},[1076,1077,1078,1081,1082,1085,1086,501],"li",{},[461,1079,1080],{},"Twilio"," requests are verified with an HMAC-SHA1 signature over the canonical URL-plus-sorted-params string (",[493,1083,1084],{},"X-Twilio-Signature","), using ",[493,1087,752],{},[1076,1089,1090,1093,1094,1085,1097,1099,1100,1102,1103,501],{},[461,1091,1092],{},"Meta (WhatsApp)"," requests are verified with an HMAC-SHA256 signature of the raw body (",[493,1095,1096],{},"X-Hub-Signature-256",[493,1098,809],{},". The ",[493,1101,1049],{}," challenge is answered using ",[493,1104,813],{},[1076,1106,1107,1109,1110,963,1113,1116,1117,501],{},[461,1108,1055],{}," requests are authenticated with a constant-time comparison of a shared secret supplied via the ",[493,1111,1112],{},"X-Webhook-Secret",[493,1114,1115],{},"Authorization: Bearer"," header, against ",[493,1118,863],{},[448,1120,1121,1122,1124,1125,1128],{},"When a verified message arrives, Owlat finds or creates a contact and a conversation thread for it and stores the message on the unified timeline, where it appears in the Team Inbox. Each channel is its own identity space: an SMS sender and an email contact with the same value are ",[452,1123,629],{}," automatically the same contact — contacts reached over SMS, WhatsApp, or generic channels may have no email address at all. See ",[457,1126,1127],{"href":121},"Audience Data"," for how identities are resolved.",[466,1130,1133],{"title":1131,"type":1132},"API reference","tip",[448,1134,1135,1136,501],{},"For the exact request shapes, headers, verification rules, and response codes, see ",[457,1137,198],{"href":197},[503,1139,500],{"id":1140},"current-limitations",[448,1142,1143],{},"Be precise about what these channels do today:",[1073,1145,1146,1176,1188],{},[1076,1147,1148,1151,1152,1155,1156,1159,1160,1159,1163,1159,1166,1168,1169,1171,1172,1175],{},[461,1149,1150],{},"Outbound send over SMS, WhatsApp, or generic only happens through the AI agent."," The full path is real and invoked: an inbound channel message runs the AI agent (",[493,1153,1154],{},"channels.ts"," ",[493,1157,1158],{},"processInboundChannel"," → ",[493,1161,1162],{},"agent.walker",[493,1164,1165],{},"agentPipeline.sendApprovedReply",[493,1167,685],{},"), which builds the real provider adapter (Twilio, Meta, or a downstream webhook) and sends. It is gated on the ",[493,1170,495],{}," feature flag and on the channel config being enabled with credentials. In addition to the AI-agent reply path, an owner\u002Fadmin can manually send on a configured channel from the contact's Unified Timeline (",[493,1173,1174],{},"channels.outbound.sendChannelMessage","); there is just no per-message reply button inside the Team Inbox itself.",[1076,1177,1178,1181,1182,1184,1185,1187],{},[461,1179,1180],{},"Signatures are not enforced as a per-channel setting."," Inbound verification is real and fails closed, but it is keyed off the backend environment variables above, not off the credentials you type into the form. Those form credentials are, however, used for the ",[452,1183,677],{}," path: they are encrypted at rest and decrypted by ",[493,1186,685],{}," when the AI agent replies on the channel.",[1076,1189,1190,1193,1194,1197],{},[461,1191,1192],{},"Health checks are credential-presence only"," for the generic webhook; SMS and WhatsApp now run a live provider ",[493,1195,1196],{},"healthCheck()"," probe (Twilio account \u002F Meta graph) for configured channels.",[448,1199,1200,1201,1204,1205,1207],{},"Use these channels to ",[452,1202,1203],{},"receive"," and triage messages in the ",[457,1206,94],{"href":93},"; outbound over SMS\u002FWhatsApp\u002Fgeneric happens through the AI agent or a manual send from the contact's Unified Timeline, since there is no per-message reply button inside the Team Inbox itself.",{"title":1209,"searchDepth":1210,"depth":1210,"links":1211},"",2,[1212,1213,1217,1222,1223,1224],{"id":505,"depth":1210,"text":506},{"id":546,"depth":1210,"text":547,"children":1214},[1215],{"id":622,"depth":1216,"text":623},3,{"id":641,"depth":1210,"text":642,"children":1218},[1219,1220,1221],{"id":694,"depth":1216,"text":695},{"id":756,"depth":1216,"text":757},{"id":817,"depth":1216,"text":818},{"id":873,"depth":1210,"text":874},{"id":997,"depth":1210,"text":637},{"id":1140,"depth":1210,"text":500},"md",{},true,{"title":134,"description":135},"1.guide\u002F38.channels","2hQomS-swYvVRxV29k3ev6_wojIsMDbKKwQ2pdCNqno",[1232,1234],{"title":130,"path":129,"stem":1233,"children":-1},"1.guide\u002F37.account",{"title":138,"path":137,"stem":1235,"children":-1},"1.guide\u002F39.desktop-app",1782846431061]