Ways to Block Constituent?

Hi Tess World, 

Has anyone dealt with unwanted guests who continue to buy tickets for events that have been specifically barred from doing so? Or has anyone found unique ways to bar people from registering for an event or account if they have a specific name? 

 

It's a long story, but for context--we have a rather unstable former student who has been explicitly told he is no longer allowed to take classes or attend shows here. Despite this, he continues to create new accounts (mostly in his own name or variations of it) and show up to more classes and shows. We try to monitor it as best we can, but are trying to find a way to have any account with his name flagged (or preferrably, restricted from being created) prior to when folks arrive for the event. That way we can take action before he actually shows up... 

 

Any ideas or suggestions are welcome!

 

Thanks,

Carrie

The Groundlings Theatre & School

 

  • Not out of the box, but I'm sure if you have someone with SQL experience they could create a job that runs periodically and lets you know if someone with that name, or variations of it, has created an account.

    Michele

  • As Michele says, you'd most likely need someone with SQL knowledge but I'm wondering if you could:

    • create a constituency to add to any prospective customer that's on an exclusion list.  Have a dynamic list that's regenerated on a periodic basis
    • maybe have a custom, local table that can be updated with email addresses of barred customers.  Have a routine that automatically adds this constituency to anyone that has a matching email address
    • use the Cart Validation routine to disallow anyone on the list to complete a sale.  Do you use TNEW?
    • have a custom element in the header showing a very clear icon if someone has the constituency so that they're identified if they try to book over the counter/phone

    Martin