Aeion Inbox for Shared Team Inbox
Teams sharing support@, sales@, billing@, info@ inboxes typically use personal Gmail accounts — no visibility into each other's work, duplicate responses, missed messages, no shared visibility into who's handling what. Front, Help Scout, Hiver, Missive solve this with shared inbox tools ($9-49/user/mo). Aeion Inbox is native to Aeion OS with assignment, filter rules, AI-assisted triage, and CRM-linked customer context. Three operating-model walkthroughs below.
The Personal-Gmail-as-Shared-Inbox Problem
`
Walkthrough 1 — Customer Support Team
`
Walkthrough 2 — Sales Team Inbox (sales@)
`
Walkthrough 3 — Operations Team Inbox (ops@)
`
Cross-Module Power
`
FAQ
There's a Singularity connector for Help Scout (conversations, customers) today; it imports into Aeion Support/Helpdesk collections, not directly into Inbox conversations, so plan for a mapping step. There's no dedicated Front connector — for Front, or for a true drop-in Inbox migration, expect a CSV/API-based one-time import rather than a native connector.
You can connect multiple shared inboxes (support@, sales@, etc.), each with its own filter rules and its own shared-vs-private visibility setting.
Yes. OAuth 2.0 with Microsoft Graph API, same conversation/message model as Gmail.
Yes — connect a personal account and mark it private (visible only to the linked user), or shared, so it behaves as a team inbox.
Per-account HTML signatures, with a default-signature toggle per account.
Not a dedicated mobile app for this feature set today — check current availability before committing to a mobile rollout plan.
Sending is per-account (from support@, from sales@, etc.), matched to the account you're replying from.
Yes — a configurable embeddable chat widget (welcome message, color, allowed domains) that routes conversations into the connected shared inbox.
Gmail-style search operators (`from:`, `subject:`, `is:unread`, `before:`/`after:`, etc.) work across connected accounts. There's no separately advertised message-count ceiling for this — it's a standard indexed query, not a special large-archive feature.
Conversations carry an SLA timer that shows how much time is left before a conversation breaches its response target, with breach alerting. Priority and status are set per conversation.
Yes — templates support a `{{variable}}` list, filled in manually when you use the template. There's no automatic pull from CRM fields today.
Credentials are encrypted at rest, and account visibility controls who can see a mailbox's conversations. There's no Inbox-specific retention/erasure automation beyond the platform's general data-handling controls — check with your Aegis/compliance settings for tenant-wide retention policy.