Beyond Static Text Bubbles
Intelligent Messaging
Every message is a typed, structured payload — rendered as native UI on every platform. Approvals, forms, workflows, and custom schemas, all within the end-to-end encrypted boundary.
Content-Agnostic Transport
Messages that do things. Not just say things.
On most platforms, a message is a string of text with an optional attachment. On InTouch, every message is a typed, structured payload inside a MessageEnvelope — rendered as native UI on the recipient's device.
Approvals, forms, scheduling, invoices, and custom schemas all travel through the same content-agnostic transport. The Asgard Protocol encrypts every envelope identically — the server cannot distinguish a text message from a fund transfer approval.
Unknown message types gracefully degrade to fallback_text, ensuring forward compatibility as new types are introduced.
Content-agnostic by design: The transport layer imposes no structure — the typed schema lives entirely within the encrypted payload. This means new message types can be deployed without any server-side changes.
Message Type Taxonomy
47 built-in types. Unlimited custom.
Four tiers of message types — from basic content to fully custom industry schemas. Every type is encrypted identically and renders as native UI.
Content Types
Core media and data types. Text, rich text, images, video, audio, files, locations, contacts, and more.
Native UI Rendering
Native on every platform. No web views.
Message types are rendered using each platform's native UI framework — not embedded browsers or web views. This means platform-native performance, accessibility, and interaction patterns on every device.
Every message type renders as a native SwiftUI view — no web views, no embedded browsers. Interactions stay within the app sandbox.
Material 3 composables render each type natively. Platform gestures, haptics, and accessibility features work out of the box.
React components render each type with full keyboard navigation and responsive layout. The same typed schemas, optimised for desktop.
Sandboxed Execution
Interactive UI components run in isolation — they cannot access the encryption layer, other messages, or device capabilities beyond their declared scope.
Graceful Degradation
When a client encounters an unknown message type, it renders the fallback_text field as plain text. Users always see something meaningful, even on older app versions.
Here's the request for your review
Q3 Budget Allocation
Marketing Department
In Practice
Complete business processes inside the conversation
No switching between apps. No insecure external links. Every interaction happens within the end-to-end encrypted boundary.
Property Listing Card
Real EstateFull property details — photos, floor plan, price — rendered as an interactive card with a "Book Viewing" action button. The agent sends a single typed message, not a text block with attachments.
4-Bed Victorian Terrace
Fund Transfer Approval
Financial ServicesAn approval card with amount, counterparty, compliance flags, and approve/decline actions. The entire interaction — including the decision — stays within the E2EE boundary.
Wire Transfer — Meridian Capital
Acquisition escrow · Deal Room #DR-2847
Appointment Booking
HealthcareA scheduling message with available slots, provider details, and one-tap booking. No need to leave the secure conversation to interact with an external calendar system.
Dr. Sarah Chen
Cardiology · Royal London HospitalAvailable Slots
Insurance Claim Card
InsuranceA claim submission card with incident details, document upload, and status tracking — all rendered inline. Adjusters and claimants communicate within the same encrypted Space.
Motor Claim — Rear Collision
Policy #POL-8842 · Filed 3 Jul 2026
Security Guarantee
Every type, the same ciphertext.
The server cannot distinguish a text message from an approval form, an invoice from a prescription. All 47+ types are identical opaque blobs.
type: text
Text message
type: approval
Approval form
type: invoice
Invoice
type: custom.*
Custom schema
All four messages are indistinguishable at the transport and server layer. Type resolution happens on-device after decryption.
Rich workflows + E2EE: choose both
WhatsApp Flows
Meta processes flow data server-side. Interactive workflows are not end-to-end encrypted.
Signal
Strong E2EE, but limited to text, images, files, and attachments. No interactive message types.
iMessage
E2EE for iMessage-to-iMessage, but no structured business workflows or typed schemas.
Teams / Slack
Rich integrations and workflows, but no end-to-end encryption. Admins and platform can access content.
InTouch
The only platform with interactive business workflows inside the E2EE boundary. 47 typed schemas, all encrypted identically.
Get started
Messages that work. Encryption that holds.
Experience intelligent messaging first-hand. Approvals, forms, and workflows — all within the end-to-end encrypted boundary.