Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: #1935

Closed
chrisdutra opened this issue Jul 1, 2016 · 6 comments
Closed

Feature request: #1935

chrisdutra opened this issue Jul 1, 2016 · 6 comments

Comments

@chrisdutra
Copy link

Description

It would be great be able to connect one "Send Email" action to another "Send Email" action in a campaign without need to add a decision.

Today, I need to think about all emails before create a campaign if I don't wanna work with "decisions" because I just can connect "send emails" with the "conditions" or "decisions". But sometimes I just need to schedule the send of emails in a sequence based on the moment of optin in.

The point is that a campaign can be changed along the time. New emails can be add but the contacts that are already started the campaign will not receive the new information if I don't create an action, which demand a big tree that repeat actions..

Steps to reproduce

@npracht
Copy link
Member

npracht commented Jul 1, 2016

Hi,

You can also construct it in parallel with 2 email actions starting from your segment with adidas rent waiting condition.

No need for a decision or condition here.

N.

Le 1 juil. 2016 à 06:58, chrisdutra notifications@github.com a écrit :

Description

It would be great be able to connect one "Send Email" action to another "Send Email" action in a campaign without need to add a decision.

Today, I need to think about all emails before create a campaign if I don't wanna work with "decisions" because I just can connect "send emails" with the "conditions" or "decisions". But sometimes I just need to schedule the send of emails in a sequence based on the moment of optin in.

The point is that a campaign can be changed along the time. New emails can be add but the contacts that are already started the campaign will not receive the new information if I don't create an action, which demand a big tree that repeat actions..

Steps to reproduce


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@chrisdutra
Copy link
Author

Sounds great, but I don't know if I understand what you mean. Can you be
more specific?

Your sugestion is for me to do something like this:

[image: Imagem inline 1]

Christiane Dutra
(31) 3667.0995

2016-07-01 3:06 GMT-03:00 Norman Pracht notifications@github.com:

Hi,

You can also construct it in parallel with 2 email actions starting from
your segment with adidas rent waiting condition.

No need for a decision or condition here.

N.

Le 1 juil. 2016 à 06:58, chrisdutra notifications@github.com a écrit :

Description

It would be great be able to connect one "Send Email" action to another
"Send Email" action in a campaign without need to add a decision.

Today, I need to think about all emails before create a campaign if I
don't wanna work with "decisions" because I just can connect "send emails"
with the "conditions" or "decisions". But sometimes I just need to schedule
the send of emails in a sequence based on the moment of optin in.

The point is that a campaign can be changed along the time. New emails
can be add but the contacts that are already started the campaign will not
receive the new information if I don't create an action, which demand a big
tree that repeat actions..

Steps to reproduce


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1935 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AF_OPtv8yBazJLg9OK7W_fg3d5TyWUV4ks5qRK5vgaJpZM4JC0Vi
.

@npracht
Copy link
Member

npracht commented Jul 1, 2016

capture d ecran 2016-07-01 a 11 32 51

@chrisdutra
Copy link
Author

Thanks, Npacht

But this alternative isn't good for me because if I add another email, people who already receive some emails will not receive the new ones because the trigger is central which means that all the send scheduled is done when the contact start.

If one email is connected to the other I can add new emails and people will receive the last ones even if they already received the first ones.

I'm sorry about my english. I'm brazilian.

@escopecz
Copy link
Sponsor Member

escopecz commented Jul 8, 2016

@npracht's answer is correct. There is no logical reason why to connect email send action in a serial chain. It wouldn't make a difference even in the example you've provided. Mautic acts when a contact triggers some action. Modifying an active campaign is not a good idea. There other issues about it so I'll close this one.

@escopecz escopecz closed this as completed Jul 8, 2016
@chrisdutra
Copy link
Author

It is a good idea because give us more liberty to build campaings.

And it is how all the big email tools work, as Active Campaign and Infusion
Soft. But ok, Mautic is not them.

Thanks.


Christiane Dutra
Brasília/DF
Em 08/07/2016 06:12, "John Linhart" notifications@github.com escreveu:

@npracht https://github.com/npracht's answer is correct. There is no
logical reason why to connect email send action in a serial chain. It
wouldn't make a difference even in the example you've provided. Mautic acts
when a contact triggers some action. Modifying an active campaign is not a
good idea. There other issues about it so I'll close this one.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#1935 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AF_OPnwyppapQLjumfCEefYHoO4WqpNfks5qThR7gaJpZM4JC0Vi
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants