NASA Eclipse: How Fuse Chooses a Primary Contact & Maps Important Data for All Contacts

For NASA Eclipse users: How does Fuse decide who the Primary Contact is? Where does Fuse look to get Names, Emails, Birthdays, and more?

Overview

All names, emails, and other contact details in Fuse are primarily derived from NASA's Insured, Co-Insured, or Related Parties entries. Occasionally, the Primary Contact email alone may also be pulled from the "Email/Web Addresses" section. (Please Note: Fuse does NOT use the "Lookup" names from Eclipse's Miscellaneous tab).

Before any data is sent to Fuse, Eclipse looks at those entries and determines whether each of them is a person or an organization/company based on the Entity type you've given it (for example, an "Individual" is treated as a person and a "Corporation" is treated as an organization/company).

Then, depending what it finds, Eclipse determines who the Primary Contact is, considers everyone else a "secondary contact", and sends Fuse the details for each person by using the following logic:

PRIMARY CONTACT

Names

1. First Name / Last Name

   Comes from the first entry that you've identified as a person, in this order of priority:

   1. Insured
      ​(The Insured is considered a person if its Entity is "Individual", "Individuals (more than one)", or "Estate of".)

   2. Co-Insured
      ​(The Co-Insured is considered a person if its Entity is anything other than "Doing Business As" or "Trading Business As")

   3. Related Parties
      ​(All Related Parties are people.)

2. Company Name

   When applicable, comes from the first entry that you've identified as a business or organization in this order of priority (If it is not defined as a person based on the rules above, it is considered a business or organization):

   1. Insured

   2. Co-Insured

3. Salutation

   Appears in Fuse as a separate "Salutation" field. If desired, it can be merged into emails in place of the First Name field. This provides an alternative name source that is entirely under your control.

Email Address & More

1. After determining which name entry to use as the Primary Contact (above), Eclipse checks the "Related Party" data correlated with that name and sends Fuse all additional details it can from there, including email address, birthday, and more.

2. If no email was found in the step above, Fuse tries to give the primary contact any email address it can find by checking all other email entries, including emails that have been entered under the "Emails/Web Addresses" section in NASA, and simply uses the first one it finds.

After determining which name entry to use as the Primary Contact (above), Eclipse checks the "Related Party" data correlated with that name and sends Fuse all additional details it can from there, including email address, birthday, and more.
​

If no email was found in the step above, Fuse tries to give the primary contact any email address it can find by checking all other email entries, including emails that have been entered under the "Emails/Web Addresses" section in NASA, and simply uses the first one it finds.

SECONDARY CONTACTS

Fuse's Secondary Contacts are derived from these Eclipse entries:

1. Co-Insured - If it is defined as a person (Also note: The Co-Insured will not be a secondary contact if it was already mapped as Fuse's Primary Contact).

2. Related Parties - All related parties (except the one that correlates with the Primary Contact) are used as Secondary Contacts.

Co-Insured - If it is defined as a person (Also note: The Co-Insured will not be a secondary contact if it was already mapped as Fuse's Primary Contact).

Related Parties - All related parties (except the one that correlates with the Primary Contact) are used as Secondary Contacts.

Names, Email Addresses, & More

Simply put: All relevant fields are mapped into Fuse from their Related Party entry, including:

• Email

• Phone

• Address, City, State, Zip Code

• Birthday