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

More customised scheduling #183

Open
andyjeffries opened this issue Sep 16, 2022 · 2 comments
Open

More customised scheduling #183

andyjeffries opened this issue Sep 16, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@andyjeffries
Copy link

Hey, given all of our customers are in the same timezone and we know the best times to message people for an optimal response rate, is it possible to have all campaign messages delivered within specific windows (or at least queued within those windows).

For example, we're happy emails being queued/sent from 9am-10am Tuesday to Thursday, but sending one of our customers/prospects an email at 10pm on a Friday will be either ignored or worst case cause them to potentially unsubscribe.

Wondered if this use-case had been considered.

@joshuap
Copy link
Member

joshuap commented Sep 20, 2022

Hey @andyjeffries, I had not considered this use case, but think it would be nice to have. I'm not sure of the right abstraction, since Heya is not aware of localized settings like timezone currently. Do you have any ideas of what the config would look like?

@andyjeffries
Copy link
Author

I don't know what triggers the job, but I would say some kind of schedule defined in the config for that process.

To be honest, I've gone with a hand-crafted solution (it was a one day thing for me to build all the campaign-based functionality), but I still think it would be useful for others.

@joshuap joshuap added the enhancement New feature or request label Sep 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants