Log in to your Simplero account to give feedback

Feature Requests

Email address propagation across Contacts record and Contacts profile
Currently, when a contact updates their email address via their Profile, it only updates the Simplero ID email, not the email associated with their Contacts record or any Participant email addresses. This is not intuitive at all - if a customer is updating their email address in their Profile they would expect this to change their login info AND the email address used for all purchase communications, subscriptions etc. We’d like to request that email address changes - whether made by a customer via their Contacts profile or by an Admin in the backend (Contacts record) - automatically propagate across the system. This includes automatic updates to the Contacts record email address, the Contacts profile email / Simplero ID email, Participant email address for every purchase, and any subscriptions. This would save the tedious work of manually updating each individual purchase email (per steps outlined in Ticket #717553... Summer, Izabella, and Catalina were very helpful in helping us understand how this all works - thanks!). We've found that people often change their email address, switching between work and personal accounts. Maintaining a single master email address throughout the platform would reduce confusion and ensure more reliable contact management. Another useful feature would be to store the previous email address(es) somewhere in the Contacts record, for Admin reference purposes. Please note: We're not suggesting the same propagation for a contact's name. We appreciate that changes to the Contacts profile name do NOT sync back to the Contacts record (and vice versa). This allows a contact to use a pseudonym in their Profile (for privacy / nickname preference etc) while we retain their full/legal name in the Contacts record. As Admins, we prefer to maintain control over our student records. It would be helpful, however, if a change to the Contacts record name propagated to each product/Participant name. Thank you so much for your consideration! We're enjoying the platform and learning about all of its intricacies and powerful capabilities.
1
Add purchase failed trigger or better yet add an automated payment failed email option
Right now I get an automated email when the first payment fails as a courtesy copy with the default Whoops looks like your payment didn't go through email which is fine and what one would expect. But after that we have to setup triggers for failed payment emails. The big issue is that we setup the amount of reattempts to recharge and timing before you stop trying and mark a purchase as failed. Like all dunning processes it is great to know payment failed and the dunning had begun based on my settings, but the MORE IMPORTANT item that really needs action potentially weeks later is the ultimate "purchase failed," we are no longer taking payments or attempting to take payments status. And that is totally lost in your system! There is no trigger or notification at all that this has stopped. We have to magically discover or keep tabs manually to know when that last attempt was taken to know that a product purchase is marked failed and that we will not be getting paid, need to remove some external access perhaps etc etc. This seems like a hug oversight that the culminating end event of failed purchase happens in the veiled backend ether of no notification. I stumbled upon a failed purchase by accident and had no idea the dunning had stopped. That should not be the case. Related to this which was marked as good idea but not implemented: https://simplero.canny.io/feature-requests/p/show-failed-payment-to-contacts-on-their-simplero-account And this for emails: https://simplero.canny.io/feature-requests/p/notification-to-myself-when-payment-from-customer-fails This is money lost for everyone so needs some TLC.
2
Load More