In Adobe Campaign Classic we have the ability to store a 'prefered sending time' of a customer (read: recipient).
We have (external) logic to calculate that prefered sending time, which will differ per recipient.
Expected behaviour is that the recipient will receive the delivery on the prefered sending time. If the prefered sending time is already passed (eg; prefered = 7AM, but workflow started a 9AM) then the business expectation is that the email is send out directly.
Question: how can I take the 'prefered sending time' into consideration when I want to send out the same delivery to all my recipients?
I've read that there is an integration with Sensei, but that (I think) it's mainly handling the calculation of the value (which is already done). I'm more interested in actually using that value in my campaigns. Maybe we can re-use ACC-Sensei logic here? Does anyone know how send time optimization is handled in that case?
Scheduler that runs every hour or whatever recipients are bucketed into
Query that selects all recipients with time preference below next bucket start, for hourly this would be '@timePreferred before Hour(AddHours(GetDate(), 1) and delivery log does not exist where this delivery was attempted to recipient this cycle'. Safe and allows for 'catch up' as there isn't a lower bound
Continuous delivery. If this is a workflow that runs on a recurring basis and should have a different delivery per cycle it gets slightly more complicated