Remove need to enter email address multiple times to redeem coupon

[LeonardM53]

I ran into this issue with dealing with coupons. I created a coupon as part of my welcome email for new sign-ups. So whether they signed up using "join my list" or text-to-join, they had to input their email to complete the registration. Now, when they go to redeem the coupon, they also have to input their email again because of how the coupon is designed to redeem it. There's no way around this at this point. An email "input" is apart of the coupon itself. 

This is an unnecessary second step for those signing up. I would like for you all to change the coupon where it's optional to have the email "input" in or out. It shouldn't be required because the whole reason why contacts are receiving a coupon offer in the first place is because we already have their email info. This would help it be more seem-less for the customer if you could correct this. Thanks

[Candace_M]

Hello @LeonardM53,

Thank you for the feedback on our coupon feature! You are required to enter your email address so customers can claim the coupon and so it is trackable in our system. This also helps in the case that a contact shares the coupon with another individual and you want to determine who this was. I understand that you feel as though this second step is unnecessary and I am sorry about that. 

How do you track who uses the coupon? If you don't need the ability to track your coupon in Constant Contact you do have the option to use a coupon block which wouldn't require an email address. This allows customers to simply have a coupon they can print or show.

[Frankie_P]

Hello. With the changes being made to our Feedback flow, we are changing this status to Not Currently Planned. At this time, we do not have plans to include this type of functionality due to the low number of tracks from other customers and the prioritization of other ideas. If we hear anything in the future regarding this feature request, we will update the thread. If we hear anything in the future regarding this feature request, we will update the thread.