Conversations

Outlook to Actually Two-Way Sync in Conversations like Gmail does
I just lost an affiliate client to this feature. There are two parts to this request. Make it clear upfront in the marketing and in the dashboard that Outlook users with custom domains must set up MX records for conversations to work properly. Simply using the default Leadconnector domain only allows outgoing emails. It took us 4 weeks to learn we had to do this just to get replies to come into the conversations tab. The conversations tab needs to be able to accept inbound emails from leads. This works fine with the Gmail integration, but does not work with the Outlook integration. For my client, whose company uses Outlook, this was a dealbreaker, since for him, the CRM was the thing he needed most. We didn't discover this until yesterday (6 weeks after signing up), and that's when he asked for a refund. There was also another issue where every time he sent an outgoing email, it would be "unsuccessful". Reconnecting the Outlook account didn't resolve this. But clicking the little red arrow every time did. However, because of his laptop screen size, the sent messages were above the fold of the email composer, so he couldn't see that his emails weren't going out until he checked back later, wondering why his customers weren't receiving his emails (see screenshot). This unsyncing issue may also have impacted the ability for conversations to function appropriately. I also notice there's a 3MB limit on attachments and larger attachments would prevent syncing. We didn't get far enough for him to send attachments, but this would have been another obstacle to his success since he sends image-heavy product PDFs to his clients that are larger than that size as part of his sales process. I know everyone here is doing their best. I'd love to see this worked out since a lot of folks in my audience use Outlook, and I wouldn't feel comfortable selling this to them until it's sorted out. I hope this is helpful!
23
·
Enhancement
·
planned
DND for Channels filter - Title/label suggestion: DND All Channels (Outbound Only)
1) Title/label suggestion:Rename DND All Channel to "DND All Channels (Outbound Only)" Clear explanation: DND All Channels currently only blocks outbound messages across all channels (email, SMS, etc.) from your account. It does not block inbound messages from contacts reaching you. To prevent confusion, the filter need to be clearly labeled as outbound-only and includes a brief reminder when activated: outbound messaging is blocked, while inbound messages are unaffected. If your goal is to stop inbound communication as well, additional controls are required. This labeling helps reduce misinterpretation and support inquiries, such as a client activating the filter and later discovering that an inbound message was still delivered. 2) UI/UX microcopy recommendations Relabel the filter to : DND All Channels (Outbound Only) Add a help/tooltip (hover or info icon): This filter applies to outbound messages only. Inbound messages are not blocked. When the user enables the filter: Add Confirmation toast or panel text: “DND All Channels (Outbound Only) is enabled. Outbound messages across all channels will be blocked. Inbound messages will still be delivered.” On initial selection (to reduce misinterpretation): Add short reminder near the toggle “Outbound only. Inbound messages are not affected.” Optional inline hint on related screens: “Note: This setting blocks outbound outreach only. If you need to pause inbound messages, use additional controls.” 3) Real-world scenario: A client turned on DND All Channels thinking it would block all communication. Later, they discovered that inbound messages from a contact were still received. The confusion stemmed from the outbound-only scope not clearly stated at the user level. Clear labeling and a reminder at activation prevent this scenario. See attachment
0
·
Enhancement
Load More