I have a custom object built out with Contacts associated with each “object.” When I select the email button, it doesn’t auto-populate the associated contact’s email address, and we have to type it in. This runs the risk that we could email the wrong person as we are sending sensitive information to more than one person.
Status: Idea Submitted
I have the same concern with emailing contacts associated to a custom object. Preferably it would have the same function of Deals and Tickets in that the “To” field of the email would recognize the associated contacts.
Ditto! We really need this list to be accessible for our custom objects.
To resolve this issue, ensure that the custom object is correctly linked to the Contact in Salesforce using a Lookup Relationship. Then, customize the Email action to pull the Contact’s email address dynamically by adding a formula or pre-populating the email field in the Email Quick Action. You may also need to check if the Contact’s email field is accessible in your page layout or automation.
It’s frustrating that custom objects—despite their significant cost—have a limited feature set. As an end user, it’s confusing when functions (like autofilling contacts in the email) that work in other object types (like contacts, deals, and companies) don’t work in custom objects, even though they appear identical in use. I’ve even reported this to support because I thought it was a bug because it seemed nuts that such essential functionality would be missing from custom objects.
Couldn’t agree more - this is needed! I created custom objects recently and only realised this limitation afterwards. Very frustrating that the added expense comes with limited features!
It also does not populate in the new Hubspot Objects - Listings/Services/Appointments, which are the new standard objects.
Hard to understand why this functionality isn’t the same as regular objects such as deals/tickets. Please keep me updated if this is worked on.
much needed feature for custom objects
I want to strongly support this idea.
In our case, this happens with the new “Projects” object created by HubSpot.
Even though the Project is associated with a Contact, when we click the email button the contact’s email is not auto-populated, forcing the user to manually type it in.
This creates a real operational risk, especially when dealing with sensitive or confidential information, since it increases the chance of sending emails to the wrong person.
From a usability and data safety standpoint, the expected behavior would be:
- If a Contact is associated → their email should be automatically suggested or pre-filled
- Or at least give the user the option to select from associated contacts
This small gap creates unnecessary friction and risk in day-to-day operations.
Hope this gets prioritized, especially now that Projects is a native object.