Still does not preserve the history of user-selected e-mail exchanges with customers #17581
Replies: 1 comment 1 reply
-
|
That's because Twenty treats the mail account as source of truth so if in mail account email is deleted, then upon synchronization it deletes too (messaging-message-list-fetch-service.ts for reference) so that's expected, when it comes to archived messages, it needs research how they're actually stored, if they have additional tags, etc., if archived messages in mail account are actually deleted in Twenty, then it's a bug, about synchronizing approach, there's not much to do(1) since there's no other way to retrieve messages (one way to decrease network overload is to change cron of importing job which is debatable as the point is to gather data ASAP) (1) Technically, Microsoft can be imported with webhooks (https://learn.microsoft.com/en-us/graph/change-notifications-delivery-webhooks) but it needs more research, Google has something called Cloud Pub/Sub but it would require a setup by technical user which may cause additional unnecessary problems, regarding IMAP/SMTP that's not possible at all for obvious reasons CC: @neo773 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
As you have introduced authentication to Microsoft accounts, I was happy to finally test how you have implemented e-mail communication history.
I think I have observed the following: Outgoing e-mail gets "synchronized", i.e. an e-mail record is automatically created under the correct contact.
Now, imagine that the sent e-mail gets removed from the remote e-mail account. Typically, this happens if incoming and outgoing e-mails are archived. When this happens, the e-mail record in Twenty gets deleted! I haven't found a setting to prevent this.
Regardless, "synchronizing" e-mails between Twenty and a remote e-mail server is conceptually very flawed. Not only does such an approach generate a huge networking overhead but also defeat partially the purpose of the CRM to be a repository, which securely preserves the entire history of important interactions with a contact, regardless what happens to the original information source.
Not all e-mails are worthy of preservation. For example, synchronizing autoresponses, spam, tangential messages, ... is nonsensical.
Beta Was this translation helpful? Give feedback.
All reactions