Custom Compose Fields

Overview

Admins can configure custom compose fields in Outlook to provide users with drop-downs, check-boxes, or free-form text options. These fields enable things like opt-ins, preferences, or additional context—without affecting or storing core user data in the platform. These custom fields are coded into the HTML template to accomplish the desired behavior.

Getting Started

• Custom Compose Fields must be enabled within the Domain Settings.

• Field Labels

  • Can include capitals and spaces.

  • Field Values (used in HTML) must be all lowercase and underscores in place of spaces.

• Padlock Behavior

  • Unlocked: field resets on each compose.

  • Locked: selection persists for future emails.

• Requires the Outlook add-in.

• You must insert either a plaintext block or visual preview for these custom fields to function.

  • Not compatible with stamping.

• Changes are local to each device — selections do not sync across devices and must be set individually.

Compose Field Types

• Dropdown

• Checkbox

• Text

Field Labels & Values

• Field Label → What the user sees in the add-in pane.

• Field Value → The value that gets coded into the HTML template.

• Field values must be custom. Avoid using default field names like name or title.

  • Do not use field names that exist within the user profiles.

  • Do not use internal defined fields.

    • Example: use title_1 or title_custom instead of title.

Global vs Group Assignment

Priority Order:

1. User profile

2. Group level

3. Domain settings level

Group Level Configuration: fields apply only to members of that group once the group is assigned to a signature via Routing.

Domain Setting Configuration: fields apply to all users scoped to the add-in.

Field Types

1. Dropdown

• Admin defines a preset list of options for users.

• Line 1 defines the name of the dropdown (Field Label) and what value to code via HTML (Field Value).

  • Label = what appears in the add-in dropdown.

  • Value = what is used in HTML/signature.

Example Use Cases: region, titles, salutations.

Example HTML:

{% if salutation_custom != blank %}
<tr>
  <td valign="bottom" style="color:#379190;font-size:13px;font-family:Aptos, Arial;line-height:19px;white-space:nowrap">
    {{ salutation_custom }}
  </td>
</tr>
{% endif %}

2. Text

• Provides a free-fill text box.

• Where the field value is coded in the HTML is where it appears in the signature.

• Character limits can be set in HTML.

  • Field Label = name of the text box.

  • Field Value = {{field_value}} coded in the HTML.

Example Use Cases: OOO Messages, Special Instructions.

Example HTML:

<td valign="bottom" style="white-space:nowrap;max-width:50ch;overflow:hidden;text-overflow:ellipsis;">
  {{ custom_text | slice: 0,50 }}
</td>

3. Checkbox

• Provides a boolean toggle: ON returns true, OFF returns false

  • Field Label = name of the checkbox.

  • Field Value = {{field_value}} used in HTML.

Note: No need to code in the HTML for “true” or “false.” If set to false, nothing renders; if set to true, it renders. These values are treated as booleans, not strings. Please reference the example HTML below.

Example Use Cases: Pronoun Opt-in, Headshot Opt-in, Disclaimer Opt-in.

Example HTML:

{% if show_pronouns %}
<tr>
  <td style="color:#010101;font-size:12.5px;font-family:Lato, Arial, Helvetica,sans-serif;white-space:nowrap">
    {{ pronouns }}
  </td>
</tr>
{% endif %}

Best Practices

• Always use unique field values to avoid conflicts with user and group fields.

• Lock fields only when persistence is required.

• When assigning custom field values via group assignment, append an identifier to the group name to indicate it contains custom values.

  • Example: sales_custom_compose_fields

Opensense Support

For further assistance, contact Opensense Support:

• Email: help@opensense.com

• Knowledge Base: help.opensense.com