E-Mails in SuiteCRM - your approach / experience

Hi,

I’d like to know: How do you handle emails in SuiteCRM?

Just from the UI, email sending is now looking quite up-to-date :+1: .
Receiving / reading email is still some 20 years back from the UI / UX.

Under the hood, I see MS, Google and others as mail servers.
MS is working fine overall, others still have a bug that sent mails are not stored in the sent folder (patch suggested by @tapio Fix #839 IMAP Sent append for outbound email sends by eleknader · Pull Request #2 · eleknader/SuiteCRM-Core · GitHub :star_struck: ).
These are the two setups I see in D-A-CH / EU mostly. I hardly see any Google mails here.
How about in north America @pstevens ?

But these are just technical details. How do you use email in SuiteCRM?

  • Not at all (via my standard eMail software)
  • With the Outlook Plugin
  • Only for sending individual mails
  • Sending individual + campaigns
  • Receiving / reading / importing
  • Auto-import for one / multiple group accounts
0 voters

I’ve implemented many different setups in projects.
Several even with external integration via n8n / ActivePieces since the requriements couldn’t be met using the UI just a few examples:

  • project numbers + auto assignment to these
  • multiple receivers + correct relationships
  • AI triaging + subfolder logic to import and trigger workflows

Compared to my Zoho implementations, where eMails adopt naturally into the CRM flow / daily processes, for SuiteCRM, there is still a way to go. I’ve observed the updates in the last few versions and I’m happy to see those for writing emails. I hope, we’ll see some more improvement around IMAP / reading emails and the workflow / features at large, as well as the underlying technical issues.

Curious:
What are your email / Suite setups? How do you use eMails? What are your experiences here?

I built my own interface and customized the system to fit my business workflows. The interface looks like this. I took inspiration from IceWarp.

1 Like

Email is one of the biggest complaints I get from clients (other than colors LOL). I have some on gmail and the Yahitt plugin is completely usable (at least it was, I haven’t used it in a while). For MS clients they typically use the o365 pluigin and push emails etc from Outlook to SuiteCRM. Virtually no one uses the email client in SuiteCRM. Except for outbound, if they are sending a template or something.

I think the real answer here is not to further develop the email client in SuiteCRM, it will never be as good as Gmail or Outlook, and even if it is, users live in Gmail and Outlook, not the CRM. Some even use Gmail and Outlook as a CRM with elaborate folder and color coding systems. It’s difficult to fight against that (I’ve tried!). I think the real answer is make Outlook and Gmail integration better. At least for enterprise clients I think this is the answer rather than trying to build a better mouse trap inside of SuiteCRM.

I totally agree with you. We need better integration of these email services with SuiteCRM.

It is very helpful to have a plugin that could archive emails to CRM.


This free one works well with Outlook.

SugarCRM Outlook Plugin

Does Opacus still work? Mine stopped working a while ago. Does it work with outlook online in the browser?

It still works, at least with the Outlook desktop app. I do not know if it still works with SuiteCRM 8.

I’m interested, what is it about reading email that is lacking?

I admit I haven’t been using emails with SuiteCRM, so the answer might be obvious to many people, but I would appreciate a quick explanation.

Thanks

That’s a very technical approach to a non technical issue :slight_smile:

It looks great. How about the integration? Templates, Campaigns, Attachments, importing / archiving mails, auto importing + cases, etc.?

Still, this should just be an out of the box feature or a much smoother integration into existing applications.
E-Mail, especially in B2B, is one of the standard means of communication.
That just needs to be on a different level per default. The sending / writing is close to good now with the new UI.

That’s really different for me in quite a few projects.
As mentioned, Gmail is almost never used here in business setups.
And I’ve got quite a few projects with some email requirements.

  • event invitations
  • email archiving
  • small ad hoc campaigns
  • quotations / proposals
  • process updates / transactional mails
  • mails from workflows & integrations

I’ve got a few projects with Mailcow, Thunderbird, Nextcloud - that’s tricky again, if only the two big mail clients (OL, GMail) get better support, the software group where SuiteCRM shines as well, will need to be left behind (open source / data sovereignty).

1 Like

It’s mostly UX.
When prospects first ask about emails, I usually tell them, that it technically works.
Sending / composing is definitely on another level now, compared to two versions back.

Reading - compared to Thunderbird / GMail / Outlook / Nextcloud - is just clumsy / outdated. It technically works, but the UX is closer to Win 3.11 or something than AngularJS. :wink:
It doesn’t match day to day business processes and user expectations anymore.

1 Like

I think this is code for that.

  1. SuiteCRM-Core/public/legacy/modules/Emails/templates/emailDetailView.tpl at hotfix · SuiteCRM/SuiteCRM-Core · GitHub

  2. SuiteCRM-Core/public/legacy/modules/Emails/EmailUI.php at hotfix · SuiteCRM/SuiteCRM-Core · GitHub

  3. SuiteCRM-Core/public/legacy/modules/Emails/EmailUI.css at hotfix · SuiteCRM/SuiteCRM-Core · GitHub

  4. SuiteCRM-Core/public/legacy/modules/Emails/templates/_baseEmail.tpl at hotfix · SuiteCRM/SuiteCRM-Core · GitHub


Files need to be check for email UX modernization:

public/legacy/modules/Emails/EmailUI.php
public/legacy/modules/Emails/EmailUIAjax.php

public/legacy/modules/Emails/templates/_baseEmail.tpl
public/legacy/modules/Emails/templates/emailDetailView.tpl

public/legacy/modules/Emails/css/EmailUI.css
public/legacy/modules/Emails/javascript/EmailReader.js

For the API/threading phase

public/legacy/modules/Emails/EmailApi.php
public/legacy/modules/Emails/EmailThread.php

And for CRM-context integration:

public/legacy/modules/Emails/EmailUIAjax.php
public/legacy/modules/Emails/templates/emailDetailView.tpl

That’s the thing .. of course, everything can always be developed / implemented. It even got easier now, with AI.
It still requires a budget, time, maintenance, reviews, optimizations etc. and eventually becomes a software project.

However, a software project is what SMEs looking for a CRM system for their day-to-day operations should avoid outright.

  • It doesn’t contribute to the value that they bring to the market
  • They don’t usually understand software development
  • Their benefit from doing it might be questionable

If a random B2B / growing SME is shopping for a CRM, they expect that communication with their main channels is integrated - at least the written communication (which is mostly web forms and emails).

I use Microsoft GraphMail with custom patch. I think IMAP would work as well, but for campaigns the mail is being sent as a normal email by Exchange servers in batches, and I think I get more mails trough by this way.

BR,
Tapio

Clients often have elaborate folders and subfolders setup in their email clients. They drag and drop emails into appropriate folders. This would be great to replicate in SuiteCRM, and maybe designate the folder with specific relationships like a specific account, client, or project for example and then a toggle on whether to auto import that folder. That would give the user an experience that they are accustom to in Outlook and Gmail. Maybe the would use the suitecrm client in that case.

The real decision here, is do you want primarily user to be using the SuiteCRM client for email, or outlook or gmail? If its the SuiteCRM client, then it has to be on par with Outlook and Gmail or people will just default to what they are familiar with. If the answer is allow them to use Outlook and Gmail, which most of my end users already do (I know Bastian has slightly different experience) the the focus should really be on integration and not so much building out the client in SuiteCRM.

Personally, I’d suggest keeping the client minimally functional but focus on integration with Outlook and Gmail and do things like, contact/lead email addresss availability, relating emails to contacts/accounts/projects, etc. right from Outlook and Gmail.

They are really two different paths. I think the latter is where most enterprise clients live.