Transactional emails are "triggered" by a user's interaction with the web or phone app and are not scheduled. The interaction itself initiates the email's delivery. In Punchh, this will typically be a notification template that informs the user of the details and nature of that transaction.
For example, if a user signs up for a rewards program and is gifted a reward for sign up that expires in 12 days, they may receive an "expiring reward" notification (and corresponding transactional email) on day 12 letting them know the reward is expiring. This fires from a pre-configured schedule in Punchh and the email delivery does not have to be scheduled manually per instance. Once the "expiry schedule" is configured the event of a reward expiring will trigger the notification and corresponding email.
Marketing emails are scheduled using campaigns and will not be sent until the campaign is activated and deployed in the system. There must be intention and planning around their delivery for each unique instance.
Disclaimer:
In an effort to supply information as quickly as possible, this article has been published prior to a formal technical review, and is subject to factual, grammatical, and various structural errors. Data may be incomplete, misordered, or incorrect.
This additional disclaimer will be removed upon formal review of this article. The standard Punchh Inc. KB Disclaimer still applies, and can be found at: https://support.punchh.com/hc/en-us/articles/360040100273-Punchh-Inc-Knowledge-Base-Disclaimer
If further assistance is required, submit a ticket to Punchh Support. (For help submitting a ticket, click here)