Use field groups
Expand a group on a contact, account, or deal to see its fields. Groups keep related details together and hide empty rows. Select a value to edit it. Required fields, option lists, and field checks still apply.
Admins set up fields in Manage fields. Choose a clear label and the right data type. Each field has a machine key for APIs and connected tools. The key stays the same when you change the label.
Define personalization tokens
A personalization token adds a record value to a message. Core and custom fields share this system. Open the field's token settings to turn it on. Add fallback text if you need it.
Tokens are scoped to the record type. For example:
{{contact.first_name}}
{{contact.first_name | default:"there"}}
Use the token picker or copy the token from its definition instead of inventing a key. Custom field tokens use the field's stable machine key. Renaming a display label does not create a new token.
Preview before sending
Choose a contact to preview their email. Deal and account tokens need those records too. The system must not guess which linked deal you mean.
Missing values need a fallback or a completed field. An unknown, disabled, or archived token needs correction. Check both a contact with complete data and one with missing optional values.
In custom HTML, use tokens in text content. Do not put them in HTML attributes, scripts, styles, or link targets. Token support in a shared service does not mean every communication channel is enabled in your workspace.