True to the date of writing this issue, the tool does check for ambiguous names / nicknames before running and sending the messages. i.e. Given a list of participants with two people having the same first name / nickname, the gifter (actually 2 in most cases) would not be able to know which of those two the message is referring to (unless one got the other - but that's a special case.)

One way to solve this issue would be to run a validator of the list of names after loading the participants' details into their classes.