Templates could already read contract details and contract custom fields, and
automations could send a message to a role. What they couldn’t do was mention
one participant to another: “your attorney is Ada Lovelace, reachable at
(617) 555-1234.”
What you may notice
The merge field picker for email templates, text templates, notes and
automation steps has a new Contract Roles section, next to Contract and
Contract Custom Fields. Every contract contact role on your team, built in or
custom, lists six fields:
- first name
- last name
- full name
- email (the contact’s primary email)
- phone (the contact’s primary phone, shown as (xxx) xxx-xxxx)
- company
The tag is built from the role’s name. A role called “Buyer Attorney” gives you
{{contract.role.buyer_attorney.first_name}}, {{contract.role.buyer_attorney.phone}}
and so on. Add a role in Settings and its fields appear in the picker right away.
How the fields fill in
- The value comes from whoever holds that role on the contract the message is
about. If the role is empty, the field renders blank, the same as an empty
custom field. - If several people share one role, the first person added to the contract in
that role is used. If you need to address two buyers separately, create two
roles, such as Buyer 1 and Buyer 2. - Renaming or removing a role does not break existing templates. Fields for the
old name simply render blank until you update the template. - A role filled by a company shows the company name in the full name and
company fields and leaves first and last name blank.
Role fields also work in automation emails and texts sent to a contract role,
which now resolve all contract merge fields against the contract that triggered
the step.