Wishlist: Action Trigger for new user creation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
We would like the ability to send a welcome email to new customers as soon as their new accounts are created, or within a few minutes..
This has two benefits. One is that it validates the email address immediately, if there are any errors that would cause a bounce, those will get taken care of immediately. There is even a chance that the library staff will see the bounce before the customer leaves the building and can ask them to fix the email address.
Second is just a good marketing opportunity. A chance to follow up with the customer and again let them know of all the services that the library offers. Letting users know of all the services that a library provides is a challenge, so this is just one more opportunity. It would be a good chance to point the customer to all of the Library policy documents.
Another possible use could be to generate postal notices to confirm customers mailing information, or to send out welcome packets with more marketing material. I've heard of libraries that allow customers to sign up online and then mail the customer their library card, which this could also be used for.
There was a discussion on the irc channel about this idea at: http://
One possible way to achieve this might be to add an A/T reactor tied to new rows being created in actor.usr.
Maybe there are other ways to go about it also. Based on customer created date? I'll try to become more familiar with how the reactors are defined.
I think there should be some sort of filtering possible based on user attributes like permission level, stat categories, etc. So you can choose to not email certain groups of users. Maybe that can be done in the templates?
Changed in evergreen: | |
importance: | Undecided → Wishlist |
tags: | added: feature request wishlist |
Changed in evergreen: | |
assignee: | nobody → Josh Stompro (u-launchpad-stompro-org) |
tags: | removed: feature pullrequest request |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
This was really easy to setup based off of the usr.create-date value, pretty much a clone of the 30 day pre overdue notice. I don't know if this is the most efficient route to go, if we are doing a sequential scan of actor.usr every 5 minutes looking for new accounts. If that gets to be a problem we can probably add an index. If someone was running this once a day it probably isn't a big deal.
I'm working on a branch with changes needed to add this notice to a new install and upgrades.
Josh