Note: Support for Salesforce opportunities is in active development. This page may not reflect the latest features and updates.
KORE Ticketing & Fan Engagement provides a Ticket Sales Opportunity (TSO) workflow. However, Salesforce offers its own opportunity (“deal in progress”) workflow which some KORE clients would prefer to use. This page describes KORE Ticketing’s support for Salesforce opportunities and how it differs from the standard KORE Ticketing product.
Support for Salesforce opportunities must be configured during the initial deployment of KORE Ticketing. Migration of existing KORE Ticketing deployments to this version is very complex and cannot be automated. Contact our Services team to discuss potential options.
Note: Salesforce does not use person accounts by default. They must be manually enabled. Once enabled, person accounts cannot be disabled.
In Salesforce, opportunities must be associated with an account. By default, Salesforce only uses business accounts. A business account can be linked to multiple contacts. A person account is different—it combines various account and contact fields into a single record which represents an individual. Person accounts cannot have direct relationships to contacts, but they can have indirect relationships with contacts or business accounts.
The standard KORE Ticketing module with TSO maps each ticketing account (whether for an organization or an individual) to a Salesforce business account. But to support opportunities instead of TSO, KORE Ticketing maps each ticketing account to a Salesforce person account.
If KORE Ticketing can’t match a ticketing account to a Salesforce account during an incremental update, it will create a new Salesforce person account (instead of a contact). You can manually create a new person account by opening the Account tab and selecting New > Person Account > Create.
As part of its implementation, Salesforce creates a hidden contact for each person account. Each person account is permanently connected to one (and only one) hidden contact. These contacts cannot be changed directly—changes must be applied to the person account itself.
CRM integration packages
KORE Ticketing uses CRM integration packages to add new views and features. We provide a different set of specialized packages to support Salesforce opportunities.
The specialized set of integration packages is still in active development and does not support all KORE Ticketing features. However, all the data needed to support additional features is still recorded and synced.
The current supported features include:
- Fan Finder
- Configuration Records (seasons, ticket groups, etc.)
- Attendance Grid
- Purchases Grid
- Ticketing Data Manager (TDM)
In a standard KORE Ticketing installation, entities created for the TSO feature would be stored in a SQL Server database. To support Salesforce opportunities, KORE instead takes advantage of Salesforce’s customization options and uses entities managed within Salesforce. This version of the integration treats Salesforce as the “source of truth” for most entities, not the SQL Server database.
Because of this, the standard entity dictionary does not apply to this version. Salesforce is the “source of truth” for all entities except: