Good follow-through starts with clear boundaries.
Understand what the system can do, what requires your approval, and where the current pilot stops.
This is a functional pilot, not an independently audited production service. These controls describe the implementation; they are not a security certification or a compliance guarantee.
People approve. Models propose.
Optional AI drafting has no tools, mailbox access or execution authority. Recipients are selected explicitly. An approved plan is required before sends are queued; changed follow-ups need fresh approval. Teams can require a different approver and pause or cancel future work.
Workspace access and sign-in
Server-side permissions separate admin, operator, reviewer and viewer roles. Record operations are scoped to the authenticated workspace. Sessions use HTTP-only cookies, request-origin and CSRF checks, rate limits and revocation. Optional TOTP two-factor authentication includes one-use recovery codes. MFA is not mandatory across all accounts.
Delivery and open signals
Signed provider events record delivery, delays, failures, bounces and complaints. Optional open tracking records approximate signals when configured and enabled. Delivery means receipt by a mail server; open signals can come from privacy tools or image prefetching. Neither proves reading, completes a task or stops a follow-up. Sandbox events are labelled and excluded from live metrics.
Storage and audit history
Business record payloads use authenticated encryption. Signed, chained audit entries and database triggers protect the normal application history from update and deletion. Database connections verify certificates and hostnames. User identities, membership and indexing metadata are not application-encrypted. These measures do not replace tested backups or externally retained audit records. Flow histories include individual task and email changes, approvals, scheduler decisions, provider events, replies and review evidence. Older events can be loaded in Activity, and admins can export the complete recorded history.
Replies are untrusted input
A matched reply from a linked mailbox, or a reply recorded manually, stops pending sends for the request and requires review. Text received from a client cannot change permissions, approve a plan or become an execution instruction.
Available, optional and planned
Editable plans, approvals, working-day scheduling, sandbox sends, contacts, suppression, manual replies, checklists, evidence notes, team roles, reports, exports, audit history, optional MFA and a mailbox reader with clickable thread highlights. Mailbox features require provider setup and consent.
AI drafting, Google Workspace and Microsoft 365 mailbox connections, and live Resend delivery, plus account emails for sign-up and password recovery. Resend sending also requires a verified sending domain and explicit workspace enablement. A configured integration does not by itself prove successful delivery.
Attachment downloads and validation, shared mailbox delegation, a document-upload portal, enforced SSO/MFA and published commercial pricing.
Before handling real client work
Independent security review, tested backup restores, monitoring and alerts, retention and deletion controls, account recovery and live-provider reconciliation remain required work. Use synthetic data for evaluation and confirm the operating requirements before a live rollout.