Documentation
Contacts
Track partner and internal people, their roles, and relationship levels
Contacts
Track partner and internal people, their roles, and relationship levels
Contacts are the people in your partnerships — both at partner organizations and on your own team. They power participant tagging on activities, the relationship map, and team rollups.
The contacts list
Open Contacts in the sidebar (subheading: "Partner-facing contacts, internal stakeholders, and relationship owners"). Three tabs filter the list: All, Partner contacts, and Internal contacts. A partner dropdown narrows further. Columns are Type, Name, Title, Relationship level, Partner, Account name, and Relationship owner. Header buttons let you Add contact, Export contacts (downloads a CSV), or Import contacts (routes to data import).
Add a contact
Click Add contact (/contacts/new). First choose the type — you can't fill in details until you do:
- Partner contact — someone at a partner organization
- Internal contact — someone at your organization
Then complete the details:
- Name (required)
- Email, Title (optional)
- Partnership roles — pick from suggested chips (Alliances, Executive Sponsor, Co-sell Lead, Delivery Lead, Solutions / Technical, Marketing, Other) or type your own
- Partner — required for partner contacts
- Relationship level — Executive, Leadership, Field, or Technical, each with inline guidance on who belongs there
- Relationship Owner — for partner contacts, the internal person who owns the relationship
If you skip the type you'll see "Choose whether this is a partner contact or an internal contact." A partner contact without a partner prompts "Select the partner this contact belongs to."
The contact detail page
The detail page shows the contact's metadata plus everything they're connected to: the last 10 Activities, connected Accounts, Opportunities (with role badges), Projects, and Events. A Connections panel shows the relationship level and a link to the relationship map. Internal contacts also get a "Link to user account" widget so a login can be tied to that contact for auto-assignment and team roles.
Relationship levels
The four levels map to how alliance leaders think about coverage:
- Executive — the top sponsor or owner of the partnership
- Leadership — senior people running a slice day-to-day (practice or regional leads, your alliance counterpart)
- Field — sellers, BD, and co-sell on specific deals and accounts
- Technical — architects, SEs, and product or integration owners
These levels drive the Relationship Map's coverage matrix.
Common gotchas
Connected accounts on a contact are inferred from activities, opportunities, and projects that reference the contact — you can't set an account directly on a contact record. To associate a contact with an account, tag them on an activity, opportunity, or project for that account.
Linking a login to an internal contact only applies to internal-type contacts; partner contacts can't be linked to a Triad user.
FAQ
Why can't I pick an account on the contact form?
Account connections are derived, not entered. Tag the contact as a participant on an activity (or add them to an opportunity or project) for that account, and the account will appear on their detail page.
What's a Relationship Owner?
For a partner contact, it's the internal person responsible for that relationship. It shows on the contact and feeds the relationship map's owner column.
Can I bulk-load contacts?
Yes — use Import contacts. The CSV needs First Name, Last Name, Email, Title, Type, Partner Name, and External ID; partner contacts must reference an existing partner by name.