[{"data":1,"prerenderedAt":1515},["ShallowReactive",2],{"search":3,"content-guide\u002Faudience-data":442,"surround-\u002Fguide\u002Faudience-data":1510},[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":122,"body":444,"description":123,"extension":1504,"meta":1505,"navigation":1506,"path":121,"seo":1507,"stem":1508,"__hash__":1509},"content\u002F1.guide\u002F35.audience-data.md",{"type":445,"value":446,"toc":1477},"minimark",[447,486,500,505,521,532,547,552,570,573,641,652,719,737,741,747,754,757,798,809,831,835,842,860,864,905,908,1018,1030,1042,1048,1052,1080,1083,1093,1097,1104,1150,1176,1180,1186,1378,1387,1401,1405,1426,1430,1446,1450],[448,449,450,451,455,456,455,459,455,462,455,464,467,468,471,472,455,474,467,476,478,479,481,482,485],"p",{},"Every contact in Owlat is more than an email address. Open any contact and you'll find six tabs: ",[452,453,454],"strong",{},"Activity",", ",[452,457,458],{},"Timeline",[452,460,461],{},"Knowledge",[452,463,110],{},[452,465,466],{},"Identities",", and ",[452,469,470],{},"Relationships",". This guide focuses on three of them — ",[452,473,466],{},[452,475,470],{},[452,477,458],{}," — which let you unify a person across channels, link them to other contacts, and read their cross-channel message history (it also references the ",[452,480,454],{}," tab). For the basics of creating and organizing contacts, start with ",[483,484,178],"a",{"href":177},".",[448,487,488,489,492,493,455,495,467,497,499],{},"You'll find these tabs on any contact's detail page under ",[452,490,491],{},"Audience > Contacts",". Click a contact, then switch between the ",[452,494,466],{},[452,496,470],{},[452,498,458],{}," tabs.",[501,502,504],"h2",{"id":503},"contact-identities","Contact identities",[448,506,507,508,511,512,516,517,520],{},"A contact is identified by one or more ",[452,509,510],{},"channel identities"," — a channel plus an identifier, such as ",[513,514,515],"code",{},"email: jane@example.com"," or ",[513,518,519],{},"phone: +14155550123",". This is how Owlat recognizes the same person whether they reply by email, send an SMS, or message you on WhatsApp.",[448,522,523,524,527,528,531],{},"Every contact has at least one identity. When a contact is created — by an inbound message, a CSV import, a form submission, a transactional send, or the API — Owlat records a ",[452,525,526],{},"primary"," identity for the channel they arrived on. For email contacts, that identity also keeps the contact's ",[513,529,530],{},"email"," field in sync, so nothing about existing email workflows changes. Contacts created from a phone, SMS, WhatsApp, or generic channel have no email at all — their identity is the phone number or handle instead.",[533,534,537],"callout",{"title":535,"type":536},"Identities are the lookup key","info",[448,538,539,540,543,544,546],{},"Behind the scenes, Owlat resolves \"who is this?\" by looking up the ",[452,541,542],{},"(channel, identifier)"," pair, not by scanning email addresses. That's what makes emailless contacts and multi-channel unification possible. See ",[483,545,266],{"href":265}," for the resolution mechanics.",[548,549,551],"h3",{"id":550},"viewing-and-adding-identities","Viewing and adding identities",[448,553,554,555,557,558,561,562,565,566,569],{},"The ",[452,556,466],{}," tab (titled ",[452,559,560],{},"Channel Identities",") lists every identity linked to the contact. Each row shows the identifier, its channel, a ",[452,563,564],{},"Primary"," badge if it's the primary identity for that channel, and a ",[452,567,568],{},"Verified"," badge once you've confirmed it.",[448,571,572],{},"To add an identity:",[574,575,576,580,589,593,616,620,627,631],"steps",{},[548,577,579],{"id":578},"open-the-identities-tab","Open the Identities tab",[448,581,582,583,585,586,485],{},"On the contact detail page, switch to the ",[452,584,466],{}," tab and click ",[452,587,588],{},"Add Identity",[548,590,592],{"id":591},"pick-a-channel-and-enter-the-identifier","Pick a channel and enter the identifier",[448,594,595,596,455,599,455,602,455,605,455,608,611,612,615],{},"Choose a channel — ",[452,597,598],{},"Email",[452,600,601],{},"Phone",[452,603,604],{},"WhatsApp",[452,606,607],{},"Twitter\u002FX",[452,609,610],{},"LinkedIn",", or ",[452,613,614],{},"Other"," — and enter the matching identifier (an email address, a phone number, or a handle).",[548,617,619],{"id":618},"optionally-mark-it-primary","Optionally mark it primary",[448,621,622,623,626],{},"Tick ",[452,624,625],{},"Set as primary"," to make this the primary identity for its channel. Setting a new primary automatically clears the previous primary for that same channel.",[548,628,630],{"id":629},"save","Save",[448,632,633,634,637,638,640],{},"Click ",[452,635,636],{},"Add",". If the same ",[513,639,542],{}," is already linked to another contact, the add is rejected — that pair can only belong to one contact.",[448,642,643,644,647,648,651],{},"You can also ",[452,645,646],{},"verify"," an identity (mark it as confirmed) or ",[452,649,650],{},"remove"," one using the actions that appear when you hover over a row.",[653,654,655,668],"table",{},[656,657,658],"thead",{},[659,660,661,665],"tr",{},[662,663,664],"th",{},"Field",[662,666,667],{},"Meaning",[669,670,671,697,705,712],"tbody",{},[659,672,673,677],{},[674,675,676],"td",{},"Channel",[674,678,679,680,455,682,455,685,455,688,455,691,611,694],{},"The communication channel: ",[513,681,530],{},[513,683,684],{},"phone",[513,686,687],{},"whatsapp",[513,689,690],{},"twitter",[513,692,693],{},"linkedin",[513,695,696],{},"other",[659,698,699,702],{},[674,700,701],{},"Identifier",[674,703,704],{},"The address, number, or handle for that channel",[659,706,707,709],{},[674,708,564],{},[674,710,711],{},"Whether this is the primary identity for its channel (one per channel)",[659,713,714,716],{},[674,715,568],{},[674,717,718],{},"Set when you mark the identity as confirmed",[533,720,722],{"title":721,"type":536},"Outbound sending today",[448,723,724,725,729,730,732,733,736],{},"Identities let Owlat ",[726,727,728],"em",{},"recognize"," a contact across channels. Today, outbound delivery is wired end-to-end for ",[452,731,530],{}," (campaigns and transactional). For SMS, WhatsApp, and generic channels, outbound is sent per-contact — from the ",[452,734,735],{},"Send a message"," composer on a contact's Timeline tab, or by AI agent replies — once you've configured that channel's provider credentials. There's no bulk campaign or transactional sending on those channels yet.",[501,738,740],{"id":739},"merging-duplicate-contacts","Merging duplicate contacts",[448,742,743,744,485],{},"The same person can end up as two contact records — for example, one created from a newsletter signup and another from an inbound reply on a different address. The Identities tab surfaces these as ",[452,745,746],{},"Merge Suggestions",[448,748,749,750,753],{},"A suggestion appears when another contact shares an identifier with the one you're viewing. Each suggestion shows the candidate contact and which identifiers matched. Click ",[452,751,752],{},"Merge"," to combine them.",[448,755,756],{},"When you merge a source contact into the one you're viewing:",[758,759,760,768,775,785,795],"ul",{},[761,762,763,764,767],"li",{},"All of the source's ",[452,765,766],{},"identities"," move over (duplicates that already exist on the target are dropped).",[761,769,770,771,774],{},"All ",[452,772,773],{},"relationships"," pointing to or from the source are repointed to the target.",[761,776,770,777,780,781,784],{},[452,778,779],{},"conversation threads"," and ",[452,782,783],{},"unified messages"," are reassigned to the target.",[761,786,787,788,780,791,794],{},"Missing ",[452,789,790],{},"first name",[452,792,793],{},"last name"," on the target are filled in from the source.",[761,796,797],{},"The source contact is then deleted.",[533,799,802],{"title":800,"type":801},"Merging is permanent","warning",[448,803,804,805,808],{},"The source contact is deleted at the end of a merge and the action can't be undone. The target keeps its own primary identities — a merge never demotes the target's primaries. Merging requires the ",[452,806,807],{},"contacts: manage"," permission (owners and admins).",[533,810,812],{"title":811,"type":536},"Automatic de-duplication",[448,813,814,815,817,818,455,820,455,822,611,825,827,828,830],{},"Beyond manual Merge Suggestions, Owlat also auto-merges unambiguous duplicates on a schedule. A cron runs every 6 hours and folds together any contacts that share an exact identifier on a ",[452,816,452],{}," channel — ",[513,819,530],{},[513,821,684],{},[513,823,824],{},"sms",[513,826,687],{}," — into the oldest (canonical) contact, processing up to 20 merges per run. Weak or social channels (",[513,829,690],{},", generic, chat handles) are never auto-merged, since handle collisions there aren't reliable enough for an unattended merge.",[501,832,834],{"id":833},"the-relationship-graph","The relationship graph",[448,836,837,838,841],{},"Relationships connect one contact to another with a typed, directional link — for example, \"Jane is the ",[452,839,840],{},"manager of"," Sam.\" This builds a lightweight CRM-style graph on top of your audience.",[448,843,844,845,847,848,851,852,855,856,859],{},"Open the ",[452,846,470],{}," tab to see every relationship for a contact, in both directions. Each entry shows the related contact (linked to their detail page), the relationship label, the direction (a relationship pointing ",[726,849,850],{},"to"," another contact versus one pointing ",[726,853,854],{},"from"," them), and a ",[452,857,858],{},"confidence"," percentage.",[548,861,863],{"id":862},"adding-a-relationship","Adding a relationship",[574,865,866,870,879,883,890,894,897,900],{},[548,867,869],{"id":868},"open-the-relationships-tab","Open the Relationships tab",[448,871,872,873,875,876,485],{},"On the contact detail page, switch to ",[452,874,470],{}," and click ",[452,877,878],{},"Add Relationship",[548,880,882],{"id":881},"identify-the-other-contact","Identify the other contact",[448,884,885,886,889],{},"Type the related contact's name or email in the ",[452,887,888],{},"Related contact"," field and pick them from the results.",[548,891,893],{"id":892},"choose-a-type-and-confidence","Choose a type and confidence",[448,895,896],{},"Pick a relationship type and set a confidence level with the slider. The slider moves in 10% steps (0–100% in increments of 10) and defaults to 80%.",[548,898,630],{"id":899},"save-1",[448,901,633,902,904],{},[452,903,878],{},". Adding the same pairing and type again won't create a duplicate — it only raises the stored confidence if your new value is higher.",[448,906,907],{},"The built-in relationship types are:",[653,909,910,920],{},[656,911,912],{},[659,913,914,917],{},[662,915,916],{},"Type",[662,918,919],{},"Inverse (shown on the other contact)",[669,921,922,934,944,955,965,974,983,992,1001,1010],{},[659,923,924,929],{},[674,925,926],{},[513,927,928],{},"manager_of",[674,930,931],{},[513,932,933],{},"reports_to",[659,935,936,940],{},[674,937,938],{},[513,939,933],{},[674,941,942],{},[513,943,928],{},[659,945,946,951],{},[674,947,948],{},[513,949,950],{},"colleague",[674,952,953],{},[513,954,950],{},[659,956,957,962],{},[674,958,959],{},[513,960,961],{},"client",[674,963,964],{},"—",[659,966,967,972],{},[674,968,969],{},[513,970,971],{},"vendor",[674,973,964],{},[659,975,976,981],{},[674,977,978],{},[513,979,980],{},"partner",[674,982,964],{},[659,984,985,990],{},[674,986,987],{},[513,988,989],{},"advisor",[674,991,964],{},[659,993,994,999],{},[674,995,996],{},[513,997,998],{},"investor",[674,1000,964],{},[659,1002,1003,1008],{},[674,1004,1005],{},[513,1006,1007],{},"friend",[674,1009,964],{},[659,1011,1012,1016],{},[674,1013,1014],{},[513,1015,696],{},[674,1017,964],{},[448,1019,1020,1021,1023,1024,1026,1027,1029],{},"When you view the relationship from the ",[726,1022,696],{}," contact's side, Owlat inverts the label automatically where an inverse is defined — so a ",[513,1025,928],{}," link reads as ",[513,1028,933],{}," from the report's perspective.",[533,1031,1033],{"title":1032,"type":536},"Relationships are manual",[448,1034,1035,1036,1038,1039,1041],{},"Relationships are created by hand from the ",[452,1037,470],{}," tab — there is no production path that extracts them from conversations or the ",[483,1040,106],{"href":105},". The Knowledge Graph does extract people and facts from conversations automatically, but it links them to a contact as knowledge entries, not as typed contact-to-contact relationships.",[533,1043,1045],{"title":1044,"type":536},"Multi-hop graph traversal",[448,1046,1047],{},"The backend can also walk the relationship graph outward by several hops (a contact's relationships, their relationships, and so on). That traversal isn't surfaced in the contact UI yet — the Relationships tab shows direct (one-hop) links only.",[501,1049,1051],{"id":1050},"the-unified-cross-channel-timeline","The unified cross-channel timeline",[448,1053,554,1054,1057,1058,455,1060,455,1063,455,1065,467,1068,1071,1072,1075,1076,1079],{},[452,1055,1056],{},"Unified Timeline"," tab shows the contact's unified multi-channel message log — two-way messages across ",[452,1059,530],{},[452,1061,1062],{},"SMS",[452,1064,604],{},[452,1066,1067],{},"chat",[452,1069,1070],{},"generic"," channels, each marked ",[452,1073,1074],{},"Received"," (inbound) or ",[452,1077,1078],{},"Sent"," (outbound). Messages are sorted newest-first.",[448,1081,1082],{},"Channel-filter pills (All, Email, SMS, WhatsApp, Chat, Generic) let you narrow the feed; selecting a specific channel shows only the message rows for that channel.",[448,1084,1085,1086,1089,1090,1092],{},"The Timeline does ",[452,1087,1088],{},"not"," merge in the activity log. Lifecycle and engagement events (sends, opens, clicks, subscriptions, and more) live on the separate ",[452,1091,454],{}," tab.",[548,1094,1096],{"id":1095},"communication-stats","Communication stats",[448,1098,1099,1100,1103],{},"Alongside the timeline, a ",[452,1101,1102],{},"Communication"," card summarizes the contact's message history:",[653,1105,1106,1116],{},[656,1107,1108],{},[659,1109,1110,1113],{},[662,1111,1112],{},"Stat",[662,1114,1115],{},"What it counts",[669,1117,1118,1126,1134,1142],{},[659,1119,1120,1123],{},[674,1121,1122],{},"Messages",[674,1124,1125],{},"Two-way messages in the unified message log",[659,1127,1128,1131],{},[674,1129,1130],{},"Threads",[674,1132,1133],{},"Conversation threads involving the contact",[659,1135,1136,1139],{},[674,1137,1138],{},"By channel",[674,1140,1141],{},"Message count per channel",[659,1143,1144,1147],{},[674,1145,1146],{},"First \u002F last contact",[674,1148,1149],{},"Earliest and most recent timestamps across messages and activities",[533,1151,1153],{"title":1152,"type":536},"What feeds the timeline today",[448,1154,1155,1156,455,1158,455,1160,455,1162,467,1164,1166,1167,1170,1171,1173,1174,1092],{},"The Timeline shows the unified multi-channel message log across ",[452,1157,530],{},[452,1159,1062],{},[452,1161,604],{},[452,1163,1067],{},[452,1165,1070],{}," channels. The non-email channels are populated by inbound traffic on the channels you've connected (via ",[483,1168,1169],{"href":197},"inbound channel webhooks","). Once you've configured a channel's provider credentials, outbound SMS, WhatsApp, and generic messages (sent from the Timeline composer or by AI agent replies) are dispatched through the provider and recorded as ",[452,1172,1078],{}," rows in the timeline alongside inbound traffic. Email engagement events (sends, opens, clicks, and inbound replies) are recorded in the activity log, which appears on the separate ",[452,1175,454],{},[501,1177,1179],{"id":1178},"activity-types-and-what-they-record","Activity types and what they record",[448,1181,1182,1183,1185],{},"The activity log (shown on the ",[452,1184,454],{}," tab) records lifecycle and engagement events. Owlat tracks the following activity types:",[653,1187,1188,1200],{},[656,1189,1190],{},[659,1191,1192,1194,1197],{},[662,1193,454],{},[662,1195,1196],{},"Label",[662,1198,1199],{},"When it's recorded",[669,1201,1202,1215,1228,1241,1254,1267,1280,1296,1309,1322,1335,1352,1365],{},[659,1203,1204,1209,1212],{},[674,1205,1206],{},[513,1207,1208],{},"created",[674,1210,1211],{},"Contact Created",[674,1213,1214],{},"A contact record is created",[659,1216,1217,1222,1225],{},[674,1218,1219],{},[513,1220,1221],{},"email_sent",[674,1223,1224],{},"Email Sent",[674,1226,1227],{},"A campaign or transactional email is sent to the contact",[659,1229,1230,1235,1238],{},[674,1231,1232],{},[513,1233,1234],{},"email_opened",[674,1236,1237],{},"Email Opened",[674,1239,1240],{},"The contact opens a tracked email",[659,1242,1243,1248,1251],{},[674,1244,1245],{},[513,1246,1247],{},"email_clicked",[674,1249,1250],{},"Link Clicked",[674,1252,1253],{},"The contact clicks a tracked link",[659,1255,1256,1261,1264],{},[674,1257,1258],{},[513,1259,1260],{},"email_bounced",[674,1262,1263],{},"Email Bounced",[674,1265,1266],{},"A send to the contact bounces",[659,1268,1269,1274,1277],{},[674,1270,1271],{},[513,1272,1273],{},"email_complained",[674,1275,1276],{},"Spam Complaint",[674,1278,1279],{},"The contact marks an email as spam",[659,1281,1282,1287,1290],{},[674,1283,1284],{},[513,1285,1286],{},"topic_subscribed",[674,1288,1289],{},"Subscribed to Topic",[674,1291,1292,1293],{},"The contact is added to a ",[483,1294,1295],{"href":17},"topic",[659,1297,1298,1303,1306],{},[674,1299,1300],{},[513,1301,1302],{},"topic_unsubscribed",[674,1304,1305],{},"Unsubscribed from Topic",[674,1307,1308],{},"The contact is removed from a topic",[659,1310,1311,1316,1319],{},[674,1312,1313],{},[513,1314,1315],{},"topic_confirmed",[674,1317,1318],{},"Topic Confirmed",[674,1320,1321],{},"The contact confirms a double opt-in topic",[659,1323,1324,1329,1332],{},[674,1325,1326],{},[513,1327,1328],{},"doi_attested",[674,1330,1331],{},"DOI Attested",[674,1333,1334],{},"Contact-level consent is attested from an external platform on import",[659,1336,1337,1342,1345],{},[674,1338,1339],{},[513,1340,1341],{},"property_updated",[674,1343,1344],{},"Property Updated",[674,1346,1347,1348,1351],{},"A custom ",[483,1349,1350],{"href":13},"property"," value changes",[659,1353,1354,1359,1362],{},[674,1355,1356],{},[513,1357,1358],{},"inbound_received",[674,1360,1361],{},"Inbound Received",[674,1363,1364],{},"The contact sends you an inbound message (e.g. an email reply)",[659,1366,1367,1372,1375],{},[674,1368,1369],{},[513,1370,1371],{},"inbound_replied",[674,1373,1374],{},"Inbound Replied",[674,1376,1377],{},"An automated reply is sent back to the contact",[448,1379,1380,1381,1383,1384,1386],{},"Each activity carries type-specific metadata — for example, an ",[513,1382,1247],{}," activity records the clicked link, and a ",[513,1385,1286],{}," activity records the topic. The Activity tab uses this metadata to render a one-line description under each event.",[533,1388,1390],{"title":1389,"type":801},"Not yet active: inbound_replied",[448,1391,1392,1394,1395,1397,1398,1400],{},[513,1393,1358],{}," is recorded live whenever a contact replies into the ",[483,1396,94],{"href":93},". The ",[513,1399,1371],{}," type is reserved for logging automated replies but isn't written by any live path yet, so you won't see it on real contacts today.",[501,1402,1404],{"id":1403},"exporting-a-contacts-data","Exporting a contact's data",[448,1406,1407,1408,1411,1412,1415,1416,1419,1420,1422,1423,808],{},"The contact detail page has an ",[452,1409,1410],{},"Export data"," button that produces a complete GDPR data-subject-access bundle for one person — everything the instance holds about them, in a single ",[513,1413,1414],{},"contact-\u003Cid>-data-export.json"," download. The bundle includes the contact record plus all of their channel identities, topic memberships, property values, activities, email and transactional sends, automation runs, form submissions, inbound and unified messages, conversation threads, and linked knowledge entries. High-volume collections are capped at 1000 rows each, with a ",[513,1417,1418],{},"truncated"," flag set when more exist. This is the export you answer an access request with — the org-wide CSV export (on the ",[483,1421,178],{"href":177}," list) only covers the base contact rows. Exporting a contact's full data requires the ",[452,1424,1425],{},"organization: manage",[501,1427,1429],{"id":1428},"permissions","Permissions",[448,1431,1432,1433,1435,1436,780,1439,1442,1443,1445],{},"Reading a contact's identities, relationships, and timeline is available to any team member with audience access. Changing them — adding or removing identities, verifying an identity, merging contacts, or creating and deleting relationships — requires the ",[452,1434,807],{}," permission, which is granted to ",[452,1437,1438],{},"owners",[452,1440,1441],{},"admins",". See ",[483,1444,74],{"href":73}," for the full permission matrix.",[501,1447,1449],{"id":1448},"next-steps","Next steps",[758,1451,1452,1457,1462,1467,1472],{},[761,1453,1454,1456],{},[483,1455,178],{"href":177}," — create, import, and organize your audience",[761,1458,1459,1461],{},[483,1460,134],{"href":133}," — connect email, chat, SMS, and WhatsApp",[761,1463,1464,1466],{},[483,1465,94],{"href":93}," — triage inbound replies as a team",[761,1468,1469,1471],{},[483,1470,106],{"href":105}," — structured facts linked to contacts",[761,1473,1474,1476],{},[483,1475,266],{"href":265}," — how contact resolution and identities work under the hood",{"title":1478,"searchDepth":1479,"depth":1479,"links":1480},"",2,[1481,1489,1490,1497,1500,1501,1502,1503],{"id":503,"depth":1479,"text":504,"children":1482},[1483,1485,1486,1487,1488],{"id":550,"depth":1484,"text":551},3,{"id":578,"depth":1484,"text":579},{"id":591,"depth":1484,"text":592},{"id":618,"depth":1484,"text":619},{"id":629,"depth":1484,"text":630},{"id":739,"depth":1479,"text":740},{"id":833,"depth":1479,"text":834,"children":1491},[1492,1493,1494,1495,1496],{"id":862,"depth":1484,"text":863},{"id":868,"depth":1484,"text":869},{"id":881,"depth":1484,"text":882},{"id":892,"depth":1484,"text":893},{"id":899,"depth":1484,"text":630},{"id":1050,"depth":1479,"text":1051,"children":1498},[1499],{"id":1095,"depth":1484,"text":1096},{"id":1178,"depth":1479,"text":1179},{"id":1403,"depth":1479,"text":1404},{"id":1428,"depth":1479,"text":1429},{"id":1448,"depth":1479,"text":1449},"md",{},true,{"title":122,"description":123},"1.guide\u002F35.audience-data","wsA84lxHLiFuPuWq-oSMh-ys0Mrg55Sqq4WkKMR-1f4",[1511,1513],{"title":118,"path":117,"stem":1512,"children":-1},"1.guide\u002F34.code-tasks",{"title":126,"path":125,"stem":1514,"children":-1},"1.guide\u002F36.importing-contacts",1782846430138]