I select recipients via an SQL Query. College-bound students have filled out scholarship application forms. They have to get in a number of resources, such as financial aid info, transcript, etc. These are entered via other forms. I do SQL Queries that get the students who need to be contacted to prompt them to get their information in before the deadline.
Some of them share email addresses with brothers or sisters, and Axon sends email to everyone who shares the email address whether it is the right person or not.
That's why I want to be able to return the UserID in an SQL Query, and have Axon send email to that individual only by getting info from that user's account.
This sacrifices some of the opt-in and other functions for Axon, but what we need to do here is be very exact in sending to a particular user. I know who the user is because the user is the one who is the "owner" of the form instance. Instead of returning an email address or a role, I want to hand Axon a UserID, and for Axon to get the email from the userid, and for the normal personalization tokens to still work.
We are now near the end of the current scholarship season, and again we are sending to the wrong people, as well as to the right people. My client gets inquiries from confused students. Sometimes both are submitting applications, and one has the info in, and the other doesn't; but they each get notified that they haven't yet complied.
I don't need a quick fix on this. Would have liked to have had it prior to March of this year for current season. Now, March of next year will mark the beginning of the next season.