Key takeaways

  1. A plugin, a sync and a real mailbox are three different products.
  2. Adoption follows the window the rep already lives in. Duplicate entry always loses.
  3. The thread on a deal should be the actual thread, including replies that never CC the CRM.
  4. Qivity reads and sends from Microsoft 365, Google Workspace and IMAP/SMTP inside the CRM.

A CRM email inbox is the actual mailbox, used from inside the CRM. Read, reply, file, template. The thread on an opportunity is not a copy that arrived later via BCC. It is the thread.

That sounds obvious. It is the feature most CRM evaluations skip, and it is the strongest predictor of whether anyone will still be using the system in month nine.

Three things vendors call “email integration”

A plugin or sidebar. Works until the next Outlook update. Reps still have two windows. Logging is optional, so it does not happen on busy days.

A sync. Messages are copied in after the fact. Threads fragment. A reply that never CC’d the CRM never arrives. You get a museum of mail, not a mailbox.

The CRM is the mailbox. Qivity connects Microsoft 365, Google Workspace or plain IMAP/SMTP and lets the team work the real inbox against the record. Templates, filing, shared visibility.

If you are choosing software, this is question one in how to choose a CRM.

Why syncs fail quietly

Email is not a document store. It is a conversation with state: drafts, folders, send-later, bounce handling, who actually replied. A nightly copy cannot carry that state. The moment a customer replies only to the rep, the CRM is wrong and nobody notices until a handover.

Shared inboxes make it worse. A team mailbox that lives in Outlook rules and forwarding is invisible to forecasting. A team mailbox inside the CRM is just another inbox with permissions.

What “inside the CRM” enables

Once mail is native, other features stop being integrations:

  • Campaigns that send from the same identity the customer already replies to. See CRM with email marketing.
  • Bounce and unsubscribe handling against live CRM records, not a CSV you exported last Tuesday.
  • An activity timeline that does not depend on a human remembering to log.

WhatsApp belongs in the same timeline for the same reason — the 24-hour rule is unenforceable if the channel is a personal phone.

A thirty-second test in the demo

Ask them to reply to a real message from your mailbox, live, without leaving the CRM, and then to show you that reply in the mail client. If they switch to a plugin screenshot, you do not have a mailbox. You have a brochure.

Book a demo and bring an inbox. That is the fastest way to see whether this is real.