Hi team,
I wanted to share a feature request based on how we manage relationships and communications in our fundraising pipeline.
Core need:
We often work with multiple stakeholders tied to a single “primary” contact, and need a structured way to ensure consistent communication across that group.
We often work with multiple stakeholders tied to a single “primary” contact, and need a structured way to ensure consistent communication across that group.
Example use case:
- Barry is the primary contact (e.g., partner or lead decision-maker).
- Jane is Barry’s assistant and should be CC’d on all communications by default so she can triage.
- In other cases, Barry and Bob are both decision-makers, and Bob should also be CC’d on every email.
Current gap:
Right now, there’s no clean way to associate additional contacts with a primary contact such that they are automatically included in outbound communication. This creates manual overhead and increases the risk of missing key stakeholders.
Right now, there’s no clean way to associate additional contacts with a primary contact such that they are automatically included in outbound communication. This creates manual overhead and increases the risk of missing key stakeholders.
Proposed solution:
- Allow a primary contact to have one or more associated contacts (secondary, tertiary, etc.).
- These associated contacts should be:
- Linked at the contact or org level
- Automatically CC’d (or optionally included) on all outbound emails tied to that primary contact or deal
- Ideally configurable per relationship (e.g., toggle who is included by default)
Why this matters:
Fundraising and deal workflows are rarely one-to-one. They’re multi-threaded across assistants, partners, and internal stakeholders. This feature would better reflect real-world communication patterns and reduce friction in managing those relationships.
Fundraising and deal workflows are rarely one-to-one. They’re multi-threaded across assistants, partners, and internal stakeholders. This feature would better reflect real-world communication patterns and reduce friction in managing those relationships.
Curious if this is already on your roadmap or if there are recommended workarounds today.
Thanks,
Brian
Brian