TOPIC: Mail Confirmation Changes

Hello,

I'm working at a company where we manage subscriptions for our clients events. We were doing custom development until recently and are now trying to develop a portal using DTHRegister. However some key features are missing.

We are used to sending different emails to the customers depending on the payment method they chose. If somebody payed via Paypal, we send an email after receiving confirmation of the payment. This email contains the ticket to be printed with the bar code generated by DTRegister. However, if the customer chose to pay via bank wire transfer (pay later option), we have to first send an email containing the details for the payment ( such as account number and a recap of the sum of money due). It's only by checking their bank records that the event's organiser can verify that the customer payed his ticket.

We could not reproduce this behaviour with DTRegister and had to hack the code to support this more or less. For the moment, when a paypal payment is confirmed, there is an automatic email to thank the customer but we can't use it to send their ticket information because this email is also automatically sent to the customer after he chose a bank wire transfer before we have the chance to check if the payment could be verified. It would be really nice if you could make so that the thanking mail of paypal and pay later methods are not the same (and I guess for the other payment method as well). If these mails were specific to each method, we could include directly our tickets with the thanking mail of the paypal method. For the pay later option (bank wire transfer), we would use the thanking mail (it's important for it to be an email so that the customer can keep a trace of the payment details) to send the payment details to the customer. We could use the existing mail for status change to send their tickets to these customers when we can confirm we received their payment.

Secondly, it would be useful to allow several discount code with the same code. It would allow to give special clients a unique code which would be translated in the system as a different deduction depending on the event the customer chose. For example, with the same code "discount_code" the customer could subscribe to "event1" en get a 30 euro reduction or he could subscribe to "event2" with the same code and get a 45 euro reduction. We tried to setup differently named codes but with the same code string "per se" but it is not allowed in the last version of DTRegister (2.7).

Lastly, we usually have to prepare guest tickets to be offered for free (it represents several hundreds of tickets). Since there are many tickets to be distributed this way, the current system of discount is not really adapted to this use. Creating manually these tickets (single use discount coupons of a 100% price reduction) can take a while and we could stil introduce them directly into the database but we would be thankful if you could include this feature in a future release.

I hope I was clear enough in my explanations. If you would like to talk about it, too clarify some part of our process or for wathever informations you could want, don't hesitate to contact me or my colleagues.

Michael Bashevkin