Skip to main content
Communication & Email

The right decisions come from the right context, every message, right where your decisions happen

Start freeView all features
6+ channel types
Customer portal built in
Collision detection
Topics across modules
Communication
  • Mosic Logo
Totrox
Communication
Views
Channels
Work Gmail
99+
Company Outlook
99+
Archive99+
Drafts
Inbox99+
Sent84
Junk
Deleted
Projects Chat
Support Channel
JM
James Miller
Inbox·james.m@acmecorp.com
4 conversations · 3 unread

Database Migration Plan - PostgreSQL to CockroachDB

Open
Company Outlook· 4 msg ·
James MillerPhase 1 covers schema migration with zero-downtime

Re: Migration - Data Validation Strategy

Open
2
Company Outlook· 3 msg ·
Marcus JohnsonData validation scripts ready for testing

Re: CockroachDB Compatibility Matrix

Open
1
Company Outlook· 2 msg ·
James MillerCompatibility matrix confirmed, all queries supported

Re: Rollback Plan Review

Open
Company Outlook· 2 msg ·
Marcus JohnsonRollback procedure tested in staging environment

Every conversation, in context

Mosic doesn't just give you a shared inbox. It connects every message, whether it came from email or your customer portal, to the people, deals, tickets, and tasks it belongs to, so you always know the full story before you hit reply.

Shared Channels
Every email account, every inbox, one place for your team
Customer Portal Messages
Portal conversations land next to your email, visible on every deal and ticket
Threaded Conversations
Every reply grouped, every thread tracked, nothing falls through
Unified Composer
Write, template, schedule, and send without leaving the page
Topics
Every message about one thing, from any channel, gathered in one place
Real-time Presence
See who's viewing, who's typing, never send a double reply again
Connected to Everything
See every conversation inside contacts, deals, tickets, tasks, and projects
Daily Views Integration
Your conversations show up in Today and Inbox, right next to your tasks

How it works

Plan your channels, reply in context, manage your team's conversations, and connect every message to the work behind it.

Set up channels in three minutes, not three hours

Connect your team's email to Mosic with a three-step wizard. Enter your address, Mosic auto-discovers your IMAP and SMTP settings from a database of providers. Pull existing emails or start fresh. Set your sync interval from 2 to 60 minutes. Add multiple folders, not just inbox. One channel per team, per project, per function, each with its own signature and auto-reply rules.

  • Auto-discovery: Gmail, Outlook, Yahoo, ProtonMail Bridge, SendGrid, and custom IMAP
  • 6 pull intervals: from every 2 minutes to every hour, per channel
  • Initial sync: pull your last 50 to 500 emails, or the last 1 to 12 months
  • Multi-folder sync: inbox, sent, archive, spam, custom folders, all configurable

Write, reply, send, right where the work is

Your team doesn't just email. They work deals, resolve tickets, and manage projects. The UnifiedComposer lives inside every entity: the contact page, the deal page, the ticket page, the task page. Reply inline. Compose new. Insert a template. Schedule for Monday. Add CC and BCC. Resize the editor, or go full-screen for focus mode. Drafts auto-save so you never lose your work. Bounce warnings flag blocked addresses before you send.

  • Reply or compose from any entity: contacts, leads, deals, tickets, tasks, projects
  • Rich formatting: bold, lists, tables, images, code blocks, and full toolbar
  • Email templates with variables: customer name, ticket subject, agent name, company
  • Scheduled sending: quick options or custom date and time, cancel anytime

Know who's handling what, without asking

Open conversations stay open. Assigned ones have an owner. Stale ones get auto-closed after a configurable window. You see presence avatars on every conversation: who's viewing, who's typing. If two agents start replying to the same thread, a collision banner appears with a preview of the other person's response. No more "sorry, I already replied to that." Bulk actions let you archive, tag, assign, and close conversations by the dozen.

  • 6 conversation statuses: Open, Pending, Waiting, Resolved, Closed, Archived
  • Real-time presence: viewing and composing indicators, collision detection banner
  • Auto-close: resolved conversations close after X hours of inactivity, configurable
  • Bulk operations: archive, tag, assign, close, mark read, delete, all at once

Every message, linked to the work it's about

A client emails about their renewal. That message shows up in the conversation, on their contact page, inside the deal, on the ticket, and in the daily Today view. A customer messages through the portal about a bug. Same thing: it lands on the ticket, the contact, and the project. Topics group all of it by theme: every email and portal message about the Q2 campaign lives under one topic, whether it came from three different senders across two channels. Create a task straight from a message. The message body becomes the task description, the topic links automatically.

  • Messages inside contacts, leads, deals, tickets, tasks, and projects, email and portal alike
  • Topics: every message about one thing, from any channel, gathered in one place
  • Create tasks from messages: body becomes description, topic auto-links
  • Read receipts: sent, delivered, read, so you know it landed

Ready to make better decisions?

Connect your email, bring in your customer portal, and let every message travel with the work. Free to start, no credit card required.

Get started freeSee all features
No credit card required
Cancel anytime
Free plan available

See how each piece works

Every feature has a job. Here's what it does, why it matters, and how it fits into your team's day.

Shared Channels: One inbox, every provider

You connect your Gmail. Your colleague connects Outlook. A third person adds a custom IMAP address. All three appear in Mosic as channels, each with its own pull interval, signature, and auto-reply rules. Conversations from all three show up in one shared inbox, color-coded by channel type. Your team never has to figure out which inbox a message landed in, because they all land in the same place. Circuit breaker protection means if one provider goes down, the others keep pulling. The unhealthy channel shows a warning badge, you reset it when it's fixed, and nothing is lost.

What's inside

  • Multi-provider: Gmail, Outlook, Yahoo, custom IMAP, all in one view
  • Per-channel pull intervals from 2 to 60 minutes with circuit breaker protection
  • Auto-discovery for 6+ providers, including ProtonMail Bridge and SendGrid
  • Multi-folder sync: inbox, sent, archive, spam, and custom IMAP folders

Customer Portal: Their voice, right inside your workspace

Your customers message you through the portal on a ticket, a task, or a project. That message doesn't disappear into a separate system. It lands next to your email in the same inbox, with its own conversation thread, its own history, and its own link back to the thing it's about. Your support team sees it alongside their email tickets. Your account manager sees it on the deal page. Your project manager sees it on the project board. One customer, one conversation history, no matter which door they walked through. Customers don't have to guess which channel to use. Your team doesn't have to check a second system. It's all there, in the same place, on the same page, every time.

What's inside

  • Portal messages and email threads in one inbox, not two separate systems
  • Customers message from the portal on any ticket, task, or project
  • Every team sees portal conversations on the entity they work on: deals, tickets, projects
  • No more losing customer messages because they chose the wrong channel

Threaded Conversations: The full story, every time

An email arrives from a client. Mosic reads the threading headers and groups it with every reply that came before it. The conversation gets a status: Open. It gets an assignee: the person who should respond. It gets a follower list: everyone who needs to know. Six statuses track the lifecycle from Open through Pending and Waiting to Resolved, Closed, and Archived. Stale conversations auto-close. New messages on a closed conversation re-open it. You never lose track of a thread because the status and assignment are always current.

What's inside

  • Auto-threading via In-Reply-To and References email headers
  • 6 statuses: Open, Pending, Waiting, Resolved, Closed, Archived
  • Assignees and followers with notification preferences per conversation
  • Auto-close resolved conversations, auto-reopen on new inbound messages

Unified Composer: Write like it's your full-time job

You hit reply on a client email. The composer opens inline with the channel indicator, the topic pill, and the To field pre-filled. You type. Rich text: bold, lists, tables, images, code blocks. You need the pricing template: tap the template button, pick it, fill in the variables (customer name, deal amount, agent name), and the body populates. You want to send it Monday morning: tap the clock, pick "Next Monday 9am," and it queues. You need to focus: hit expand, then expand again, then go full-screen. The rest of the screen disappears. Your draft auto-saves every few seconds. You accidentally close the tab. You come back. The draft is there.

What's inside

  • Rich text editor with full toolbar: formatting, tables, images, code, alignment
  • Email templates with variable substitution, searchable by category
  • Schedule send: quick options (1 hour, tomorrow, next week) or custom date/time
  • Focus mode: expand to half-screen, then full-screen with keyboard shortcuts

Topics: The full customer story, no matter where you're standing

A customer emails support about a bug. Then they message through the portal about the same issue. Then their manager replies to an old deal thread mentioning the rollout delay. Three channels, three conversations, one customer who expects you to know what's going on. Topics tie all of it together. Tag every conversation under one topic and the whole picture appears: the support agent sees the deal context, the account manager sees the bug report, the project manager sees the client's frustration building. Open the topic and every message sits in one chronological timeline, no matter which channel it came from or who sent it. Link that topic to the deal, the ticket, the task, and the project, and it shows up on every page. Sales knows what support promised. Support knows what the client already heard. The project team knows the scope changed before the meeting. One story, one place, everyone reading from the same page.

What's inside

  • Gather conversations from email, portal, and any channel into one view
  • Everyone sees the full context: sales, support, and project teams all read the same story
  • Link topics to deals, tickets, tasks, and projects so the context follows the work
  • Turn any message into a task in one click: the topic follows, no copy-paste

Real-time Collaboration: No more double replies

Two support agents open the same conversation at the same time. In a regular shared inbox, they both reply. The customer gets two answers, maybe contradictory. In Mosic, presence avatars appear in the conversation header: Sarah is viewing, her avatar glows yellow. Marcus starts typing, his avatar switches to red with a "composing" dot. A collision banner slides in at the top of Marcus's screen: "Sarah replied: Hi, let me check on that..." He reads the preview, decides to wait. Sarah sends her reply. Marcus sees the new message appear in real-time. Zero double replies. Your team looks coordinated because it is coordinated.

What's inside

  • Presence avatars: yellow for viewing, red for composing, with status dots
  • Collision banner: real-time preview of the other person's reply
  • Typing indicators in message threads
  • WebSocket-powered: new messages, status changes, and assignments appear instantly

Connected to Everything: The messages tab that travels

You open a contact's page. The messages tab shows every conversation they've ever had with your team, email and portal, sorted by date. You open a deal. Same tab, same conversations, filtered to that deal's linked topics. You open a ticket. The messages tab is there, showing the customer's support thread alongside their portal replies. You open a task. Messages again. You open a project. Messages. Six entity types, one tab, zero context switching. It doesn't matter whether the customer emailed, messaged through the portal, or replied to an old thread. The conversation follows the work. You never have to remember which inbox handled which conversation, because every message is already where you need it.

What's inside

  • See every conversation inside contacts, leads, deals, tickets, tasks, and projects
  • Portal messages and email threads in the same timeline, on the same page
  • Turn any message into a task: the body becomes the description, the topic auto-links
  • No more switching between your inbox, your CRM, and your helpdesk to piece together a story

Read Receipts and Delivery Tracking: Know it landed

You send a follow-up to a warm lead. A single gray checkmark appears: sent. A minute later, it becomes two gray checkmarks: delivered to their server. Tuesday at 9:14am, the checkmarks turn blue: they opened it. Hover over the indicator and you see who read it and when. For team emails, you see every reader listed individually. Bounced addresses get flagged in the composer before you send: a red warning chip next to the recipient warns you that their mailbox rejected your last message. You remove them, swap in their colleague, and send clean.

What's inside

  • Three receipt states: sent (single gray), delivered (double gray), read (double blue)
  • Per-reader details: hover to see who read it and when
  • Bounce status warnings in the composer: blocked recipients flagged before send
  • Failed message indicator with retry button for delivery errors

Your Daily Views: Conversations, right next to everything else you do today

Conversations don't live in a silo. A client replies to a deal thread, and you need to follow up today. A support ticket escalates, and it can't wait until tomorrow. But your inbox only shows email. Mosic's Today view pulls your pending conversations alongside your tasks, deals, and tickets, sorted by urgency. Unread conversations with SLA deadlines float to the top. The Inbox view catches conversations with no follow-up date, the ones that got read but never replied to. Overdue surfaces conversations that slipped past their deadline. Upcoming shows what's coming this week. Each item is color-coded: amber for conversations, blue for tasks, violet for deals, orange for tickets. One list, every module.

What's inside

  • Four views: Today, Inbox, Overdue, Upcoming, each pulling conversations, tasks, deals, and tickets
  • Urgency sorting: unresolved conversations first, then overdue, then everything else
  • Color-coded cards: amber conversations, blue tasks, violet deals, orange tickets
  • Filter by type or see everything mixed together, no app switching

See it in action

Real scenarios teams run every day in Mosic.

The handoff that didn't drop the ball

A SaaS company runs sales and support through two shared inboxes. Before Mosic, a support agent would flag a billing issue, email the account manager, and wait. The account manager would check the CRM, find the deal, and reply. The customer got two uncoordinated responses a day apart. After Mosic, they connect both inboxes as channels in one workspace.

  1. 1Support agent replies to the billing ticket in Mosic, the conversation is linked to the customer's contact and the open deal
  2. 2She reassigns the conversation to the account manager right from the conversation header
  3. 3The account manager opens the deal page, sees the messages tab with the full thread, no switching apps
  4. 4He replies inline from the deal page, his signature and channel are pre-selected, the topic is already linked
  5. 5The customer gets one coherent response in under an hour, and the conversation auto-resolves after 48 hours of silence
The support manager sees the reassignment in real-time. The account manager saw the full context without opening a separate inbox. The customer never knew two teams were involved, because one person handled it, one thread, one response. Average response time dropped from 6 hours to 45 minutes.

Friday drafts, Monday impact

A sales team of four manages 30 active deals. Every Friday at 4pm, they block 30 minutes to draft follow-ups for the next week. Before Mosic, they'd draft in Gmail, save as drafts, and hope they remembered to send Monday morning. Half the time they forgot. After Mosic, they draft in the UnifiedComposer and schedule each one.

  1. 1Friday 4pm: each rep opens their deals, clicks the messages tab, and drafts the follow-up
  2. 2They insert the pricing template, fill in the variables (customer name, deal amount, next step), and personalize the opening line
  3. 3Each follow-up is scheduled: warm leads get "Next Monday 9am," busy executives get "Next Tuesday 10am" to avoid Monday morning spam
  4. 4The rep hits full-screen focus mode for the tricky ones, the rest of the screen disappears, they write without distraction
  5. 5Monday at 9am, all follow-ups send automatically, read receipts start tracking opens by 9:30
The sales manager sees 30 follow-ups queued on Friday, 30 sent by Monday noon, and 14 opens by Tuesday. No one worked the weekend. No follow-up was forgotten. The team's reply consistency went from 60% to 100% because the drafts became scheduled sends instead of hope.

One thread, three conversations, zero confusion

A consulting firm manages 12 client accounts. One client emails their account manager about a project scope change, emails support about a bug in the portal, and replies to an old thread about last quarter's invoice. Three separate conversations, three channels, three topics, one client relationship. Before Mosic, the team had to manually cross-reference three inboxes to piece together what was happening.

  1. 1The account manager sees all three conversations on the client's contact page, linked under one topic: "Q3 Scope Change"
  2. 2She opens the topic view and reads all three threads chronologically: the scope email, the bug report, the invoice reply, one timeline
  3. 3She creates a task from the bug report message: the message body becomes the task description, the topic auto-links to the task
  4. 4She replies to the scope email from the topic view, not the inbox, with full context visible
  5. 5Her manager opens the project and sees the linked topic with all three conversations in the messages tab
Three conversations that used to live in three separate inboxes, now visible under one topic on the contact page, the deal, and the project. The manager sees the full picture without asking anyone for context. The client got one coordinated response instead of three disconnected ones. The bug became a task in 10 seconds without copy-paste.

Every conversation has a home. Give yours one.

Connect your channels, link every message to the work behind it, and start making decisions with full context. Free to start.

Get started freeSee all features
No credit card required
Cancel anytime
Free plan available