Group Inboxes give your team a shared home for inbound email in one place — read it, reply to it, and analyze what arrives with it. Each inbox gets its own dedicated receiving address you can forward mail to, and you can import existing mailbox history from a standard mbox export. Every imported or received conversation becomes searchable, threaded data — and where graph analytics is enabled, inbox activity powers the Data Analyst dashboards and filters.
flowchart LR
A[Forwarded mail to the inbox address] --> C[Group Inbox]
B[mbox history import] --> C
C --> D[Threaded, searchable conversations]
D --> E[Data Analyst dashboards and filters]
agents:mail:read) — this controls whether Group Inboxes appears in your CRM menu (under Daily work).To capture mail sent to an address on your own domain (support@yourcompany.com, a teammate's mailbox), see Routing Your Email Into KarmaFlow — it covers Google Workspace and Microsoft 365, and the CRM-timeline destination as well.
…@sys.karmaflow.ai address mail is forwarded to; it is registered with the mail provider so messages route into the inboxA dedicated inbound email address is generated and registered for the inbox automatically — you'll see it at the top of the inbox page after creation, with a Registered badge once it can receive mail. Forward or route mail to that address and it appears in the inbox.
From an inbox's page you can:
Bring in past conversations by uploading a standard mbox export (the format most mail providers, including Google Takeout, produce):
.mbox fileThe inbox lists conversations with their Subject, From participants, message count, and the date of the latest message. Search and pagination cover the whole inbox.
Select a thread to review the full conversation:
Click Reply on a thread to answer the latest inbound message — the button is in the thread header on desktop, and a floating button in the lower-right corner on a phone. The reply threads correctly in the recipient's mail client, appears in the thread alongside the received messages, and supports CC, signatures, and file attachments.
Who the reply comes from: the compose window's From dropdown lists your workspace's sender profiles, defaulting to the inbox's own Reply from profile — set it via Edit on the inbox page, and pick the profile matching the address that routes into the inbox (so replies come from the address the sender originally wrote to). Sending requires the crm:contacts:edit permission and at least one verified sender profile (Settings → Notifications).
Each stored attachment carries an Analyze button: one click runs AI document analysis — a document-type classification (invoice, contract, proposal, receipt…), a one-line summary, and extracted fields for financial documents. Supported: images, PDFs up to 8MB, and Word documents (.docx). Each analysis is billed as AI usage, results are saved on the attachment so you only pay once, and the workspace's AI kill switch is honored.
Tenant admins can also opt in to automatic analysis of qualifying inbound attachments — governed by file-size, file-type, per-inbox, and daily-cap limits — under Tenant Settings → Agents & AI → Attachment Intelligence. It is off by default.