Email integration for CRM use

Ideas & Features Integrations
,
21

Reply to emails should be possible via automation button in the next release (note that auto-replies will be also possible via rules)

3 Likes
22

Sick :heart_eyes:

What would be the most optimal set-up in your opinion for the following use case?

As a user:

  • I want to create emails based on email templates
  • I want to use them when I reply on e-mails (and adjust the email when needed)
  • And I want to use them when I send the first email or a new email

Iā€™m thinking of the following

  • A new database ā€˜create emailā€™
  • User can create a new entity. They put the content of the email in the rich text field. We can create templates for the rich text field.
  • User clicks on a ā€˜send emailā€™ button. Fibery will send the email and the email and it will appear as message due to the email integration. The ā€˜create emailā€™ entity will be deleted.

Then that same database can also be used when you want to reply on an email (thread).

It feels a bit clunky. But since you canā€™t create new items in the message database Iā€™m thinking of this workaround.

What do you think?

23

Also another question/feature request.

It would be great if we can use the highlight function in email messages as well! :grin: Since emails often contains valuable feedback/insights.

24

But what stops you now? You can indicate Message database as a Source in email integration and create highlights from emails

25

I am not sure I got the flow. The good solution would be connect Message to Email Template database and let user select Email Template in a button action, then react to this selection and set message text field, but this is not possible so farā€¦

26

I know it may be a while away, but this links to What is the Upgrade plan of the Comments feature?, having emails as a Thread View would be absolutely beautiful. I know thread view is only for entity comments right now, but why not extend it further to any entity types? (Or upgrade comments to proper entities :eyes:)
Thread view is beautiful for commutation for things like email, integrated chat, think integrating whatsapp api to fibery, or any other communication platform. Curious to hear your thoughts.

27

No plans so far. In fact we did not even have intention to make email better, but it appeared a low hanging fruit, so we went for some improvements. This is not in our focus for the next 2-3 months, then we will see

28

Fair enough. Good to know, thanks! Still glad email got some love :)) I will wait patiently with fingers crossed :crossed_fingers:

29

Apologies; didnā€™t knew that! Because highlights are not possible in Readwise integration, I assumed it was also not possible in message database.

Forget about the template part; thatā€™s easy to solve :slight_smile:

Letā€™s simplify my question.

What would the ideal set-up be if a user wants to send a new email via Fibery to a contact?

They canā€™t create an entity in the message database. So we need to create a separate database to send emails, right?

And if so: what would then be ideal if you want to reply on an email? I was thinking of linking that database also to the message database. So that a user has more flexibility when they want to reply on a thread (with the button solution as showed in your video, it feels not very user friendly if itā€™s a longer text reply)

30

If you sync the Outbox as well as the Inbox, you can send an email from Fibery, and on the next sync, it will appear in the Message db

31

Overall after some research and experiments I donā€™t think we will be able to have a good Email Communication with just integration and automation buttons, it seems Email communication should be a custom module built by us. Right now there are many problems:

  1. No multi-relations ready, so Message may have many links to other databases
  2. No private databases and no way to mix different emails into a single database, so if I to use your own email, like michael(at)fibery.io and another user wants to use teddy(at)fibery.io, it is not possible to mix them in a single Message database. Moreover, all databases are public and your emails will be visible to all admins (at least).
  3. Email formatting in our rich text is far from good
  4. Templates are not there (and even signatures are not there)
  5. All UI is quite cumbersome and very hard to setup. Most likely Email communication demands custom UI.
2 Likes
32

I know :slight_smile: But the big benefit would be that my clients simply open a contact in the CRM, click ā€˜create emailā€™, select a template (we already have solutions for that), adjust the template and send the email. All via Fibery.

(and we could also automate the emails that needs to be send when their clients buy a product; we already made a test set-up back in the days for that, it was quite simple)

I agree. Some of them are not a problem for our clients (entrepreneurs that mostly work with freelancers or a small team), but others are.

For Fiberyā€™s ideal customer there isnā€™t a good solution yet.

Would be pretty sick if we have one in the future since email is a pain in the but for a lot of companies. But since all of them already have a solution for email, I donā€™t know what the priority should be.

33

Is it possible to quote original message and use signature somehow automatically?