Sourcing and Validation
Buyer Lists
The DMO will seed potential Buyers from two sources: (1) the ServiceNow Buyer create form and (2) the list of previous Buyers migrated from uTour.
Buyer creation/modification form
Frontline teams can submit new Buyer creation/edit requests to the DMO through ServiceNow tickets. Teams are required to include buyer organization/names and address. This information provides the DMO team a starting point for sourcing buyer information.
Ambiguous Requests
The DMO will make a best effort to identify and validate Buyer information submitted through the Buyer request form. For requests where the Buyer cannot be confidently identified, it is the policy of the DMO to first reach out to the requesting party either through email or slack for more information before closing a ticket without action.
Under no case will the DMO log partial, incomplete, or unvalidated information into Auth Data related to requests with ambiguous or nebulous information.
uTour Buyer Migration spreadsheet
The DMO team will populate Buyers into Auth Data using a manually curated list of Buyers originating from uTour. Buyers on this list are validated and de-duped through a case-by-case investigation of each proposed Buyer.
Validation
The DMO will validate any new Buyer into Auth Data based on the information that lies within the official business registration information databases for the state, province, or country where the business is registered.
Examples of business registries include:
Absent the locality of the Buyer’s business registration, the DMO will use search engines and AI tools to identify in which state or country registry to find the Buyer’s official business information.
Sample AI prompts used to source Buyer data include:
- What is the legal business name of [trade name]?
- Where is [business name] registered?
- What is the business registration information for [trade name/business name]?
- Who owns [trade name]?
- What company is registered at [address]?
- What business operates under the trade name [trade name]?
Once the locality has been identified, the DMO will search within the relevant database to obtain the necessary business registration information.
Connecting with uTour
To maintain connection between UTA’s different systems, each Buyer within Auth Data must be linked to their corresponding entry in uTour. This is done by adding an ExternalRecord of type uTourId to the Buyer.
If no entry exists in uTour, the DMO will create a new Buyer profile in uTour and link it to the Auth Data instance of that buyer.
Undeterminable business information
The DMO will make a reasonable effort to accurately identify Buyers from uTour and migrate them into Auth Data. However, there are many reasons an entity in uTour will not be migrated, most commonly from lack of information that prevents the DMO from identifying the Buyer with certainty.
Individuals that cannot be validated
Individuals lacking identifiable contact information cannot be migrated into Auth Data with reasonable certainty. The key problem is the difficulty in disambiguating one person from another with the same name. In these cases, the DMO will not migrate that uTour entity into Auth Data.
Trade names or legal names that cannot be validated
Buyers using trade names that cannot be validated within a business registry will not be migrated into Auth Data.
Venues as Buyers
Within uTour, venue and buyer entity types can both be listed as Buyers within a deal. In the case where a uTour venue acts as a Buyer, the DMO will use the legal business name of the venue’s operating entity as the buying party in Auth Data. The DMO will link the Buyer to the uTour ID of the venue, even though the Auth Data instance of the venue will also link back to the same uTour ID.
Multiple buyers listed as one
Deals in uTour can be structured such that multiple Buyers are added to a deal contract. This can be done by creating a new uTour Buyer entity named as a combination of all the Buyers involved in the deal. For example, a uTour Buyer would be created for “The Complex Live & Dead Nation Presents” instead of creating separate contracts for The Complex Live and Dead Nation Presents. Multiple Buyers can also be listed as an OBO (“On Behalf Of”) entry such as “Mojo Concerts obo MESSA S.A.”.
In these cases, the DMO will not create an Auth Data party that is the combination of the buyers. If each Buyer exists individually in Auth Data, the DMO will not link the uTour entity to any of the individual Buyers. The joint uTour entity will remain unlinked to any party in Auth Data.