# Twintual - Full Reference

> Complete text of Twintual's glossary, comparisons, role pages, and guides, generated automatically from the site's own content so it stays current. For positioning, pricing and key facts, see /llms.txt.

## Glossary

### Communication Twin
URL: https://www.twintual.com/glossary/communication-twin
A communication twin is a per-person AI trained on one individual's writing style that drafts their replies, meetings, and follow-ups for them to review.
How it works: A communication twin learns from a specific person's actual sent messages and writing patterns across their connected channels. It drafts replies, meeting notes, and follow-ups in that person's own voice, and surfaces them for review. Nothing is sent until the person clicks send themselves.
How it differs: It differs from a single shared company chatbot, which answers in one generic voice for everyone. It differs from an autonomous AI agent, which can act and send without a human checking first. And it differs from a general-purpose assistant like ChatGPT or Claude, which has no memory of how a specific person writes unless it's told each time.
Where Twintual fits: Twintual gives every employee at a company their own communication twin, rather than one shared assistant for the whole organization. Each twin only learns that one person's voice, and every send still requires that person's explicit click.

### Digital Twin (Communication Context)
URL: https://www.twintual.com/glossary/digital-twin-communication
In a communication context, a digital twin is a live model of how one person writes and responds, used to draft in their voice - not a physical machine.
How it works: The industrial and manufacturing use of 'digital twin' refers to a virtual model of a physical asset, built from sensor data, used to simulate and predict how that asset behaves. Applied to communication, the same core idea - a live, continuously updated model of a real thing - is pointed at a person's communication behavior instead of a machine: their tone, phrasing, and the way they typically respond to different kinds of messages.
How it differs: It differs from the industrial digital twin, which models equipment or a process for simulation and predictive maintenance, not a person. It's also a broader concept than 'communication twin' specifically: a communication-context digital twin is the general idea, and a communication twin is one concrete implementation of it - the product feature a person actually uses day to day.
Where Twintual fits: Twintual's twin is a digital twin of a person's communication behavior: it's built from that person's own writing, not from a physical asset, and its purpose is drafting messages in their voice rather than simulating machinery.

### Governed AI Layer
URL: https://www.twintual.com/glossary/governed-ai-layer
A governed AI layer is AI deployed on top of a company's existing tools that keeps human approval and admin oversight in place, rather than acting autonomously.
How it works: A governed AI layer sits on top of a company's existing systems - email, calendar, chat - instead of replacing them. It adds AI drafting and summarization while leaving two things intact: a human still has to approve anything that goes out, and IT/admin retains visibility into how the tool is used, even if not into message content itself.
How it differs: It differs from an autonomous agent layer, where AI can take actions (including sending messages) without a person reviewing each one first. It also differs from shadow AI, where employees adopt AI tools on their own, outside any admin visibility or IT approval at all.
Where Twintual fits: Twintual is built as a governed AI layer on top of Google Workspace or Microsoft 365: it does not replace those tools, every send is an explicit human click, and the admin console gives IT visibility into usage without exposing message content.

### Metadata-Only Administration
URL: https://www.twintual.com/glossary/metadata-only-administration
Metadata-only administration lets admins see usage information - who messaged whom, when, and where - but never the actual content of the messages.
How it works: The admin console shows connection status, which channels are active, and usage patterns at the account level. It does not surface message bodies, drafts, or transcripts. Administrators can confirm the tool is deployed and being used without being able to read what any individual employee wrote.
How it differs: It differs from full-visibility monitoring or DLP-style tools, where an administrator or security team can read message content directly. It also differs from having no admin oversight at all, where IT has no way to confirm usage or troubleshoot deployment issues.
Where Twintual fits: Twintual's admin console is metadata-only by design: admins never see message content, which is the specific answer to the objection IT and security reviewers raise first about any AI communication tool.

### Human-in-the-Loop Messaging
URL: https://www.twintual.com/glossary/human-in-the-loop-messaging
Human-in-the-loop messaging is a workflow where AI drafts a message but a person must click send before it goes out - the AI never sends on its own.
How it works: The AI generates a draft reply, meeting note, or follow-up. That draft is presented to the person it was written for, who can edit it or leave it as-is, and then has to take an explicit action - a click - to actually send it. If they don't act, nothing goes out.
How it differs: It differs from fully autonomous sending, where an AI agent can dispatch a message without any review step. It also differs from a purely manual workflow with no AI drafting at all - human-in-the-loop messaging keeps the AI's speed while keeping a person as the final check.
Where Twintual fits: This is a non-negotiable design choice for Twintual: every send requires an explicit human click, with no autonomous-send mode.

### Shadow AI
URL: https://www.twintual.com/glossary/shadow-ai
Shadow AI is AI tool use inside a company that hasn't been formally evaluated or approved by IT, like an employee using a personal ChatGPT account for work.
How it works: It typically shows up as employees pasting company information into consumer AI tools, installing AI-powered browser extensions, or using AI features embedded in SaaS products IT never reviewed for that purpose. None of it is malicious - people are usually just trying to get their work done faster - but none of it is visible to, or controlled by, IT.
How it differs: It differs from a governed AI layer, which IT evaluates and approves once and which stays visible through admin metadata. It's a category of risk, not a specific tool - the same person can use both a governed tool at work and shadow AI for a task the governed tool doesn't cover.
Where Twintual fits: Twintual is positioned as the governed alternative that gives employees AI drafting without pushing them toward shadow AI: once IT approves and deploys it, there's less reason for someone to paste company communication into an unapproved consumer tool instead.

### AI Communication OS
URL: https://www.twintual.com/glossary/ai-communication-os
An AI communication OS is an AI layer that runs across every channel a company uses to communicate, rather than living inside a single app.
How it works: Instead of an AI feature bolted onto one product - a smart-reply button in one inbox, a summarizer in one chat app - an AI communication OS sits underneath all of them: mail, calendar, chat, and messaging. It provides drafting, summarization, and prioritization as one consistent layer, regardless of which channel a given message came in on.
How it differs: The broader 'AI operating system' idea in enterprise software describes a general orchestration layer for AI agents, data, and workflows across a whole business, not specifically communication. An AI communication OS is that idea scoped to one domain: messaging and correspondence. It's also a broader term than 'governed AI layer' - a governed AI layer is a specific, constrained kind of AI communication OS, one where sending stays human-in-the-loop and admin visibility stays metadata-only, rather than a description that applies to any implementation.
Where Twintual fits: Twintual functions as an AI communication OS across Google Workspace or Microsoft 365, Teams, Slack, and WhatsApp Business - one layer, not a separate feature per app. It's specifically a governed one: no autonomous sending, no content-level admin visibility.

### Unified Inbox
URL: https://www.twintual.com/glossary/unified-inbox
A unified inbox brings messages from multiple channels - email, chat, and messaging apps - into one place to read and respond from, instead of checking each app separately.
How it works: A unified inbox connects to a person's various accounts and channels and surfaces their messages in a single interface. At its simplest, that's just aggregation: one list to scroll instead of several apps to open. More capable versions add prioritization or grouping on top, but the core function is consolidation, not drafting.
How it differs: It differs from a governed AI layer, which is a broader concept: a unified inbox solves where you look, but says nothing on its own about who drafts replies, in whose voice, or what an administrator can see. A tool can be a unified inbox without including AI drafting at all, and a governed AI layer typically includes unified-inbox-style consolidation as one part of a larger system, not the whole of it.
Where Twintual fits: Twintual includes unified-inbox-style channel consolidation as one piece of its governed AI layer - but the differentiator is what's layered on top of that consolidation: a per-person communication twin that drafts in that individual's voice, human-in-the-loop sending, and metadata-only admin visibility.

### Message Handling Time
URL: https://www.twintual.com/glossary/message-handling-time
Message handling time is the total time someone spends reading, triaging, and drafting replies to messages across all of their communication channels.
How it works: It covers the full cycle of dealing with a message, not just replying to it: noticing it, deciding whether and how urgently to respond, and composing the reply. Someone can have a fast average response time and still lose hours a day to message handling time, if triage and drafting themselves are slow.
How it differs: It differs from response time or SLA metrics, which measure how quickly a reply goes out after a message arrives - a latency measure, not an effort measure. It also differs from general screen time, which includes time on channels unrelated to correspondence.
Where Twintual fits: Reducing message handling time is the productivity case Twintual makes to operations teams, executive assistants, and customer-facing teams: less time spent reading and triaging by consolidating channels into one layer, and less time spent drafting because a communication twin produces a starting draft instead of a blank page.

### Context-Switching Cost
URL: https://www.twintual.com/glossary/context-switching-cost
Context-switching cost is the time and focus lost when someone moves between different apps or tasks and has to re-orient before they can continue working.
How it works: Every time someone leaves a task to check a different app - a chat notification, a separate inbox - they don't return to full focus immediately. A widely cited 2008 study by Gloria Mark at UC Irvine, 'The Cost of Interrupted Work,' found people took an average of 23 minutes and 15 seconds to return to an interrupted task at the same level of focus.
How it differs: It differs from message handling time, which is about the effort of dealing with messages themselves. Context-switching cost is specifically about the interruption tax of moving between separate tools to reach those messages in the first place - the two compound when communication is spread across many apps, but they're distinct costs.
Where Twintual fits: Consolidating channels into one governed layer reduces how often someone has to switch apps just to check whether something needs their attention - the mechanism covered in more detail in the message-handling-time guide.

## Comparisons

### Twintual vs. Microsoft Copilot
URL: https://www.twintual.com/compare/microsoft-copilot
Both put AI drafting inside your existing tools. The real difference is what each one sees and who it's trained on.
Where Microsoft Copilot does better: If your company runs entirely on Microsoft 365, Copilot's integration into Word, Excel, and Outlook is native in a way no third-party layer can fully match. Copilot inherits Microsoft 365's existing compliance, eDiscovery, and enterprise-admin tooling directly, which matters if your organization is already deep into that ecosystem. Microsoft's scale means Copilot ships broad document- and spreadsheet-level AI features well beyond messaging, which Twintual doesn't attempt to cover.
Where Twintual wins: Twintual works across Google Workspace and Microsoft 365 at once, plus Teams, Slack, and WhatsApp Business - useful for any company that isn't 100% Microsoft. Each person gets a twin trained specifically on their own writing, rather than one general assistant experience shared across the company. A metadata-only admin model built specifically around never exposing message content, as the core design choice rather than a configuration option.

### Twintual vs. Generic AI Assistants
URL: https://www.twintual.com/compare/generic-ai-assistants
General-purpose assistants are excellent at open-ended tasks. They aren't built to live inside your inbox and know your channels.
Where Generic AI assistants (like ChatGPT or Claude) does better: General-purpose assistants are far more flexible for open-ended work - research, writing from scratch, coding, analysis - that isn't about drafting a reply inside a specific channel. No setup or channel connection required; you can start using one immediately for a one-off task. Broader reasoning and general knowledge than a tool scoped specifically to communication.
Where Twintual wins: Twintual connects directly to your actual inbox, calendar, and chat channels - no copy-pasting drafts back and forth. It learns your writing automatically from what you've already sent, rather than needing to be reminded of your style each session. It's deployed by the company with a metadata-only admin layer, which is what most IT and security reviewers ask for and a personal chat account can't provide.

### Twintual vs. a Unified Inbox Tool
URL: https://www.twintual.com/compare/unified-inbox-tools
Unified inboxes solve where you look. Twintual also drafts what you say - in your own voice, with a human still clicking send.
Where a unified inbox tool does better: Purpose-built unified inbox tools are often stronger at pure inbox organization - filtering, snoozing, and triage views - since that's their whole focus. Some offer a genuinely unified single view across more niche channels than Twintual currently covers. Lighter-weight setup if all you need is one place to see everything, with no drafting involved.
Where Twintual wins: A unified inbox tells you where to look; Twintual also drafts the reply in your own voice, so it addresses handling time, not just visibility. Company-wide deployment with a metadata-only admin layer, rather than a personal tool with no organizational oversight. Every send still requires a human click, so consolidation doesn't come with reduced control over what goes out.

### Twintual vs. Doing Nothing
URL: https://www.twintual.com/compare/status-quo
The real alternative to any AI communication tool is what a team already does: switch between five apps and answer everything manually.
Where the status quo (no tool) does better: Zero setup, zero new tool to learn, zero risk of the kind that comes with adopting new software. No dependency on a vendor, no data flowing through an additional layer. For a very small team with low message volume, the overhead of any tool may simply not be worth it yet.
Where Twintual wins: Consolidates channels that are currently handled separately into one governed layer, rather than leaving people to context-switch between five apps. Drafts replies in each person's own voice instead of every message being composed from scratch. A 15-day trial with no credit card makes the cost of testing this against the status quo low.

## For your team

### Twintual for Operations Teams
URL: https://www.twintual.com/for/operations-teams
Ops runs on messages - supplier updates, internal escalations, customer handoffs - scattered across every channel the company uses.

### Twintual for Executive Assistants
URL: https://www.twintual.com/for/executive-assistants
You manage someone else's inbox, calendar, and reputation across channels they don't have time to check themselves.

### Twintual for Customer-Facing Teams
URL: https://www.twintual.com/for/customer-facing-teams
In client-facing roles, a slow or generic-sounding reply reads as a signal about how much the relationship matters.

### Twintual for IT and Security Reviewers
URL: https://www.twintual.com/for/it-security-reviewers
Before any AI tool touches company communication, someone has to answer: what does it see, and who controls what it does.

## AI Assistant by channel

### Gmail AI Assistant
URL: https://www.twintual.com/ai-assistant/gmail
Twintual is an AI assistant for Gmail that drafts replies in your own writing voice inside your existing inbox - it doesn't replace Gmail, and nothing sends until you click.

### Outlook AI Assistant
URL: https://www.twintual.com/ai-assistant/outlook
Twintual is an AI assistant for Outlook that drafts replies in your own voice on top of Microsoft 365 - not a replacement for Outlook, and every send still needs your click.

### Slack AI Assistant
URL: https://www.twintual.com/ai-assistant/slack
Twintual is an AI assistant for Slack that drafts replies and catches you up on threads in your own voice, deployed on top of your existing Slack workspace.

### WhatsApp Business AI Assistant
URL: https://www.twintual.com/ai-assistant/whatsapp-business
Twintual is an AI assistant for WhatsApp Business that drafts customer and partner replies in your own voice - built for WhatsApp Business specifically, not personal WhatsApp.

## Guides

### The Governed AI Layer for Enterprise Communication
URL: https://www.twintual.com/guides/governed-ai-layer-enterprise-communication
What it means to add AI to a company's communication without losing control of who sends what, and why that distinction is the whole category.
What a governed AI layer is: A governed AI layer is AI functionality added on top of a company's existing tools - not a replacement for them - that keeps two things intact: a human approves every outbound message, and administrators retain visibility into how the tool is used. It sits between two failure modes companies are trying to avoid: fully autonomous AI agents that can act without review, and ungoverned shadow AI that employees adopt on their own with no IT visibility at all.
Why this is a category, not a feature: Most AI communication tools are described by what they can draft. Fewer are described by what they're structurally prevented from doing. A governed AI layer is defined by its constraints as much as its capabilities: no autonomous sending, and no content-level admin surveillance. Those constraints are what make an AI tool adoptable inside a company that has a real IT and security review process, rather than something that spreads informally, one employee at a time.
The per-person twin, not a shared assistant: Inside a governed AI layer, the unit of AI is usually the person, not the company. A communication twin is trained on one individual's own writing and drafts on their behalf - closer to a digital twin of how that person communicates than to a single shared chatbot everyone talks to. That distinction matters for voice: a company-wide assistant answers in one generic register; a per-person twin sounds like the person it represents.
Where Twintual fits: Twintual is a governed AI layer deployed on top of Google Workspace or Microsoft 365, covering Teams, Slack, and WhatsApp Business as well. Every employee gets their own communication twin trained on their own writing. Every send is an explicit human click. The admin console is metadata-only. Those are product constraints, not configuration options.

### Metadata-Only Administration and Human-in-the-Loop AI
URL: https://www.twintual.com/guides/metadata-only-administration-human-in-the-loop-ai
The two design constraints that make an AI communication tool something a security team can actually approve.
The question every security review starts with: Before an AI communication tool gets anywhere near a company's inboxes, IT and security ask a version of the same question: what does this tool - and its administrators - actually have access to? For a lot of AI products, the honest answer includes message content. That's the specific gap metadata-only administration is built to close.
Metadata-only administration, concretely: Metadata-only administration means the admin console shows usage information - who messaged whom, when, and through which channel - without ever surfacing message content itself. It's a narrower promise than "we take security seriously," and a checkable one: an admin trying to read an employee's message in that console simply can't, because the content was never made available to that view in the first place.
Human-in-the-loop as the second constraint: Metadata-only administration answers "what can an admin see." Human-in-the-loop messaging answers a different question: "what can the AI do on its own." The answer, in a governed system, is nothing that reaches another person without an explicit human click. AI drafts; a person decides. There's no autonomous-send mode to disable, because there isn't one to begin with.
Why this matters more as shadow AI grows: Gartner predicts more than 40% of enterprises will experience a security or compliance incident linked to unauthorized shadow AI by 2030, based on a 2025 survey of cybersecurity leaders (Gartner, "Gartner Identifies Critical GenAI Blind Spots That CIOs Must Urgently Address," November 2025). Shadow AI grows precisely where there's no approved, governed alternative - employees under time pressure reach for whatever gets the job done, IT visibility or not. A metadata-only, human-in-the-loop tool that IT can actually approve is a direct answer to that gap, not just a compliance checkbox.
Where Twintual fits: Twintual's admin console is metadata-only by design, and every send requires an explicit human click - there is no setting that changes either of those. Both are covered in more detail on the security page.

### Reducing Message Handling Time and Context-Switching Cost
URL: https://www.twintual.com/guides/reducing-message-handling-time
The productivity case for a communication layer, in the reader's own terms: less time spent switching apps and drafting from scratch.
Two different costs get bundled together: "Communication overload" usually mixes two separate costs: the time spent actually composing replies, and the time lost switching between the apps where those replies live. They compound - every extra channel adds both more messages to answer and more app-switching to reach them - but they're solved differently. Drafting help addresses the first. Consolidating channels into one layer addresses the second.
What interruption actually costs: A frequently cited 2008 study by Gloria Mark at UC Irvine (with colleagues at Humboldt University Berlin), "The Cost of Interrupted Work," found that after a single interruption, people took an average of 23 minutes and 15 seconds to return to the original task at the same level of focus, and tended to compensate by working faster afterward - at the cost of more stress and time pressure. That's third-party academic research, not a Twintual figure, and it's specifically about interruption cost, not about any particular tool's impact.
Where a communication twin changes the math: A twin trained on a person's own writing removes the blank-page part of drafting - the reply still gets reviewed and sent by a human, but it doesn't start from nothing. Combined with one layer across channels instead of five separate apps, the two constraints being addressed are: less time composing, and fewer context switches to reach the message in the first place.
Where Twintual fits: This is the productivity case for the three role pages that link here: operations teams juggling supplier and internal channels, executive assistants matching a specific voice at volume, and customer-facing teams where response time and tone both matter. The mechanism is the same in each case - fewer channels to check separately, and a drafted starting point instead of a blank page - applied to different volumes and stakes.

## Frequently asked questions

Q: Does Twintual replace our Microsoft or Google tools?
A: No. Twintual works on top of your environment - Google Workspace or Microsoft 365 - and adds the twin layer across your channels.

Q: Can admins read employees' messages?
A: No. The admin console is metadata-only - admins never see message content.

Q: Does Twintual send anything on its own?
A: No. Every send is an explicit human click.

Q: Which channels does Twintual cover?
A: Google Workspace and Microsoft 365 for mail and calendar, plus Teams, Slack and WhatsApp Business.

Q: Where does our data go?
A: One governed space your company controls. We'll walk your security team through the details.

Q: Does the free trial need a credit card?
A: No. The 15-day trial starts without a card. You only add payment when you choose a plan.

Q: How is the Company plan priced?
A: An annual platform fee plus per-user pricing plus implementation, scoped to your channels, teams and controls. Talk to sales and we'll map it with you.

Q: When am I charged on the individual plans?
A: Your card is charged when you subscribe, and the plan renews each billing cycle. Cancel anytime.

Q: Can I switch plans later?
A: Yes. Upgrade or downgrade anytime; changes apply at the next billing cycle.