CRM MVP
Email can be sent and received inside the CRM, and the sync runs both ways, so mail sent from the normal mail client also appears against the record.
Correspondence is most of the relationship. If it only reaches the CRM when someone remembers to put it there, the record is incomplete in a way nobody can see, and the person covering an absence has no idea what was actually said.
One-way sync and BCC addresses both work until the day they are forgotten, which is every day.
Mail must be sendable from inside the CRM, from any object, and mail sent or received in the user's own client must reach the record through a connected mailbox.
Yes where the connection runs in both directions.
Partial where a mailbox connection exists but carries mail in one direction only.
Fails if there is no mailbox connection at all. A BCC address, a forwarding address or a drop box is a person doing by hand what a sync does, and an add-in installed into the mail client sits outside the CRM. Neither is a sync, and neither rescues a platform that has no connection of its own.
Provider coverage is recorded but does not cap the verdict. A platform that syncs both ways against one mainstream provider passes, and the narrower coverage is stated in the evidence.
Email is composed and sent to a contact from inside Act! through the Write menu, and email merges are sent from Act! to a group of contacts with the correspondence recorded to history. In the other direction, the Google integration is configured to automatically capture both sent and received Gmail messages as history records against the matching contact, and the Act! sidebar for Outlook automatically records email history from Outlook. Act! records mail as history against the contact rather than presenting a mailbox inside the CRM.
https://www.act.com/training-videos/act-premium-desktop/creating-emails-and-letters/
https://www.act.com/training-videos/act-premium-cloud/recording-gmail-history/
https://www.act.com/training-videos/act-premium-cloud/using-outlook-integration/
https://www.act.com/training-videos/act-premium-cloud/creating-an-email-merge/
A user connects a Gmail, IMAP or Microsoft Exchange mailbox to the CRM, and messages to and from contacts then sync into the contact and deal records, appearing in the activity stream and an Emails tab. One-to-one mail is composed and sent from inside a deal, contact or account record; when a mailbox is connected the message goes out through that mail server and lands in its Sent folder. The troubleshooting guidance confirms that both sent and received mail from the connected client is shown, subject to documented conditions such as the contact having an open deal, the address matching, and trashed mail being excluded. The connection is per user, so one user's synced mail is not visible to another.
A user authenticates a mailbox in preferences by IMAP, giving user name, password, host and port, after which incoming mail from a customer, contact or lead is associated automatically with the matching record, and mail can also be sent from within Apptivo through the authenticated address using email templates, including in bulk. Every record shows an Emails section holding incoming and outgoing email associated to that object. The constraint is on the return path: the documented Office 365 route is a forwarding address configured in Outlook, which captures mail into Apptivo rather than synchronising a mailbox, and no vendor document states that a message sent from the user's own mail client is written back onto the CRM record or that a message sent from Apptivo lands in the mailbox sent folder.
https://answers.apptivo.com/questions/11886/how-do-i-setup-email-in-preferences-settings
https://www.apptivo.com/user-manual/user-interface-navigation-global-features/
https://answers.apptivo.com/questions/13152/how-can-i-synchronize-office-365-email-with-apptivo
https://answers.apptivo.com/questions/11319/how-do-i-set-up-custom-email-templates-in-customers-app
Email sync connects a Gmail or Microsoft 365 mailbox and imports past and future mail. Sent items are within scope - for Google accounts all non-deleted mail is synced, and for Microsoft 365 the Inbox and Sent folders are synced - so mail sent from the user's own client appears in Attio. Users compose, reply, reply all and forward from inside Attio, and Attio states it is not an email service provider and sends everything through the synced Gmail or Microsoft account. Synced mail surfaces on the Emails tab of person and company records; the vendor changelog records emails being extended to deals and custom objects during 2026. Forwarding is offered separately for mailboxes on unsupported providers.
A user connects a personal mailbox to Bigin over IMAP, with Gmail, Microsoft 365, Outlook Mail, Zoho Mail and other IMAP services named and direct sign-in offered for the major providers. Email is composed and sent from records in the Contacts and Pipelines modules, but not from Companies. Once a mailbox is configured, the Emails tab on a record shows sent and incoming email interactions, and messages can be replied to and forwarded from there. What the vendor does not state anywhere is that mail sent from the user's own email client outside Bigin is pulled back onto the record, so the return path is documented for incoming mail only. A separate mechanism forwards incoming mail to a Bigin email alias, which is a capture address rather than a mailbox sync. An admin setting governs whether a user's email is private, public or the user's choice.
https://help.zoho.com/portal/en/kb/bigin/channels/email/articles/em
https://help.zoho.com/portal/en/kb/bigin/channels/email/articles/sending-email-from-bigin
https://help.zoho.com/portal/en/kb/bigin/faqs/emails/articles/how-to-configure-imap-in-bigin
https://help.zoho.com/portal/en/kb/bigin/channels/email/articles/email-sharing
A mailbox is connected through Google Workspace authorisation, a Gmail application password, a Microsoft 365 or Outlook account, or IMAP and SMTP. Once connected, mail sent and received in the external mailbox syncs automatically onto the matching contact, and the vendor states that activity from integrations such as Gmail is synced and includes emails, messages and interactions related to leads. Mail is composed and sent from inside the CRM, both from the unified inbox and from the lead view alongside LinkedIn, WhatsApp and Telegram. Ingestion is broad enough that the vendor supplies an email filtering rule set to exclude unwanted mail by subject, sender name, sender address or body content.
A user connects a Google Workspace, Gmail, Microsoft 365 or Outlook mailbox and then composes and sends mail from a Send email button inside Capsule, on contact, opportunity and project records, with the sent copy landing in the provider's own sent folder. The return path is not a mailbox sync: inbound and externally sent mail reaches Capsule either by forwarding or BCC to the account's Mail Drop Box address, or through the Gmail add-on or Outlook add-in, which can be set to auto-store all mail to and from a chosen contact once switched on for that contact. Auto-store attaches only to contact records, not to opportunities or projects, and only catches mail where the contact is in the To or From field. There is no unified inbox inside Capsule and no documented account-wide automatic capture, so the two-way flow is present but constrained.
A Gmail or Google Workspace mailbox, a Microsoft Office 365 mailbox or a custom IMAP and SMTP mailbox can be connected, and the vendor describes it as two-way email integration. Mail is sent from inside Close and replies are logged automatically; mail sent from the external client or a phone is picked up from the Sent folder and logged to the lead's activity feed, and mail sent from Close appears in the connected mailbox's Sent folder. Vendor documentation states explicitly that there is no need to BCC Close when sending from an external client, so a dropbox address is not the mechanism.
With a connected Google account, mail sent and received in Gmail syncs automatically onto the matching Copper records, and the Send and Reply from Copper setting lets users compose and reply from inside Copper with delivery through their Gmail address, so the flow runs both ways. The capability is constrained to Google mailboxes: vendor documentation names no Microsoft 365 or Outlook mailbox connection, and directs users of other clients to a BCC address instead. Mail between users on the account's own domain is excluded from sync.
https://support.copper.com/en/articles/8823339-email-settings
https://support.copper.com/en/articles/8823283-working-with-the-gmail-integration
https://support.copper.com/en/articles/8823340-send-and-reply-from-copper-setting
https://support.copper.com/en/articles/8823268-how-emails-and-logged-activities-sync-between-records
Email can be sent from inside folk - from a contact record, from a deal, or to a selection of records in a group - once a sender is configured, and messages sent from folk are logged automatically as interactions. Mail sent and received in the user's own client also reaches folk: connecting a Google Workspace or Outlook account imports emails and attaches them to the matching contact profiles in real time. The gap is on the reply side. folk states that replies from recipients land in the user's external mailbox, not in a folk inbox, and that the folk messaging inbox tracks outbound messages by status rather than holding inbound correspondence. folk also states plainly that actions performed in folk are visible only in folk and that there is no back synchronisation to the connected source. Certain classes of mail are excluded from import, including unread messages, messages older than three years, messages with twenty or more recipients and mailing list traffic.
Connecting a mailbox offers a two-way sync option, described by the vendor as the default, which synchronises both incoming and outgoing mail between the mailbox and the CRM. Mail sent from the native client is matched against the contact database and appears in the CRM, and mail sent from the CRM is written back to the mailbox. Gmail, Microsoft 365 and generic IMAP/SMTP providers are supported.
A connected personal inbox lets users send one to one email from CRM records and logs replies back onto those records. Mail composed in Gmail or Outlook is logged into the CRM by HubSpot's own Chrome extension or Outlook and Office 365 add-ins, and a super admin can switch on logging by default for all users. Constraint worth noting: an incoming message that is not a reply to a thread already logged does not log automatically and needs manual logging.
Email Inbox Sync connects a Gmail, Office 365 or Outlook mailbox and captures inbound and outbound mail automatically, matching it to contact and lead records and threading replies. Mail sent from Insightly lands in the native client's sent folder, and mail sent or received in the native client syncs back into the CRM without forwarding or a BCC address.
A one to one email can be composed and sent from inside Keap using the email icon on the contact record, sending from the address on the selected user record. Email sync connects a Gmail or Microsoft mailbox so that incoming and outgoing mail exchanged with Keap contacts is written back to the contact record, which covers mail sent from the native client. The vendor states plainly that mail sent from Keap is not synced to the external mailbox, and that attachments are not synced, so the loop is not closed in both directions.
Server-side synchronisation connects user mailboxes to the application and, with Exchange or Exchange Online, synchronises email in both directions without any Outlook add-in, so a seller can send from an opportunity or contact record and mail sent or received in Outlook is tracked back onto the record timeline. Incoming mail is polled on a five-minute cycle and outgoing mail queued as Pending Send is picked up on the same cycle. Gmail and Yahoo mailboxes are supported for email over POP3/SMTP or IMAP/SMTP.
Emails & Activities connects a Gmail or Outlook mailbox by OAuth with read and write permission and provides a composer on the CRM item, and every thread sent from that composer is logged to the item timeline. Mail sent or received in the native client is also logged onto the item when the message carries both the address in the item's Email column and the connected mailbox address, and monday describes this as two-way email integration with Gmail and Outlook. A setting narrows logging to messages that BCC the connected address, but that is optional rather than the only route. Limits are documented: messages predating setup are not captured, and an address used in more than 250 Email columns stops being logged.
Connecting a mailbox by OAuth for Gmail and Microsoft 365, or by IMAP for other providers, creates what the vendor calls a bidirectional sync, pulling in the Inbox, Sent, Starred, Archive and Trash folders from the preceding ninety days and continuing forward. Mail can be composed and sent from inside Nimble, and synced messages surface in the Message tab and on the Interactions tab of the matching contact. There is no reliance on a BCC dropbox.
A Gmail or Office 365 mailbox is connected to Nutshell so that messages send and receive in both places, with mail synced from the mailbox appearing in the Nutshell inbox and on person, company and lead timelines. Mail can be composed and sent from within Nutshell from a record timeline, from list pages in bulk or from the dashboard. A BCC dropbox address exists as an alternative capture route for other providers, and deleting a message in the mailbox does not delete the copy held in Nutshell.
Email sync connects a Gmail, Microsoft Exchange, Outlook.com, Yahoo or iCloud mailbox so mail can be read, sent and replied to from the Sales Inbox and from contact and deal detail views. Mail sent from the user's own client populates the Pipedrive inbox and sent sections, and deleting an email in Pipedrive can also delete it in the connected account, so the flow runs both ways. Smart Bcc is a separate mechanism for manually pushing individual threads in from an external client.
Mail can be sent, replied to and forwarded from inside the CRM from records that show an email icon, including opportunities, with the copy saved automatically against the record and outbound mail sendable from the customer's own domain. Inbound mail arrives by two manual routes only: the Save to CRM add-ins for Outlook desktop, Outlook web and Gmail, which save individual messages against a chosen record, and a unique CRM inbox address that users copy, blind copy or forward to, optionally via a client-side forwarding rule. No connected-mailbox synchronisation is documented, so mail sent or received in the native client does not reach the CRM unless the user pushes it there.
Users send email directly from any activity-enabled record (leads, contacts, person accounts, opportunities, cases, custom objects) and the message is logged to the activity timeline of that record and related records. In the other direction, Einstein Activity Capture connects the user's Microsoft or Google mailbox and automatically captures messages sent and received there, matching them to contacts, leads, accounts and opportunities, so mail composed in the native client reaches Salesforce without a BCC address. With Sync Email as Salesforce Activity enabled, captured mail is stored as standard EmailMessage and Task records visible to standard reports and the API; without it, captured mail appears on the activity timeline as virtual activity that is not editable and not available in standard reports. A BCC dropbox (Email to Salesforce) also exists as a separate, older mechanism.
https://help.salesforce.com/s/articleView?id=sales.aac_how_it_works.htm&language=en_US&type=5
https://help.salesforce.com/s/articleView?language=en_US&id=sales.eac_email_activity.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.aac_guidelines.htm&language=en_US&type=5
https://help.salesforce.com/s/articleView?id=sales.email_my_email_2_sfdc.htm&language=en_US&type=5
Streak runs inside Gmail, so mail is composed, sent and received in the same client the CRM lives in, and an email can be attached to a box from the inbox, from the inbox view, from the compose window or from an existing thread. Automatic email sharing can be switched on per contact and per organisation so that correspondence with that person or company is added to the box without manual action, and a teammate's shared mail is pulled into the same box timeline. There is no separate mailbox to reconcile, and no BCC dropbox is required. The capability is tied to Gmail and Google Workspace accounts.
Vtiger documents two-way email synchronisation between the Vtiger inbox and a connected Gmail, Outlook or IMAP and SMTP account, so mail sent or received in either place appears in the other. Mail sent from inside Vtiger is written back into the connected account's sent folder when two-way sync is on. Mail is composed and sent from within the CRM, and emails are related to records so that the correspondence history sits against the customer.
An IMAP mailbox can be attached to a user's CRM account, after which both sent and received mail is associated with the matching lead or contact record, including mail addressed to a record's secondary email address. Mail can be composed and sent from inside the CRM, with an option to write sent messages back to the mail server. A separate Gmail API mode reads and sends through Gmail servers rather than storing copies in the CRM, so mail disappears from record pages if that connection is switched off.