Improve Custom Field Logic in Documents & Contracts for Multi-Party Support
T
Tron Tran
Building on my earlier suggestion regarding field assignments for multiple contacts in the Documents & Contracts template feature, I wanted to raise another improvement opportunity related to custom fields (merge fields).
At present, even when fields are set with the "To be filled by" property (e.g., Contact, Sender, Creator), merge fields still default to pulling data from the primary contact only, regardless of who the field is actually assigned to. This creates a major limitation when preparing documents that need to:
- Automatically insert the name, email, or phone number of the assigned contact completing that section
- Support multiple parties (e.g. client, support person, guardian, etc.)
đź’ˇ Suggested Improvement:
Update the custom field logic so that when a field is assigned using the "To be filled by" dropdown (e.g., Primary, Secondary, Tertiary Contact), the corresponding custom fields pull data from that specific assigned contact, not just the primary.
For example:
- If a signature or name field is marked "To be filled by: Secondary Contact"
- Then custom fields like {{contact.name}} within that field should pull from the Secondary Contact’s profile (or custom value)
âś… Benefits:
Enables more powerful automation for contracts and service agreements
- Avoids manual entry or duplication of fields
- Makes merge fields context-aware based on contact assignment
- Expands use of GHL documents for organisations with complex client relationships
Would love to see this implemented—it would really unlock the full potential of document automation and take the feature to the next level!
Thanks again 🙌
Log In