Introduce Emails Activities

[Bonapara]

Email is received

New email received

New reply received

Email is sent

Reply sent

New email sent

Email preview

Clicking the Chevron down icon button expands the email content

Full sharing

Subject and metadata are shared

Metadata only are shared

Figma

https://www.figma.com/file/xt8O9mFeLl46C5InWwoMrN/Twenty?type=design&node-id=17557-99083&mode=design&t=b1PFpV7KkNPNAh81-11

[Eyesonly88]

Hello @Bonapara, first of all, Merry Christmas and Happy Holidays 🤩. Second, I'm not sure this is the correct place to ask, but will Twenty have the ability to send emails to contacts? or is it just syncing to other email providers?

For example, if I add in all my contacts, will I be able to use something like Resend as an SMTP to send emails using Twenty? If so, will it also have scheduling or conditions? For example, for all my contacts who didn't open the first email, send a second follow-up email, or a drip email sequence type of condition, etc...?

If the above is possible, then I see Twenty as a really good alternative for automated marketing features that Intercom and other CRM software provide.

[FelixMalfait]

@Eyesonly88 Merry Christmas to you too! That's 100% on the roadmap but we're not there yet, we're going there step-by-step: First step is to import emails from gmail automatically, that should be live in January. Second step is the ability to reply to emails through the gmail API, that should be live in February. And third step is to move from the "1-to-1 sales email" use-case to a more "marketing / mass email sender" use-case (with providers like Resend or any generic smtp). That's going to take a few more months to do it well probably.

[cocobeach]

IMO I think we could do 2 birds with 1 stone, if we implement the call straight into an Openai custom Assistant's actions API scheme, so everyone can set it up and customise how it wants.` Including adding some knowledge based gathered from sent emails (but I would leave that feature manual and individual as it needs to be done only once to "teach" the AI to answer the right things on the basis of similar past answers. Otherwise we only follow what other CRM do and don't differentiate ourselves, like that we solve the problem of sending and receiving emails, and we get it done automatically or semi automatically?

[FelixMalfait]

@cocobeach 100% agree AI assistants will be super cool to implement, along with embeddings of emails, in the context of "Automations" which is a workstream we will tackle later this year. But mail is really foundational for CRM so it makes sense to have proper gmail/office/smtp integrations first. AI is only as powerful as the integration you give it - we need to get that structure right first!

[cocobeach]

Agreed, in fact I can tell you from experience , having worked with and for Salesforce for the last 18 years, the best implementations are the ones you never need to open.

For a CRM data entry is the pain, sales people are lazy - takes one to know one - and the more you data-entry automatically the more the CRM will be up to date and useful. Automation needs to accomplish jobs not creating alerts that stagnate in the system. Now with the AI you can do high quality data entry, oops scoring, forecasting, reporting etc...

Having smtp is great but having it intercepted and entered in the CRM by the AI is the biggest differentiator you can think of.

It's because for some reason my API is not recognised - prolly because I am on local host.

But you can extract the schema of the CRM and use it inside the actions of the assistant in json or yaml, then in system prompt you put the various actions for the AI to recognise and use. (Next step is to fine-tune the AI on the actions themselves).

My 2 cents...

Ps if you use OvidijusParsiunas/deep-chat you can probably include it in the interface very easily and offer an array of AI solutions from local to OpenAI Assistants out of the box, with everything else in the middle.

;)