Requirements Re-cap:





Parents/other relations to be stored against Lead. Contacts.
Users should be able to include the related contacts in the campaigns.
Users should be able to review campaign responses and reply accordingly.
Filtering on any lead/related contact property should be available in campaigns.
Campaign support on Contact is not desired due to security concerns.
Summary of Suggested Approach:



Introduce a new shared object – IU Relation
All relations will be created as Contacts. IU relation object will connect the relation contact and
the lead.contact instance to each other.
Relationships:
1
Contact (Lead)






Many
Many
IU Relation
1
Contact
(Relation)
Enable campaign support on IU Relation object
Create IU Relation instances via import
Options for setting Teams for the IU Relation created via import
 Share the IU Relation instance will all the teams in which the contact has leads in. (More
efforts for imports while creating and updating IU Relation instances)
 Share the IU Relation instance with all the admissions teams and the alumni teams by
default. Since the access is controlled via the lead object, only teams with access to a
lead will be able to see its related contact object and hence the relationships. Even if a
user gets access to an IU Relation instance that is not related to a lead in their team,
they will not be able to open other lead instances since lead is still controlled at a team
level. (Easier, simpler imports)
Users with the right permission will be able to directly create campaigns with IU Relation as the
base object.
IU Relation will always store one side of the relationship i.e. relationship between the
lead.contact and the related contact.
Users with the right permission will be able to directly create campaigns with IU Relation as the
base object.
Pros
Security: Only users with access to the admissions
teams will have access to the relations
The lead will be a second level relationship to IU
Relation. Easy filtering on information in the
campaign workflow. For e.g. filtering on leads
with GPA > 3
The related contact will be a first level
relationship to IU Relation. Easy filtering on
information in the campaign workflow. For e.g.
filtering on parents from IN only
After campaign support is enabled on IU Relation:
- Lead wise, Relation wise tracking of outbound
communication possible through the IU
Relation object
- Lead wise, Relation wise unsubscribe option
available
Bio Demo information about the relation is
stored only on the contact object making it a
single version of truth
Cons
Some redundancy will exist. See the table
below for sample scenarios.
Manual creation of the IU Relation object
instance may be cumbersome because of
the multiple relationships that need to be
set
Responses to the mailers will be tagged
against the contact only. Incoming
interactions will not be tagged to the IU
Relation object
Sample Scenarios:
Note: Detailed scenarios with screenshots in a later section

Contact A is a prospect for IU. A is related to Contacts B (Father), C (Mother) and D (Sister).
Three IU Relation instance created will be as given below:
Primary Contact
Contact A

Secondary Contact
Contact B
Contact C
Contact D
Relationship
Father
Mother
Brother
Contact B also is a prospect for IU. For B, three more instances of IU Relation will be created as
below:
Primary Contact
Contact B
Secondary Contact
Contact A
Contact C
Contact D
Relationship
Son
Spouse
Daughter
Note: The above scenario only illustrates the way in which the information is to be stored. Actual data in
the system will be dependent on the relationship information that will be made available during
imports.
Screenshots:
IU Relation Object view
Viewing Prospect Student.Contact’s related contacts
Viewing other contacts where Prospect Student.Contact is related
IU Relation based campaign with Send Mailer step configured to send mails to IU Relation 
Related Contact  Email Address
Filters on the campaign nodes allow easy filtering on the Lead as well as the IU Relation
Contact object properties
Detailed Scenarios:
1. Prospect student with relations not having any other link to IU:
Actors:
 Prospect student (IUPUI) – Charles
 Father – Rob
 Sister – Jessica
Object instances created for above scenario:
Contact
Lead (Team)
• Charles
• Charles
• Rob
(IUPUI Admissions)
• Jessica
IU Relation
• Charles – Rob
• Charles – Jessica
View of Charles’ relations for IUPUI admissions user:
2. Prospect student with related father who is a prospect with another campus:
Actors:
 Prospect student (IUPUI) – Adam
 Father (prospect in Bloomington) – Jack
Object instances created for above scenario:
Contact
Lead (Team)
• Adam
• Charles
• Jack
(IUPUI Admissions)
• Jack
(Bloomington Admissions)
IU Relation
• Adam – Jack
• Jack – Adam
View of Adam’s relations for IUPUI admissions user:
View of Jack’s relations for Bloomington admissions user:
3. Prospect student with multiple relations (including alum and other relations):
Actors:




Prospect student (IUPUI) – Sam
Father (alum) – Mike
Brother (prospect Bloomington) – Joel
Mother - Jane
Object instances created for above scenario:
Contact
Lead (Team)
• Sam
• Charles
• Mike
(IUPUI Admissions)
• Joel
• Mike (Alumni)
• Jane
• Joel
(Bloomington Admissions)
View of Sam’s relations for IUPUI admissions user:
IU Relation
• Sam – Mike
• Sam – Joel
• Sam – Jane
• Joel – Sam
• Joel – Mike
• Joel – Jane
• Mike – Sam
• Mike – Joel
• Mike – Jane
View of Joel’s relations for Bloomington admissions user:
View of Mike’s relations for Alumni team user:
Configuration:
New Object – IU Relation
Properties Tab
Relationship to Primary Contact (Lead.Contact)
Relationship to Related Contact
Suggested Permissions:
-
-
All IU Relation object instances will be created via the import and hence the users should not be
given the Create IU Relation/Edit IU Relation permission. If a user notices that there is
information missing in Talisma, the same should be updated in the SIS and it will be updated to
Talisma using the batch imports. This will ensure that the SIS and Talisma are always in sync.
Users who will be creating campaigns based on IU Relation object should be given the Campaign
 Manage Campaign  IU Relation in the team in which they are authorized to operate.