It is imperative we keep our partners and customer safe from clear and present compliance and regulatory risks. It is imperative to their goals as partners and to our goals of building a business. Too often companies are attacked by splashy headlines of ticket misuse, the majority of which are caused by high-profile events often bought on the secondary market. Beyond the PR damage, which usually subsides rather quickly, there are oftentimes heavy fines which are made worse by the legal fees incurred dealing with the issue. TicketManager is built to assure our customers and partners are protected against these threats. To do so, we must, together, have “a reasonable process in place to deter fraud and non-compliance.” What does that mean? It means we need to make clear to agents of the customer what the rules and guidelines are for buying tickets. In today’s world, users can access the secondary market from anywhere. If a company blocks access in TicketManager, the user will simply go to the secondary site in another browser window. If the company blocks the access in all browsers, which is costly and very rare as there are thousands of sites, they use their phones, which is even more costly to block and impossible if the company has a BYOD (Bring-Your-Own-Device) policy in place. If the user can access these sites and isn’t made aware of rules and guidelines at the point of purchase, there is risk. The Marketplace comes with tools which demand the user acknowledge the rules and guidelines of the business. Companies can place multiple stop signs in front of the user at the point of purchase with links and information reminding and compelling them to follow the regulations in place. There are other tools we will address in later sections which encourage good behavior. Sometimes, in the face of all these data points, an administrator or power user will still want to shut off the Marketplace for personal reasons as tickets can be emotionally driving forces. If that were to happen, and the company got caught in a scandal, we would be putting the TicketManager name at risk as well as the only choices would be to denounce the customer as a poor user, something we will not do, or accept the implication our product does not work and protect our customers and partners, which we also will not do.
